context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The page is served from hydr0.org subdomain (black-sabbath-amp-junkie-xl.hydr0.org) but clones the full visual identity, branding, CSS, JavaScript, and layout of mp3.cc. The canonical tag points to mp3.cc, making this a typosquat/subdomain clone impersonating the legitimate MP3.cc service. Copyright footer falsely claims '© 2017–2026 MP3.cc' while the actual domain is hydr0.org. (location: page.html:5, page.html:9, page.html:538)
malicious redirect
All audio playback URLs route through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. Users clicking play are silently redirected through this off-brand proxy which handles all actual media delivery. This proxy domain could intercept requests, serve malware-laced files, or track users without their knowledge. (location: page.html:228, page.html:247, page.html:266 (and all data-url attributes in playlist items))
malicious redirect
The page canonical tag redirects to https://mp3.cc/t/2450207296-black-sabbath-amp-junkie-xl/, representing a redirect from the serving domain (hydr0.org) to the impersonated domain (mp3.cc). This is the single redirect flagged in Tier 2 pre-scan signals and serves as a SEO cloaking mechanism. (location: page.html:9, metadata.json (redirects: 1))
social engineering
An off-domain link to looz.net is embedded in the sidebar genre navigation list with a special CSS class 'z__important' and opens in a new tab (_blank). This disguises an off-domain promotional/affiliate link as a legitimate genre navigation item ('Online Radio'), manipulating users into clicking an unaffiliated external site. (location: page.html:204-215)
obfuscated code
12 base64-encoded blobs appear in data-url attributes of playlist play buttons. These encode proxied file paths for fine.sunproxy.net. While individually they encode MP3 file paths, the use of base64 obfuscation conceals the true routing of media requests through the sunproxy.net infrastructure, obscuring the off-domain media proxy from casual inspection. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513 (all data-url attributes))
curl https://api.brin.sh/domain/black-sabbath-amp-junkie-xl.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
black-sabbath-amp-junkie-xl.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.