context safety score
A score of 63/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 2907581383.hydr0.org but all canonical URLs, assets, and links point to mp3.cc. The canonical tag (<link rel="canonical" href="https://mp3.cc/">) and og:url both reference mp3.cc, indicating this subdomain is serving a full clone of mp3.cc. A redirect was detected (Tier 1: Redirects: 1), suggesting traffic is being funneled through a numeric subdomain before landing on or mirroring the mp3.cc brand. (location: page.html:9, page.html:14, .brin-context.md (Redirects: 1))
brand impersonation
The site at 2907581383.hydr0.org fully replicates the visual identity, content, branding, logo, and navigation of mp3.cc — a legitimate music download site — including its title tag, og:site_name, logo SVG, CSS/JS assets loaded directly from mp3.cc, and all song download links pointing to mp3.cc. The hosting domain (hydr0.org) is unrelated to mp3.cc, and the page impersonates mp3.cc without authorization. MP3 file URLs embed '(Hydr0.org)' in filenames (e.g., Maluma_-_Maluma_-_Corazon_(Hydr0.org).mp3), indicating the operator is the hydr0.org entity rebranding mp3.cc content as their own. (location: page.html:5,9,11,14,18,19,33; audio file data-url attributes (e.g., line 228))
malicious redirect
All audio playback URLs route through fine.sunproxy.net, a third-party proxy domain unaffiliated with mp3.cc. Every 'data-url' for audio playback points to https://fine.sunproxy.net/file/<base64_token>/filename.mp3. This intermediary proxy could intercept requests, serve malicious files, track users, or redirect to exploit pages. The 12 suspicious base64 blobs flagged in Tier 2 correspond to these encoded proxy tokens. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 (and all subsequent playlist-play data-url attributes))
hidden content
The page contains a section with class 'Other listen' populated with a dense block of search terms/keywords (e.g., 'phil harris dj suziq boogie nights', 'alicia keys so done', etc.) that appears to be SEO keyword stuffing injected into what renders as secondary/auxiliary content. This content is rendered in a separate section likely not prominently displayed and serves to manipulate search engine indexing rather than provide user value. (location: page-text.txt:1099-1101)
curl https://api.brin.sh/domain/2907581383.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2907581383.hydr0.org currently scores 63/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.