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 2431981094.hydr0.org but all content, canonical URL, CSS, JS, and internal links point to mp3.cc. This is a transparent proxy/mirror setup: the numeric subdomain on hydr0.org silently serves the mp3.cc site, constituting a redirect/cloaking arrangement that could be used for traffic interception, SEO manipulation, or serving a modified version of the legitimate site to specific visitors. (location: page.html:9 - canonical href='https://mp3.cc/'; metadata.json domain=2431981094.hydr0.org)
brand impersonation
The page fully impersonates MP3.cc — reproducing its logo, title, branding ('MP3.cc'), copyright notice ('© 2017–2026 MP3.cc'), and all UI — while being served from the unrelated domain 2431981094.hydr0.org. This constitutes brand impersonation of the legitimate mp3.cc service. (location: page.html:5,9,35 - title and canonical mismatch with serving domain)
malicious redirect
All audio file play URLs route through fine.sunproxy.net (a third-party proxy domain unrelated to mp3.cc or hydr0.org), e.g. https://fine.sunproxy.net/file/NDgwd... This intermediary proxy intercepts all media requests and could log user activity, serve malicious files, or redirect users. (location: page.html:228,247,266 - data-url attributes on playlist-play anchors)
hidden content
The .brin-context.md scan flagged 12 suspicious base64 blobs. Inspection confirms all base64 content is contained in the sunproxy.net file path tokens (e.g. NDgwdkFuTUxJZ0tH...), which are obfuscated file identifiers used to route audio requests through the third-party proxy. While not standalone injected payloads, these opaque tokens obscure the actual backend file paths and destination, consistent with deliberate obfuscation of resource routing. (location: page.html:228,247,266 - data-url base64 path segments in fine.sunproxy.net URLs)
social engineering
The site presents itself as a free MP3 download service offering copyrighted music (Taylor Swift, Drake, Post Malone, etc.) for free download, which is used as a lure to attract users to a domain (hydr0.org) that impersonates and proxies another site. The free music offer is a classic social engineering lure to drive traffic through an untrusted intermediary. (location: page.html:224 - 'Most popular songs' playlist with download links; page-text.txt:131)
curl https://api.brin.sh/domain/2431981094.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2431981094.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.