context safety score
A score of 37/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
js obfuscation
JavaScript uses Function constructor for runtime code generation
obfuscated code
Two nearly identical heavily obfuscated JavaScript blocks are injected at the bottom of the page (lines 540-541 in page.html). The code uses a string-interleave decode technique ('ChmaorrCfozd...'.split('').reduce((B,J,R)=>R%2?B+J:J+B).split('z')) to reconstruct method names at runtime, then dynamically creates hidden iframes, wraps document APIs, intercepts querySelector calls, and manipulates localStorage/sessionStorage. This pattern is characteristic of malvertising loaders and ad-fraud scripts. The script is loaded from yb23b.com (data-verifysrc attribute) and runs without CSP restrictions. (location: page.html:540-541, data-verifysrc=https://yb23b.com/vignette.min.js)
malicious redirect
The obfuscated script (loaded via https://yb23b.com/vignette.min.js) creates hidden iframes and intercepts document.createElement calls, a well-known technique used by ad-fraud and malvertising infrastructure to silently load third-party content, execute redirects, or serve pop-under ads outside user visibility. The domain yb23b.com has no clear legitimate affiliation with HiAnime. (location: page.html:540, data-verifysrc=https://yb23b.com/vignette.min.js)
hidden content
Commented-out ad script block references 'pubbidgeartag' with zone ID 10411 and captures window.location.href. While currently disabled via HTML comments, this ad network integration code (lines 252-265) was previously active and transmits the visitor's current URL to a third-party ad network, which can be used for tracking or retargeting without user consent. (location: page.html:252-265)
social engineering
The site explicitly promotes itself as 'safe' and claims to actively scan ads 24/7, building false trust with users while simultaneously embedding obfuscated third-party scripts. This trust-building language ('Is HiAnime.to safe? Yes we are...') contradicts the actual presence of opaque, unvetted code from external domains. (location: page.html:181-185, page-text.txt:111-115)
curl https://api.brin.sh/domain/hianime.toCommon questions teams ask before deciding whether to use this domain in agent workflows.
hianime.to currently scores 37/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.