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 page is hosted on a subdomain of hydr0.org (drake-ft-big-sean-kanye-west.hydr0.org) but all canonical URLs, assets (CSS/JS), and links point to mp3.cc. The canonical tag explicitly redirects to https://mp3.cc/t/850351518-drake-ft-big-sean-kanye-west/. This is a shadow/doorway domain pattern where the hydr0.org domain is used to capture traffic and funnel users to mp3.cc, confirmed by the single redirect noted in the pre-scan context. (location: page.html:9 - <link rel='canonical' href='https://mp3.cc/t/850351518-drake-ft-big-sean-kanye-west/'>)
brand impersonation
The site presents itself as MP3.cc (logo, branding, copyright notice '© 2017 – 2026 MP3.cc') while being served from hydr0.org. The entire UI including header logo, navigation, footer, and all links brand the site as mp3.cc, constituting impersonation of the mp3.cc service via a deceptive lookalike subdomain on hydr0.org. (location: page.html:5,33-36,671 - title tag, logo anchor, footer copyright)
malicious redirect
All audio file URLs point to fine.sunproxy.net, a third-party proxy/CDN domain not affiliated with the branded mp3.cc site. Audio play requests route through base64-obfuscated URLs on fine.sunproxy.net, which could serve malicious files, track users, or redirect to exploit pages. The domain 'sunproxy' is characteristic of proxy abuse infrastructure. (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,646 - data-url attributes pointing to fine.sunproxy.net)
obfuscated code
All 22 audio file download URLs embedded in data-url attributes use base64-encoded path components (e.g. 'YVlGMWFTTXN3M0VjVThHdEhvZHd2bG9QWDhzMDl6Skw0...'). The pre-scan context flagged 12 suspicious base64 blobs. These obfuscated URLs mask the true destination of audio streams routed through fine.sunproxy.net, preventing inspection of the actual resource being fetched. (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,646 - base64 segments in fine.sunproxy.net file paths)
social engineering
The page presents itself as a legitimate free MP3 download service using well-known celebrity artist names (Drake, Kanye West, Big Sean, Beyoncé) as bait to attract users. The hydr0.org domain name itself encodes artist names as a subdomain to appear in search results for these artists, driving organic traffic to the shadow domain and its third-party audio proxy infrastructure. (location: page.html:5 - title tag; metadata.json - domain field 'drake-ft-big-sean-kanye-west.hydr0.org')
curl https://api.brin.sh/domain/drake-ft-big-sean-kanye-west.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
drake-ft-big-sean-kanye-west.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.