context safety score
A score of 36/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 served from domain b-o-b-ft-hayley-williams.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 metadata claiming site_name MP3.cc. The actual serving domain has no affiliation with mp3.cc and uses it as a facade. (location: page.html:5-14, canonical href and og:site_name tags)
malicious redirect
The canonical link tag and all internal navigation links redirect users to mp3.cc (a different domain), meaning the page is designed to funnel traffic from hydr0.org to mp3.cc. The pre-scan context also flags 1 redirect. Users landing on hydr0.org are silently treated as if they are on mp3.cc. (location: page.html:9, <link rel="canonical" href="https://mp3.cc/t/2880622762-b-o-b-ft-hayley-williams/">)
malicious redirect
All audio file play URLs route through fine.sunproxy.net, a third-party proxy domain unrelated to either hydr0.org or mp3.cc. Audio streams are proxied through an unknown intermediary (sunproxy.net) rather than served directly, enabling traffic interception, ad injection, or payload delivery via the audio pipeline. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 - data-url attributes pointing to fine.sunproxy.net)
hidden content
The data-url attributes on playlist play links contain long Base64-encoded strings (e.g. NDgwdkFuTUxJZ0tHbEJUVFE0QUZzO...) embedded as file path segments in the sunproxy.net URLs. These 12 suspicious base64 blobs (flagged in pre-scan) are opaque encoded parameters whose decoded content and purpose cannot be verified without execution, potentially encoding tracking identifiers, encrypted redirect targets, or exfiltration payloads. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 - Base64 path segments in fine.sunproxy.net URLs)
social engineering
The site presents itself as a free MP3 download service ("Download mp3 free, listen music online") impersonating the legitimate MP3.cc brand. This social engineering lures users seeking free music into interacting with an unofficial third-party domain (hydr0.org) that proxies all content through sunproxy.net, potentially exposing users to ads, tracking, or malicious payloads. (location: page.html:5 - title tag; page-text.txt:9 - MP3.cc branding; metadata.json - domain hydr0.org)
brand impersonation
The page footer displays copyright notice '© 2017 – 2026 MP3.cc' and contact email 'hydrofm@yandex.com', falsely attributing MP3.cc branding to the hydr0.org domain. The Yandex email address associated with the footer is inconsistent with a legitimate MP3.cc operation and suggests a Russian-operated clone site. (location: page.html:652 - footer copyright and email)
curl https://api.brin.sh/domain/b-o-b-ft-hayley-williams.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
b-o-b-ft-hayley-williams.hydr0.org currently scores 36/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.