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 served from a subdomain of hydr0.org (b-g-soulja-slim-feat-juvenile.hydr0.org) but fully impersonates MP3.cc, including its logo, branding, CSS/JS assets loaded from mp3.cc, canonical URL pointing to mp3.cc, and Open Graph site_name set to 'MP3.cc'. The actual serving domain is unrelated to mp3.cc, creating a deceptive clone of the legitimate MP3.cc service. (location: page.html:5-14, metadata.json domain field)
malicious redirect
All audio file URLs use a third-party proxy domain 'fine.sunproxy.net' rather than mp3.cc infrastructure. All download links route through mp3.cc but playback streams are proxied through fine.sunproxy.net, which intercepts audio traffic. The site also served a redirect (1 redirect noted in .brin-context.md) consistent with traffic interception. The canonical URL points to mp3.cc while the actual domain is hydr0.org, indicating the page is a redirected/proxied clone. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 (all data-url attributes))
brand impersonation
All MP3 filenames in the proxied URLs at fine.sunproxy.net contain '(Hydr0.org)' branding embedded in them (e.g., 'B.G._-_187.9_FM_(Hydr0.org).mp3'), indicating hydr0.org is rebranding/claiming content that belongs to or is associated with mp3.cc. The footer contact email 'hydrofm@yandex.com' is a Yandex address inconsistent with a legitimate MP3.cc property. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 (MP3 filenames in data-url), page.html:462 (footer email))
social engineering
The site presents itself as a free MP3 download service (MP3.cc clone) to lure users into downloading files through an unvetted proxy (fine.sunproxy.net). Users believe they are on the legitimate MP3.cc site but are actually on a third-party domain that intercepts all media traffic through its own proxy infrastructure, potentially delivering modified or malicious audio files or tracking user download behavior. (location: page.html:5 (title), page.html:228-451 (all playlist play/download links routed through fine.sunproxy.net))
curl https://api.brin.sh/domain/b-g-soulja-slim-feat-juvenile.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
b-g-soulja-slim-feat-juvenile.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.