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
malicious redirect
The scanned URL https://2502787582.hydr0.org redirects to and fully impersonates MP3.cc. The subdomain uses a numeric subdomain under hydr0.org (a lookalike/alternate domain for Hydr0) while serving content that presents itself as MP3.cc with canonical URLs, OG tags, logos, and footer copyright all pointing to mp3.cc. Users and agents arriving at the suspicious subdomain are silently served the MP3.cc interface without any indication they are on a different domain. (location: metadata.json: url=https://2502787582.hydr0.org; page.html line 9: canonical href=https://mp3.cc/; line 14: og:url=https://mp3.cc/)
brand impersonation
The page fully impersonates MP3.cc — including its title ('Most popular songs | Download mp3 free, listen music online - MP3.cc'), logo, site branding, canonical tag, Open Graph site_name, footer copyright '© 2017 – 2026 MP3.cc', and all navigation links — while being served from the unrelated domain 2502787582.hydr0.org. This constitutes brand impersonation of MP3.cc on a suspicious numeric subdomain. (location: page.html lines 5, 9, 11, 14, 33-36, 1184)
malicious redirect
All audio file streaming URLs route through the third-party proxy domain fine.sunproxy.net, which is entirely off-domain from both the hosting domain (hydr0.org) and the impersonated brand (mp3.cc). The base64-encoded path parameters in these URLs (12 suspicious base64 blobs flagged in Tier 2) obscure the actual file paths and could facilitate tracking, data exfiltration, or serving malicious payloads. The proxy sits between the user and media content without transparency. (location: page.html lines 228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437 (and all subsequent playlist entries): data-url=https://fine.sunproxy.net/file/<base64>/<filename_(Hydr0.org).mp3>)
hidden content
MP3 filenames embedded in the sunproxy.net URLs contain '(Hydr0.org)' as a tag (e.g., 'Maluma_-_Maluma_-_Corazon_(Hydr0.org).mp3'), revealing that the actual file serving infrastructure is branded as Hydr0.org — the same entity operating the scanning target domain — while the page presents the MP3.cc brand. This affiliation is not disclosed to visitors. (location: page.html: all data-url attributes, e.g. line 228: ...Maluma_-_Corazon_(Hydr0.org).mp3)
social engineering
The contact email in the footer is hydrofm@yandex.com — a Yandex (Russian email provider) address attributed to 'MP3.cc', inconsistent with a legitimate Western music streaming brand. Combined with the domain mismatch, this may be used to collect user feedback, DMCA complaints, or other sensitive communications under the false MP3.cc brand identity, redirecting them to the actual operator (Hydr0). (location: page.html line 1184: hydrofm@yandex.com; page-text.txt line 1087)
curl https://api.brin.sh/domain/2502787582.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2502787582.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.