context safety score
A score of 58/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 domain a-ap-rocky-x-a-ap-ferg-x-nicki-minaj.hydr0.org is a subdomain that serves content cloned from mp3.cc, impersonating that site. The canonical URL, OG tags, CSS/JS assets, and all internal links point to mp3.cc, indicating the subdomain acts as a redirect/proxy layer rather than the legitimate origin. The brin-context confirms 1 redirect was detected. (location: page.html:9 (canonical link), page.html:11-14 (OG meta tags), metadata.json (domain vs canonical mismatch))
brand impersonation
The subdomain hydr0.org hosts a full copy of the MP3.cc website, presenting itself as MP3.cc with its logo, branding, copyright notice ('© 2017 – 2026 MP3.cc'), and navigation. All MP3 file URLs are served through fine.sunproxy.net rather than mp3.cc, indicating the site proxies or repackages MP3.cc content under a different domain. This constitutes brand impersonation of MP3.cc. (location: page.html:5 (title tag), page.html:33-36 (logo), page.html:633 (copyright footer))
malicious redirect
All audio file download/play URLs use the third-party proxy domain fine.sunproxy.net with base64-encoded path parameters. Actual content is routed through this intermediary rather than the canonical mp3.cc domain. The base64 blobs (12 detected) in the data-url attributes encode opaque file paths. This proxy layer could intercept traffic, inject malware into downloads, or track users without disclosure. (location: page.html:228 (data-url on first playlist-play anchor), page.html:247, page.html:266, page.html:285 (and all subsequent playlist items — fine.sunproxy.net/file/NDgw...))
hidden content
The HTML contains 12 base64-encoded blobs embedded as data-url attributes on playlist play buttons. While individually they appear to be encoded MP3 file paths, the opaque encoding obscures the actual destination URLs, preventing users and security tools from inspecting where audio requests are sent. This aligns with the 12 suspicious base64 blobs flagged in the pre-scan context. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437 (data-url attributes on .playlist-play anchors))
curl https://api.brin.sh/domain/a-ap-rocky-x-a-ap-ferg-x-nicki-minaj.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
a-ap-rocky-x-a-ap-ferg-x-nicki-minaj.hydr0.org currently scores 58/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.