context safety score
A score of 34/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 b-o-b-and-hayley-williams.hydr0.org but fully impersonates MP3.cc, including its logo, branding, canonical URL (https://mp3.cc/t/593342137-b-o-b-and-hayley-williams/), Open Graph metadata (og:site_name=MP3.cc), stylesheets, and scripts all sourced from mp3.cc. The subdomain hydr0.org is a separate domain masquerading as the legitimate MP3.cc service. (location: page.html:5-14, line 9 (canonical href), line 11 (og:site_name), lines 18-19 (external assets from mp3.cc))
malicious redirect
The canonical link tag points to https://mp3.cc/t/593342137-b-o-b-and-hayley-williams/ on a different domain (mp3.cc) from the serving domain (hydr0.org). The brin-context notes 1 detected redirect. Users and crawlers arriving at hydr0.org are served content that declares its canonical identity as mp3.cc, which is deceptive and constitutes a redirect/cloaking mechanism used to funnel traffic under a false identity. (location: page.html:9 (canonical tag), .brin-context.md (Redirects: 1))
hidden content
All 12 MP3 audio file download URLs contain long base64-encoded path segments within the fine.sunproxy.net domain (e.g. NDgwdkFuTUxJZ0tH...). These base64 blobs obfuscate the actual file routing tokens passed to a third-party proxy server (fine.sunproxy.net), which is not disclosed to users. The brin-context flags 12 suspicious base64 blobs. While not classic hidden DOM content, the opaque encoded routing through an undisclosed proxy constitutes hidden content/obfuscation. (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 (data-url attributes))
malicious redirect
All playback audio is routed through fine.sunproxy.net, a third-party proxy domain, rather than being served directly. This intermediary proxy intercepts all audio streaming requests and could be used to track users, serve malware payloads, or redirect downloads. Users are not informed of this proxy in the UI. (location: page.html: all data-url attributes on playlist-play anchors (e.g. line 228))
brand impersonation
The footer copyright reads '© 2017 – 2026 MP3.cc' and includes contact email hydrofm@yandex.com, reinforcing the impersonation of the legitimate MP3.cc brand while the page is served from hydr0.org. The contact address uses a Yandex email rather than any official MP3.cc domain, indicating the operators are distinct from the real MP3.cc. (location: page.html:652)
social engineering
The deceptive link flagged in brin-context (Deceptive link count: 1) corresponds to the sidebar link to https://looz.net/ styled with class 'z__important' and labeled 'Online Radio', which is an off-brand external site embedded among legitimate genre navigation links with no disclosure that it is a third-party site. This could lure users to an unrelated external destination. (location: page.html:204-215 (looz.net link with class z__important))
curl https://api.brin.sh/domain/b-o-b-and-hayley-williams.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
b-o-b-and-hayley-williams.hydr0.org currently scores 34/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.