context safety score
A score of 67/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
brand impersonation
The page is served from anthrax-ft-chuck-d-of-public-enemy.hydr0.org but fully impersonates mp3.cc: the page title reads 'MP3.cc', the footer copyright states '© 2017–2026 MP3.cc', all navigation and genre links point to mp3.cc, and the canonical/OG URLs are set to mp3.cc. The hydr0.org domain is operating as an unauthorized mirror/clone of mp3.cc without disclosure. (location: page.html:5,9,11,14,443 — <title>, canonical, og:url, og:site_name, footer copyright)
malicious redirect
All audio file URLs route through the third-party proxy domain fine.sunproxy.net rather than mp3.cc or hydr0.org. This intermediary proxy intercepts media requests and could redirect, track, or tamper with downloads. The base64-encoded path segments in the proxy URLs obfuscate the actual file locations. (location: page.html:228,247,266,285,304,323,342,361,380,399,418 — data-url attributes pointing to fine.sunproxy.net)
hidden content
11 base64-encoded blobs are embedded within data-url attributes on playlist items. While decoded values appear to be encrypted/tokenized file-access credentials (not plaintext injection), the obfuscated encoding hides the actual downstream resource paths from scanners and agents, making the true destination of audio file requests opaque. (location: page.html:228,247,266,285,304,323,342,361,380,399,418 — data-url base64 path segments on fine.sunproxy.net URLs)
social engineering
The subdomain name 'anthrax-ft-chuck-d-of-public-enemy.hydr0.org' is crafted to exactly match a popular music search query, designed to attract users and automated agents searching for this content and funnel them through the unauthorized mirror rather than the legitimate mp3.cc site. (location: metadata.json — domain field; .brin-context.md — URL/Domain fields)
curl https://api.brin.sh/domain/anthrax-ft-chuck-d-of-public-enemy.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
anthrax-ft-chuck-d-of-public-enemy.hydr0.org currently scores 67/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.