context safety score
A score of 52/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
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted on big-blessing-ft-drake.hydr0.org but uses a canonical URL pointing to mp3.cc/t/1217958712-big-blessing-ft-drake/ and all navigation/download links redirect to mp3.cc. The subdomain acts as a redirect/proxy front for mp3.cc, a known piracy/copyright-infringing MP3 download site. The redirect detected in Tier 2 pre-scan confirms this pattern. (location: page.html:9 - canonical link; page.html:228-229 - all media links)
brand impersonation
The page at big-blessing-ft-drake.hydr0.org presents itself with the full MP3.cc branding, logo, site name, copyright notice ('© 2017–2026 MP3.cc'), and contact email (hydrofm@yandex.com), while being served from a different domain (hydr0.org subdomain). This constitutes impersonation of the MP3.cc brand from an unaffiliated or shadow domain. The use of 'hydr0' (zero substituting 'o') in both the domain and embedded MP3 filenames (e.g., 'Hydr0.org' in filenames) suggests this is a deliberate alternate-domain operation. (location: page.html:5 - title tag; page.html:671 - footer copyright; page.html:228 - MP3 filenames containing Hydr0.org)
social engineering
The site offers free MP3 downloads of copyrighted music by well-known artists (Drake, Big Sean, Kanye West, 2 Chainz, DJ Khaled) without authorization, using the lure of free music to drive traffic. Download links route through fine.sunproxy.net, a third-party proxy/CDN whose trustworthiness is unknown and which could serve malicious payloads. (location: page.html:229 - download links via mp3.cc; page.html:228 - play URLs via fine.sunproxy.net)
malicious redirect
All audio file URLs route through fine.sunproxy.net/file/ with long base64-encoded path parameters. This third-party proxy is not the hosting domain and represents an opaque redirect chain for media delivery. The 12 suspicious base64 blobs flagged in Tier 2 correspond to these encoded file paths. While the encoding appears to be URL routing tokens rather than injection payloads, the use of an intermediary proxy domain for all file delivery is a common technique in piracy and potentially malware distribution infrastructure. (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 on playlist-play anchors)
curl https://api.brin.sh/domain/big-blessing-ft-drake.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
big-blessing-ft-drake.hydr0.org currently scores 52/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.