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
brand impersonation
The page is hosted on a subdomain of hydr0.org (using a zero instead of the letter 'o' in 'hydro') but fully impersonates MP3.cc, including its logo, layout, CSS/JS assets loaded from mp3.cc, canonical URLs pointing to mp3.cc, and Open Graph metadata claiming og:site_name='MP3.cc'. The actual serving domain is 22-25-hz-quality-control-lil-baby-dababy-team-deaf-bonce.hydr0.org, not mp3.cc. (location: page.html:5, page.html:9-14, page.html:18-19, metadata.json domain field)
malicious redirect
All audio file playback URLs route through fine.sunproxy.net, a third-party proxy domain unrelated to either the hosting domain or the impersonated brand (mp3.cc). Audio streams are served via base64-encoded opaque tokens from this proxy, obscuring the true destination and enabling traffic interception or substitution. The brin-context notes 1 redirect was detected. (location: page.html:228, page.html:247, page.html:266 (and all data-url attributes across playlist items))
obfuscated code
All 15 audio stream URLs embed long base64-encoded blobs as path segments on fine.sunproxy.net (e.g., NDgwdkFuTUxJZ0tH...). These encode opaque parameters that cannot be inspected without decoding, consistent with the 12 suspicious base64 blobs flagged in the Tier 2 scan. This obscures the true file origin and any potential tracking or exfiltration parameters. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494 (all data-url attributes))
social engineering
The site presents itself as a legitimate free MP3 download service impersonating the established MP3.cc brand, enticing users to stream or download audio files through an unverified third-party proxy (fine.sunproxy.net). The combination of a lookalike domain (hydr0.org vs hydro), full brand cloning, and proxied downloads creates a deceptive experience designed to build false trust and drive traffic through attacker-controlled infrastructure. (location: page.html:5 (title), page.html:9 (canonical), page.html:519 (footer copyright claiming MP3.cc ownership), metadata.json)
curl https://api.brin.sh/domain/22-25-hz-quality-control-lil-baby-dababy-team-deaf-bonce.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
22-25-hz-quality-control-lil-baby-dababy-team-deaf-bonce.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.