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
brand impersonation
The page is hosted on subdomain b-o-b-feat-hayley-williams.hydr0.org but fully impersonates mp3.cc, including its logo, branding, navigation, canonical URLs, og:site_name, og:url, og:image, CSS/JS assets, and footer copyright — all pointing to mp3.cc. The actual serving domain (hydr0.org) is distinct from the brand being impersonated (mp3.cc). (location: page.html:5-14, page.html:33-36, page.html:652)
malicious redirect
The canonical link tag and all Open Graph URL metadata redirect users and crawlers to mp3.cc rather than the actual serving domain (hydr0.org). This creates a deceptive redirect signal: the page presents itself as residing at mp3.cc while actually served from a different domain. (location: page.html:9, page.html:14)
malicious redirect
All audio file download/play links route through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc or hydr0.org. The base64-encoded URLs passed to this proxy obscure the final file destinations, creating an untrusted intermediary that could serve malicious payloads or track user activity. (location: page.html:228, page.html:247, page.html:266 (and all playlist data-url attributes))
hidden content
Twelve suspicious base64 blobs were flagged by the pre-scan. These correspond to the obfuscated file path tokens embedded in the fine.sunproxy.net URLs (e.g., NDgwdkFuTUxJZ0tHbEJUVFE0QUZz...). While these appear to be encoded file routing tokens rather than injected payloads, they obscure the true destination of all media file requests. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437 (all data-url attributes))
social engineering
The site presents itself as a legitimate free MP3 download service impersonating the brand mp3.cc, which may deceive users into downloading files from an untrusted third-party proxy (fine.sunproxy.net) believing them to be sourced from the legitimate mp3.cc service. (location: page.html:5, page.html:33-36, page.html:652)
curl https://api.brin.sh/domain/b-o-b-feat-hayley-williams.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
b-o-b-feat-hayley-williams.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.