context safety score
A score of 70/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 is hosted on a subdomain of hydr0.org but the canonical URL, all internal links, CSS, JS, and content point to mp3.cc. The page is effectively a mirror/clone of mp3.cc served from a different domain (hydr0.org), indicating a redirect/cloaking setup where the actual content domain differs from the serving domain. The brin-context confirms 1 redirect was detected. (location: page.html:9 - canonical href https://mp3.cc/t/2624158615-21-23-hz-quality-control-lil-baby-dababy-team-deaf-bonce/; metadata.json domain: 21-23-hz-quality-control-lil-baby-dababy-team-deaf-bonce.hydr0.org)
brand impersonation
The page is served from hydr0.org but fully impersonates mp3.cc by using mp3.cc branding, logo, stylesheet (mp3.cc/i/css/_main_min.css), JavaScript (mp3.cc/i/js/_main_min.js), and canonical tags. Users and agents accessing hydr0.org would believe they are on mp3.cc. The mp3 file download URLs embed '(Hydr0.org)' in the filename, indicating this is a deliberate off-brand distribution site mimicking mp3.cc. (location: page.html:5,18,19,33 - title and assets referencing MP3.cc; mp3 filenames contain Hydr0.org)
malicious redirect
All audio file streaming URLs route through fine.sunproxy.net, a third-party proxy domain, rather than directly from mp3.cc or a known CDN. This proxy intermediary could intercept requests, log user activity, or serve modified/malicious content. The base64-encoded path parameters in these URLs are opaque and cannot be verified without decoding. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494 - data-url attributes pointing to fine.sunproxy.net/file/)
hidden content
12 suspicious base64 blobs were flagged by Tier 2 scanning. These correspond to the opaque base64-encoded path segments in the fine.sunproxy.net audio file URLs (e.g. NDgwdkFuTUxJZ0tHbEJUVFE0QUZzeU50Smt3cnFoanUy...). While these appear to be encoded file routing tokens rather than injected payloads, their content is not transparently verifiable and could encode redirect targets or tracking parameters. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494 - base64 segments in fine.sunproxy.net URLs)
curl https://api.brin.sh/domain/21-23-hz-quality-control-lil-baby-dababy-team-deaf-bonce.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
21-23-hz-quality-control-lil-baby-dababy-team-deaf-bonce.hydr0.org currently scores 70/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.