context safety score
A score of 45/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
cloaking
Page conditionally redirects based on referrer or user-agent
obfuscated code
Large inline script labeled '<!-- PC Pops -->' uses URI-encoded payload with a custom character-rotation cipher (charCode-32 mod-95 Caesar-style shift keyed by string position) to hide its true behaviour at parse time. The decoded string is then sliced by a hardcoded index table and reassembled into URLs, function names, and logic before execution, making static analysis impossible without runtime evaluation. (location: page.html:413-414 (inline <script data-cfasync="false"> block, PC Pops comment))
malicious redirect
An external script is loaded from the suspicious domain 'chubbyexemplaryhardiness.com' (path /on.js) via a protocol-relative URL. The domain name is a randomly generated nonsense string — a common pattern for malvertising/popup networks. The script is wired to a callback function 'xmlim(15)' both on load and on error, and carries a 'data-clocid' attribute (2100442) consistent with pop-under/pop-up ad injection frameworks. This third-party script executes with full page privileges and likely triggers unsolicited redirects or pop-ups. (location: page.html:415 (<script src="//chubbyexemplaryhardiness.com/on.js">))
obfuscated code
The Bance SSP ad-network scripts (js.ssp.bance.jp/bnctag.js) are injected three times into the page body with different placement IDs (10060, 10062, 3030) and publisher IDs (803, 68). While bance.jp is a known Japanese ad network, these inline tag-manager scripts execute third-party code with full DOM access and could serve malicious ad payloads or conduct user tracking beyond normal analytics. (location: page.html:184-191, 320-329, 374-382 (Bance Native ad blocks))
hidden content
Two Google Analytics tracking IDs are loaded simultaneously (UA-191785687-1 and G-X42TH49BB5), with both using duplicate 'window.dataLayer' and 'gtag' function definitions. Dual-tracking configurations can be used to exfiltrate user behaviour data to multiple parties and may indicate the site operator and a third party are independently collecting analytics. (location: page.html:35-48 (dual gtag scripts in <head>))
curl https://api.brin.sh/domain/nyahentai.oneCommon questions teams ask before deciding whether to use this domain in agent workflows.
nyahentai.one currently scores 45/100 with a suspicious verdict and medium 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.