context safety score
A score of 41/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
encoded payload
suspicious base64-like blobs detected in page content
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is served from the subdomain chris-brown-party-playlist.hydr0.org but all canonical URLs, assets, links, and branding point to mp3.cc. The canonical tag explicitly redirects to https://mp3.cc/t/2315342111-chris-brown-party-playlist/. This subdomain acts as a shadow/proxy copy of the mp3.cc site, masquerading under the hydr0.org domain. The Tier 2 scan confirmed 1 redirect. Users and agents landing on this domain are silently proxied through a third-party domain rather than the legitimate mp3.cc origin. (location: page.html:9 - canonical href; .brin-context.md: Redirects: 1)
brand impersonation
The page fully impersonates the MP3.cc brand — including its logo, site name, navigation, footer copyright '© 2017–2026 MP3.cc', and all internal links pointing to mp3.cc — while being served from the unrelated domain hydr0.org. The site title, og:site_name, and all UI elements present the page as if it were the legitimate MP3.cc website, but it is hosted on a different domain entirely. (location: page.html:5,11,34-36,671 - title, og:site_name, logo, footer)
malicious redirect
All audio file playback URLs use the domain fine.sunproxy.net rather than mp3.cc or hydr0.org. Every 'play' link routes audio streaming through this third-party proxy (fine.sunproxy.net/file/...), which intercepts audio requests and could be used for traffic monitoring, ad injection, or serving malicious payloads in place of audio files. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627,646 - data-url attributes)
hidden content
The base64-encoded path segments embedded in all fine.sunproxy.net audio URLs (12 suspicious base64 blobs flagged by Tier 2) are opaque encoded parameters. While individually they may be legitimate token/auth parameters for proxied file access, their consistent use across all 22 track URLs through a third-party proxy domain warrants attention as they obscure the actual file destinations and could encode tracking or exfiltration parameters. (location: page.html:228,247,266 et al. - data-url base64 path segments in fine.sunproxy.net URLs; .brin-context.md: Suspicious base64 blobs: 12)
social engineering
The page presents free MP3 downloads of copyrighted commercial music (Chris Brown, Pitbull, etc.) as a legitimate service. This is a lure commonly used to attract users to piracy proxy sites that may serve malicious ads, require account creation, or redirect to phishing pages. The footer contact email hydrofm@yandex.com uses a free Russian email provider, inconsistent with a legitimate commercial music distribution service. (location: page.html:671 - footer hydrofm@yandex.com; page.html:224 - Chris Brown Party Playlist download page)
curl https://api.brin.sh/domain/chris-brown-party-playlist.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
chris-brown-party-playlist.hydr0.org currently scores 41/100 with a suspicious verdict and low 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.