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 scanned domain anuel-aa-feat-daddy-yankee-wisin-farruko-zion.hydr0.org serves content that impersonates MP3.cc (mp3.cc), with canonical URLs, CSS, JS, and all internal links pointing to mp3.cc. The actual serving domain is hydr0.org, a third-party subdomain. The pre-scan context confirms 1 redirect was detected. Users and AI agents browsing this URL are silently redirected to/from a different domain than what the content represents. (location: page.html:9 - canonical href and all resource links point to mp3.cc while served from hydr0.org)
brand impersonation
The page fully impersonates MP3.cc — including the MP3.cc logo, branding, title tag, OG tags (og:site_name=MP3.cc), footer copyright '2017-2026 MP3.cc', and all navigation/download links — while being served from the unrelated domain anuel-aa-feat-daddy-yankee-wisin-farruko-zion.hydr0.org. This is a complete brand clone designed to appear as the legitimate MP3.cc service. (location: page.html:5,11,33,652 - title, og:site_name, logo link, and footer all reference MP3.cc)
malicious redirect
All MP3 audio streaming/download links use the third-party proxy domain fine.sunproxy.net with base64-encoded file paths (data-url attributes). Users clicking play/download are routed through fine.sunproxy.net, an off-domain proxy not affiliated with MP3.cc. This proxy intercepts all media requests and could serve malware, track users, or harvest behavior. The 12 suspicious base64 blobs flagged in pre-scan correspond to these encoded URLs. (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 - all data-url attributes in playlist-play links)
hidden content
MP3 filenames embedded in the base64-encoded fine.sunproxy.net URLs contain the string '(Hydr0.org)' appended to every song filename (e.g., 'Anuel_AA_Ft._Daddy_Yankee_Wisin_Farruko_Y_Zion_Lennox_-_Sola_Official_Remix_(Hydr0.org).mp3'). This watermarks/tracks downloads through the proxy without user disclosure, embedding the hydr0.org brand into served files covertly. (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 - all encoded data-url filenames)
curl https://api.brin.sh/domain/anuel-aa-feat-daddy-yankee-wisin-farruko-zion.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
anuel-aa-feat-daddy-yankee-wisin-farruko-zion.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.