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
brand impersonation
The page is served from subdomain 4014692230.hydr0.org but fully impersonates MP3.cc — using MP3.cc's title, logo, canonical URL (https://mp3.cc/), Open Graph metadata, all internal links pointing to mp3.cc, and even the copyright notice '© 2017–2026 MP3.cc'. A user or AI agent visiting this URL would have no indication they are not on the legitimate mp3.cc domain. (location: page.html:5,9,11,14,33,1184 — <title>, canonical, og:url, og:site_name, logo href, footer copyright)
malicious redirect
The scanned URL https://4014692230.hydr0.org redirects (1 redirect recorded in .brin-context.md) and serves content cloned from mp3.cc. All media play links route through a third-party proxy domain 'fine.sunproxy.net' rather than mp3.cc's own infrastructure, silently routing audio file requests through an unrelated intermediary that could log, modify, or monetize traffic. (location: page.html:228,247,266 — data-url attributes pointing to https://fine.sunproxy.net/file/...)
brand impersonation
All 40+ MP3 file download URLs embed '(Hydr0.org)' in the filename (e.g., 'Maluma_-_Corazon_(Hydr0.org).mp3'), while the UI presents links pointing to mp3.cc. This reveals the files are served under the hydr0.org brand identity while the page pretends to be mp3.cc, indicating deliberate deceptive rebranding of media assets. (location: page.html:228,247,266,285 — data-url filenames containing (Hydr0.org).mp3)
malicious redirect
All audio file URLs use long base64-encoded path tokens served from fine.sunproxy.net, a proxy/relay service. These opaque tokens obscure the true file origin and allow the intermediary to perform traffic interception, ad injection, or redirect chaining without user awareness. 12 suspicious base64 blobs were flagged in pre-scan. (location: page.html:228 — https://fine.sunproxy.net/file/NDgwdkFuTUx... (and 39 similar instances))
social engineering
The site presents itself as a free MP3 download service for popular copyrighted songs (Taylor Swift, Drake, Post Malone, etc.) to attract high user traffic under false legitimacy, while actually operating from an unrelated numeric subdomain. This bait-and-switch approach exploits user trust in the MP3.cc brand to drive engagement with a rogue infrastructure. (location: page.html:224 — playlist of popular songs; page-text.txt:131)
curl https://api.brin.sh/domain/4014692230.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
4014692230.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.