context safety score
A score of 54/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 page is hosted on a subdomain (drake-x-lil-baby.hydr0.org) that clones content from mp3.cc, with a canonical tag pointing to mp3.cc and all internal links redirecting to mp3.cc. The subdomain acts as a cloaked mirror/redirect site that intercepts traffic intended for the legitimate mp3.cc service. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/3500657199-drake-x-lil-baby/">)
brand impersonation
The site at hydr0.org fully impersonates mp3.cc — reproducing its logo, branding, CSS/JS assets loaded directly from mp3.cc CDN, copyright notice '© 2017–2026 MP3.cc', and identical page layout. The domain hydr0.org is unrelated to mp3.cc, creating a deceptive brand impersonation to appear as the legitimate mp3.cc service. (location: page.html:5,18-19,33-36,671 - title, assets, logo, footer copyright)
malicious redirect
All MP3 audio file URLs (data-url attributes) point to fine.sunproxy.net, a third-party proxy domain, rather than mp3.cc infrastructure. Users clicking play will have their requests routed through an unknown proxy (sunproxy.net) which could intercept, log, or manipulate traffic. 12 such proxy URLs are present, consistent with the 12 suspicious base64 blobs flagged in Tier 2 (the base64 strings are encoded file path tokens passed to sunproxy.net). (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627 - data-url attributes pointing to fine.sunproxy.net)
social engineering
The site presents itself as a free, legal MP3 download service using celebrity artist names (Drake, Lil Baby) to attract users, while actually operating as an unauthorized mirror that routes downloads through a third-party proxy. This exploits user trust in recognized artist names to drive traffic and proxy usage. (location: page.html:5 - title tag; page.html:224 - h2 heading 'Drake X Lil Baby')
curl https://api.brin.sh/domain/drake-x-lil-baby.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
drake-x-lil-baby.hydr0.org currently scores 54/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.