context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
5 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted on a typosquatting/lookalike subdomain (dr-dre-feat-2pac-eminem-dr-dre-kurupt-snoop-nate-dogg-dmx-nas.hydr0.org) that mimics the legitimate MP3.cc service. The canonical URL and all internal links point to mp3.cc, but the actual serving domain is hydr0.org — a different third-party domain. Users and agents navigating to this URL are silently served content belonging to a different brand from a different host, constituting a redirect/domain mismatch deception. (location: metadata.json: url field; page.html: <link rel='canonical'> line 9)
brand impersonation
The page fully impersonates MP3.cc — including its logo, branding, title tag, og:site_name, canonical link, CSS/JS assets, and footer copyright — while being hosted on hydr0.org. All visual and metadata signals present the site as MP3.cc to users and crawlers/agents, but the actual domain is entirely different. This is a complete brand clone. (location: page.html: lines 5, 9, 11, 18-19, 33-36, 609-614; metadata.json: domain field)
malicious redirect
All MP3 audio files are served via fine.sunproxy.net, a third-party proxy domain, rather than from mp3.cc or hydr0.org directly. The data-url attributes in each playlist item point to fine.sunproxy.net/file/ endpoints with base64-encoded path parameters. This routes all media traffic through an unvetted intermediary that could intercept, modify, or track requests. 12 suspicious base64 blobs were flagged in the pre-scan, consistent with these encoded proxy URLs. (location: page.html: lines 228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570 (all data-url attributes))
social engineering
The site presents itself as a free, legitimate MP3 download service using well-known celebrity artist names (Dr. Dre, Eminem, 2Pac, Snoop Dogg, DMX, Nas, etc.) as search bait to attract users. The domain name itself is constructed entirely from famous rapper names to maximize search engine and user trust, while the actual serving infrastructure (hydr0.org + sunproxy.net) is entirely separate from the branded identity presented. (location: metadata.json: domain field; page.html: line 5 (title), line 224 (h2 heading))
hidden content
The page contains an HTML comment embedding the raw search query string immediately after the visible h2 heading: <!-- "dr dre feat 2pac eminem dr dre kurupt snoop nate dogg dmx nas" -->. While minor, this is a pattern used to inject additional keyword signals invisible to users but visible to crawlers and AI agents parsing raw HTML. (location: page.html: line 224)
curl https://api.brin.sh/domain/dr-dre-feat-2pac-eminem-dr-dre-kurupt-snoop-nate-dogg-dmx-nas.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-dre-feat-2pac-eminem-dr-dre-kurupt-snoop-nate-dogg-dmx-nas.hydr0.org currently scores 40/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.