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 scanned URL (2-chainz-feat-future.hydr0.org) is a subdomain that serves content impersonating MP3.cc. All canonical links, CSS, JS, and og:url tags point to mp3.cc, while audio files are served from fine.sunproxy.net — a third-party proxy/CDN not affiliated with mp3.cc. The site acts as a redirect/mirror that proxies the mp3.cc brand through an unrelated domain (hydr0.org), and all MP3 download URLs contain the 'Hydr0.org' branding embedded in the filenames. (location: page.html:9 (canonical href), page.html:228 (data-url attributes pointing to fine.sunproxy.net))
brand impersonation
The page fully impersonates MP3.cc (logo, branding, navigation, copyright notice '© 2017–2026 MP3.cc') while being hosted on hydr0.org — a completely different domain. The canonical tag and all internal links reference mp3.cc, but the actual serving domain is 2-chainz-feat-future.hydr0.org. This is a classic typosquat/mirror site impersonating a legitimate music service. (location: page.html:5 (title tag), page.html:11 (og:site_name), page.html:652 (footer copyright), page.html:9 (canonical pointing to mp3.cc))
malicious redirect
All audio file playback URLs use fine.sunproxy.net as a proxy to serve MP3 files. The subdomain 'fine.sunproxy.net' is a third-party proxy service with unknown ownership. Routing media through an uncontrolled proxy can be used to serve malware-laced files, track user behavior, or perform man-in-the-middle attacks on media downloads. The 12 suspicious base64 blobs flagged by Tier 2 are these encoded proxy URLs embedded in data-url attributes. (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 (all data-url attributes))
social engineering
The site presents itself as a free, legitimate MP3 download service (MP3.cc) but operates from an unaffiliated domain (hydr0.org) with the contact email hydrofm@yandex.com — a free Russian email provider, inconsistent with a legitimate established music service. Users are misled into believing they are on the official MP3.cc site and may trust downloads served through the sunproxy.net intermediary. (location: page.html:652 (footer: hydrofm@yandex.com), page.html:5 (title claiming MP3.cc identity))
curl https://api.brin.sh/domain/2-chainz-feat-future.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2-chainz-feat-future.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.