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 page is hosted at subdomain 2178505071.hydr0.org but presents itself entirely as MP3.cc, with canonical URL, og:url, all links, and branding pointing to mp3.cc. The numeric subdomain on hydr0.org is a cloaking/redirect layer proxying the legitimate MP3.cc site. Users and agents accessing this URL are transparently served content from mp3.cc while interacting with an unrelated third-party domain. (location: metadata.json: url=https://2178505071.hydr0.org; page.html line 9: canonical href=https://mp3.cc/; page.html line 14: og:url=https://mp3.cc/)
brand impersonation
The site at 2178505071.hydr0.org fully impersonates MP3.cc, reproducing its title, logo, branding, content, and all navigation links verbatim. The domain hydr0.org is unrelated to mp3.cc, and the numeric subdomain pattern is characteristic of infrastructure used for traffic interception or ad-injection proxies. (location: page.html lines 5, 9, 11, 14, 33-36: title and all branding assets reference MP3.cc while domain is hydr0.org)
malicious redirect
All audio file playback URLs route through fine.sunproxy.net rather than mp3.cc or any legitimate CDN. The domain sunproxy.net is a third-party proxy/intermediary that intercepts all media streaming requests. This could be used for traffic monitoring, ad injection, or serving malicious payloads in place of expected audio files. (location: page.html lines 228, 247, 266, 285, 304, 323, 342 etc.: data-url attributes all point to https://fine.sunproxy.net/file/...)
hidden content
All audio file URLs contain long base64-encoded path segments (12 flagged by Tier 2 scanner) embedded within fine.sunproxy.net file paths. These blobs encode opaque parameters passed to the proxy, obscuring the true destination and any tracking or payload data from cursory inspection. Example: NDgwdkFuTUxJZ0tHbEJUVFE0QUZzNUtmT3Q5UlZlNlAveTNlSGJkYkhO... (location: page.html lines 228, 247, 266, 285 etc.: data-url base64 path segments in fine.sunproxy.net URLs)
brand impersonation
MP3 filenames served via the sunproxy CDN contain the string '(Hydr0.org)' appended to each filename (e.g., Maluma_-_Maluma_-_Corazon_(Hydr0.org).mp3), indicating the files have been rebranded/watermarked by the hydr0.org operator rather than served directly from the legitimate MP3.cc source. (location: page.html lines 228, 247, 266, 285, 304 etc.: all .mp3 filenames contain (Hydr0.org) suffix)
curl https://api.brin.sh/domain/2178505071.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2178505071.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.