context safety score
A score of 36/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
js obfuscation
JavaScript contains heavy hex-escape encoding typical of obfuscation
obfuscated code
JavaScript array uses hex-encoded strings (\x70\x75\x73\x68, etc.) to obfuscate function names and values including 'cookie', 'decrypt', 'R3ACTLB=', and cookie expiry strings. Variable names are mangled (_0xa3fe, _0x4e0ex2). This is a classic obfuscation pattern used to hide malicious intent from static analysis. (location: page.html:11, page-text.txt:8)
obfuscated code
The obfuscated script uses AES decryption (via /aes.min.js and slowAES.decrypt) with hardcoded hex keys/IV (67f5b2892b882944714f157552ceeda2, 0b6871b675e8fc798cedc460bd84db59, d5c795e64d393923bfd6fa5e7d9e69db) to compute and set a cookie named 'R3ACTLB'. This encrypted cookie-setting mechanism conceals the payload value from static inspection. (location: page.html:10-11)
malicious redirect
A timed JavaScript redirect (setTimeout) fires after 5000ms to 'https://blackrussia.online:443/', combined with a dynamically loaded external HTML fragment via w3IncludeHTML('/5s.html'). The redirect is obfuscated inside a script that also performs AES cookie operations, suggesting a DDoS bypass or cloaking mechanism before delivering actual content. (location: page.html:5,8,12)
hidden content
The page body contains almost no visible content — only a noscript warning. Real content is loaded dynamically via an external script (/vddosw3data.js) and a remote HTML include (/5s.html), both fetched at runtime. This deferred/hidden content loading prevents static analysis from seeing the actual page payload. (location: page.html:3,5)
hidden content
The page uses a DDoS-protection challenge pattern (AES-encrypted cookie 'R3ACTLB', JavaScript requirement gate, timed redirect) consistent with anti-bot/anti-crawler cloaking systems used to serve different content to real users versus security scanners. This obscures the true landing page from automated analysis. (location: page.html:6-12)
curl https://api.brin.sh/domain/blackrussia.onlineCommon questions teams ask before deciding whether to use this domain in agent workflows.
blackrussia.online currently scores 36/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.