context safety score
A score of 58/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The scanned URL (2426067485.hydr0.org) is a subdomain that serves content fully impersonating MP3.cc, including canonical tag, og:url, all asset URLs, and footer copyright pointing to mp3.cc. The page was reached via a redirect (1 redirect detected in pre-scan), routing users from the suspicious hydr0.org subdomain to what appears to be the legitimate MP3.cc site — but the page is actually served from the attacker-controlled domain. This is a classic cloaking/redirect pattern used to proxy a legitimate site. (location: page.html:9 (canonical href), metadata.json (url field), .brin-context.md (Redirects: 1))
brand impersonation
The page fully impersonates MP3.cc: the title reads 'Most popular songs | Download mp3 free, listen music online - MP3.cc', the logo and branding say 'MP3.cc', og:site_name is 'MP3.cc', the canonical URL points to https://mp3.cc/, and the footer copyright states '© 2017 – 2026 MP3.cc'. All of this content is served from 2426067485.hydr0.org — a numerically-prefixed subdomain with no relation to mp3.cc, designed to deceive users and automated agents into believing they are on the legitimate site. (location: page.html:5,9,11,14,1184)
malicious redirect
All MP3 audio files are served via fine.sunproxy.net, a third-party proxy domain, rather than from mp3.cc or any CDN associated with it. Every play link routes audio through this intermediary (e.g., data-url='https://fine.sunproxy.net/file/...'). This sunproxy.net infrastructure is the same operator as hydr0.org and may be used to track plays, inject malware, or serve modified files. The filenames in the URLs are appended with '(Hydr0.org)' confirming operator ownership. (location: page.html:228,247,266 (and all subsequent playlist-play data-url attributes))
hidden content
The MP3 file URLs embedded in data-url attributes contain long base64-encoded path segments (e.g., NDgwdkFuTUxJZ0tHbEJUVFE0QUZzNUtmT3Q5UlZlNlA...). The pre-scan flagged 12 suspicious base64 blobs. These blobs are consistent with encoded file tokens or signed URLs, but they are opaque to inspection and could conceal tracking parameters, session tokens, or exfiltration data embedded in the file request path. (location: page.html:228,247,266 (all playlist data-url attributes — 12+ instances))
curl https://api.brin.sh/domain/2426067485.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2426067485.hydr0.org currently scores 58/100 with a caution 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.