context safety score
A score of 41/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
brand impersonation
The site operates on hianime.do but consistently brands itself as 'HiAnime.to' throughout all content, titles, meta tags, og:title, and body text. The .do domain is impersonating the legitimate HiAnime.to brand, including using hianime.to in the page title ('Watch Anime Online, Free Anime Streaming Online on HiAnime.to Anime Website') while actually serving from hianime.do. (location: page.html:4,12,163,175,176,181,186 — title, og:title, h1, body text)
obfuscated code
Two near-identical heavily obfuscated JavaScript blocks are present, loaded from yb23b.com (data-verifysrc) and inline. The obfuscation uses a character-interleaving string encoder, creates hidden iframes, intercepts document.createElement and querySelector, patches localStorage, manipulates the DOM environment, and proxies window/document APIs. This pattern is consistent with ad-fraud, click injection, fingerprinting, or malware delivery scripts that evade detection by obscuring their behavior. (location: page.html:554-555 — two <script> blocks with data-cfasync='false' and data-verify='1')
malicious redirect
The obfuscated scripts load an external payload from yb23b.com via data-verifysrc attribute. This third-party domain is not a known CDN or legitimate ad network and the script dynamically manipulates the browsing context, potentially redirecting users or injecting additional scripts at runtime. (location: page.html:554 — data-verifysrc='https://yb23b.com/vignette.min.js')
hidden content
The obfuscated scripts intercept document.createElement, patch localStorage with a custom proxy, and create hidden iframes (setting style to display:none equivalent), allowing content and behavior invisible to the user to operate in the page context. This hidden iframe technique is used to sandbox and execute additional payloads outside user visibility. (location: page.html:554-555 — obfuscated scripts performing hidden iframe creation and DOM API interception)
social engineering
The page contains explicit trust-building language designed to reassure users about safety: 'Yes we are safe', 'we keep scanning the ads 24/7', 'only one Ads', 'trustworthy and safe site'. This is a common social engineering pattern on piracy/shadow sites to lower user guard before delivering ad payloads or redirects. (location: page.html:181-185, page-text.txt:111-115)
curl https://api.brin.sh/domain/hianime.doCommon questions teams ask before deciding whether to use this domain in agent workflows.
hianime.do currently scores 41/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.