context safety score
A score of 39/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
JavaScript uses Function constructor for runtime code generation
social engineering
Site distributes modified ('Мод меню' / 'Unlocked') versions of commercial games (Zombie Catchers, Angry Birds 2, Monument Valley, Lara Croft GO, Subway Surfers, etc.) without authorization, inducing users to download pirated/cracked APKs that may contain malicious payloads. The use of well-known brand names to attract downloads is a classic social-engineering vector. (location: page.html lines 17–1075, feed items listing modded/unlocked apps)
brand impersonation
The site uses trademarked game titles and official artwork (Angry Birds, Monument Valley, Lara Croft GO, Subway Surfers, Toca Boca World, DREDGE, etc.) to present itself as a legitimate source for these apps, while distributing unofficial modified builds. This constitutes brand impersonation to build false trust. (location: page.html lines 17–1075, img alt attributes and feed__item-title elements)
hidden content
A Yandex Metrica tracking pixel is injected via a noscript tag with style='position:absolute; left:-9999px;' positioning it off-screen and invisible to users, constituting hidden tracking content. (location: page.html line 1269, noscript div with img src='https://mc.yandex.ru/watch/14969539')
social engineering
A dynamically loaded language banner is injected via an AJAX call 5 seconds after DOMContentLoaded ($.post('/lang_banner/')), allowing server-controlled content injection into the page after initial load without user awareness. This pattern can be used to deliver targeted social engineering content post-load. (location: page.html line 6, script block: $.post('/lang_banner/', ...))
social engineering
The site distributes 'Lucky Patcher' and 'Root Explorer' — tools commonly used to bypass app licensing, root devices, and patch security controls — normalizing use of device-compromise tools under the guise of a utilities catalog. (location: page-text.txt line 975, sidebar 'Самые нужные' section listing Lucky Patcher and Root Explorer)
curl https://api.brin.sh/domain/pdalife.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
pdalife.to currently scores 39/100 with a suspicious verdict and low confidence. The goal is to protect agents from high-risk context before they act on it. Treat this as a decision signal: higher scores suggest lower observed risk, while lower scores mean you should add review or block this domain.
Use the score as a policy threshold: 80–100 is safe, 50–79 is caution, 20–49 is suspicious, and 0–19 is dangerous. Teams often auto-allow safe, require human review for caution/suspicious, and block dangerous.
brin evaluates four dimensions: identity (source trust), behavior (runtime patterns), content (malicious instructions), and graph (relationship risk). Analysis runs in tiers: static signals, deterministic pattern checks, then AI semantic analysis when needed.
Identity checks source trust, behavior checks unusual runtime patterns, content checks for malicious instructions, and graph checks risky relationships to other entities. Looking at sub-scores helps you understand why an entity passed or failed.
brin performs risk assessments on external context before it reaches an AI agent. It scores that context for threats like prompt injection, hijacking, credential harvesting, and supply chain attacks, so teams can decide whether to block, review, or proceed safely.
No. A safe verdict means no significant risk signals were detected in this scan. It is not a formal guarantee; assessments are automated and point-in-time, so combine scores with your own controls and periodic re-checks.
Re-check before high-impact actions such as installs, upgrades, connecting MCP servers, executing remote code, or granting secrets. Use the API in CI or runtime gates so decisions are based on the latest scan.
Learn more in threat detection docs, how scoring works, and the API overview.
Assessments are automated and may contain errors. Findings are risk indicators, not confirmed threats. This is a point-in-time assessment; security posture can change.
integrate brin in minutes — one GET request is all it takes. query the api, browse the registry, or download the full dataset.