context safety score
A score of 56/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 at subdomain 2431673810.hydr0.org but all canonical URLs, links, CSS, JS, and branding point to mp3.cc. The canonical tag (line 9) explicitly redirects search engines and agents to https://mp3.cc/, and all navigation/download links resolve to mp3.cc. This is a classic shadow/mirror domain that redirects traffic to a different origin (mp3.cc) while operating under a separate unrelated domain (hydr0.org), consistent with traffic hijacking or SEO cloaking. (location: page.html:9 — <link rel='canonical' href='https://mp3.cc/'> and throughout all hrefs)
brand impersonation
The domain 2431673810.hydr0.org fully impersonates mp3.cc — copying its title, logo SVG, branding, OG tags (og:site_name='MP3.cc', og:url='https://mp3.cc/'), and all navigation. All static assets (CSS, JS) are loaded from mp3.cc directly. The operator identity is 'hydr0.org' but the page presents itself entirely as MP3.cc, deceiving users and automated agents into believing they are on the legitimate mp3.cc site. (location: page.html:5,9,11,14,18,19,33)
malicious redirect
All MP3 audio stream URLs route through fine.sunproxy.net rather than mp3.cc or hydr0.org. The data-url attributes on all play buttons point to https://fine.sunproxy.net/file/[base64-encoded-path], which is a third-party proxy domain not disclosed to users. This intermediary proxy could intercept playback, serve malware-laced files, or track users without consent. (location: page.html:228,247,266,285,304 etc. — data-url='https://fine.sunproxy.net/file/...' on all playlist-play elements)
hidden content
The Tier 2 scan flagged 12 suspicious base64 blobs. These correspond to the base64-encoded path components embedded in all fine.sunproxy.net streaming URLs (e.g., NDgwdkFuTUxJZ0tH...). While these appear to be encoded file routing tokens rather than injected payloads, they obfuscate the actual destination file paths and the underlying proxy routing logic, preventing transparent inspection of streamed content. (location: page.html:228,247,266,285,304 etc. — base64 segments in fine.sunproxy.net file URLs)
social engineering
The site presents pirated/unlicensed commercial music (Taylor Swift, Drake, Post Malone, etc.) for free download under the MP3.cc brand while operating from an unrelated hydr0.org subdomain. This is designed to attract users seeking free music via a trusted brand facade, exposing them to the third-party proxy (fine.sunproxy.net) and the redirect infrastructure of the hydr0.org operator. (location: page.html:399-413, 741-755 and throughout playlist — commercial artists offered for free download via unaffiliated domain)
curl https://api.brin.sh/domain/2431673810.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2431673810.hydr0.org currently scores 56/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.