context safety score
A score of 49/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
malicious redirect
The scanned URL (https://2512324650.hydr0.org) presents itself as MP3.cc via canonical tag, OG tags, all internal links, and branding — while the actual serving domain is a numeric subdomain of hydr0.org. This is a classic cloaking/redirect setup: the domain impersonates MP3.cc to serve content and redirect traffic through a third-party proxy domain (hydr0.org), with the tier-1 scan confirming 1 redirect was detected. (location: page.html:9 (canonical href), metadata.json (domain: 2512324650.hydr0.org))
brand impersonation
The page fully impersonates the MP3.cc brand: the <title>, logo, canonical URL, og:site_name, og:url, og:image, all navigation links, footer links, and copyright notice all reference mp3.cc. The actual serving domain is 2512324650.hydr0.org, not mp3.cc. This constitutes deliberate brand impersonation of a legitimate music streaming/download site. (location: page.html:5,9,11,14,33,59,1179,1184)
malicious redirect
All audio file playback URLs route through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. Every 'play' link uses data-url pointing to fine.sunproxy.net/file/[base64-encoded-path]. This intermediary proxy intercepts all media requests, enabling traffic monitoring, data collection, or substitution of malicious payloads. (location: page.html:228,247,266 (and all subsequent playlist-play data-url attributes))
hidden content
Audio file URLs embed base64-encoded strings as file path tokens on fine.sunproxy.net (e.g., NDgwdkFuTUxJZ0tH...). These 12 suspicious base64 blobs (flagged in tier-2 scan) encode opaque routing parameters, obscuring the actual destination of media requests and preventing straightforward analysis of where user data and requests are sent. (location: page.html:228 (data-url attributes throughout playlist))
social engineering
The site mimics a well-known free MP3 download service (MP3.cc) to lure users into interacting with proxied content served from an unrelated domain (hydr0.org / fine.sunproxy.net). Users believing they are on MP3.cc are actually interacting with infrastructure controlled by the operator of hydr0.org, which could expose them to tracking, malware delivery, or unwanted redirects upon download. (location: page.html (overall page structure, footer: line 1184 — hydrofm@yandex.com contact using Yandex mail))
curl https://api.brin.sh/domain/2512324650.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2512324650.hydr0.org currently scores 49/100 with a suspicious 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.