context safety score
A score of 49/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
brand impersonation
The page is served from the domain 'anne-clark-talla-2xlc.hydr0.org' (note: 'hydr0' with a zero, not the letter 'o') but presents itself entirely as 'MP3.cc', including the title tag, logo, canonical URL, Open Graph metadata, footer copyright, and all navigation links pointing to mp3.cc. The subdomain infrastructure (hydr0.org / hydrofm) hosts a pixel-perfect clone of MP3.cc, impersonating that brand without authorization. (location: page.html:5, page.html:9, page.html:11, page.html:14, page.html:614)
malicious redirect
The canonical link tag redirects crawlers and AI agents to 'https://mp3.cc/t/2523661560-anne-clark-talla-2xlc/' while the actual serving domain is 'anne-clark-talla-2xlc.hydr0.org'. This misleads indexing agents and search engines about the true origin of the content, effectively hijacking SEO authority from the legitimate MP3.cc domain. (location: page.html:9)
malicious redirect
All 19 MP3 audio file download/play URLs route through 'fine.sunproxy.net', a third-party proxy service, using base64-encoded opaque file paths. Users and AI agents clicking play or download are directed through this intermediary rather than the ostensible MP3.cc infrastructure, enabling traffic interception, substitution of payloads, or tracking. (location: page.html:228, page.html:247, page.html:266, page.html:285, page.html:304, page.html:323, page.html:342, page.html:361, page.html:380, page.html:399, page.html:418, page.html:437, page.html:456, page.html:475, page.html:494, page.html:513, page.html:532, page.html:551, page.html:570, page.html:589)
hidden content
A full PHP fatal error stack trace is rendered in the page body and visible in page-text.txt, exposing internal server file paths ('/var/www/oxy/data/www/hydro.fm/system/...'), class names, and database library internals. This information disclosure reveals the real backend infrastructure ('hydro.fm') behind the hydr0.org front, and can be leveraged by attackers to map the application structure. (location: page.html:629-638, page-text.txt:528-537)
obfuscated code
All 19 audio file URLs passed to the 'fine.sunproxy.net' proxy contain long base64-encoded path components (e.g., 'NDgwdkFuTUxJZ0tH...'). These opaque tokens obscure the true destination of audio file requests, preventing inspection of the actual resource being fetched. The brin-context pre-scan flagged 12 suspicious base64 blobs consistent with this pattern. (location: page.html:228, page.html:247, page.html:266, page.html:285, page.html:304, page.html:323, page.html:342, page.html:361, page.html:380, page.html:399, page.html:418, page.html:437, page.html:456, page.html:475, page.html:494, page.html:513, page.html:532, page.html:551, page.html:570, page.html:589)
curl https://api.brin.sh/domain/anne-clark-talla-2xlc.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
anne-clark-talla-2xlc.hydr0.org currently scores 49/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.