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
brand impersonation
The page is served from subdomain 2167856495.hydr0.org but fully impersonates mp3.cc — using its title, logo, canonical URL (https://mp3.cc/), og:url, og:site_name, all internal links, and copyright notice. A user or agent browsing to hydr0.org would believe they are on the legitimate mp3.cc site. (location: page.html:5,9,11,14,33 — <title>, canonical, og:url, og:site_name, logo href all point to mp3.cc while actual domain is 2167856495.hydr0.org)
malicious redirect
The scanned URL (https://2167856495.hydr0.org) redirected to serve content that presents itself as mp3.cc. The brin-context notes 1 redirect. The canonical tag and all resource URLs reference mp3.cc, indicating the hydr0.org subdomain is functioning as a transparent proxy or redirect front for mp3.cc, masking the true origin from users and agents. (location: metadata.json / .brin-context.md — 1 redirect recorded; page.html:9 canonical href='https://mp3.cc/')
hidden content
All MP3 file download/play URLs route through a third-party proxy domain 'fine.sunproxy.net' with long Base64-encoded path tokens (12 suspicious base64 blobs flagged by Tier 2). These encoded tokens obfuscate the actual file destinations and could be used to track users, deliver malicious payloads, or bypass content filters. The real file targets are not visible to the user or agent. (location: page.html:228,247,266 etc. — data-url attributes on playlist-play anchors use https://fine.sunproxy.net/file/<base64token>/filename.mp3)
social engineering
The site presents itself as a free, legitimate MP3 download service (mp3.cc brand) but is hosted on a numerically-named subdomain of hydr0.org — a domain associated with the proxy infrastructure. Users are induced to download files through an obfuscated third-party proxy (fine.sunproxy.net), which obscures the true origin and chain of custody of downloaded files. This pattern is consistent with drive-by download or traffic-laundering schemes. (location: page.html — overall site structure; file downloads via fine.sunproxy.net proxy with base64-encoded tokens)
brand impersonation
MP3 filenames in the download URLs contain '(Hydr0.org)' branding (e.g., 'Maluma_-_Maluma_-_Corazon_(Hydr0.org).mp3'), indicating the files were rebranded or watermarked by hydr0.org, yet the site UI presents the mp3.cc brand. This dual-branding creates deliberate confusion about the true operator and origin of the content. (location: page.html:228 — data-url filename: Maluma_-_Maluma_-_Corazon_(Hydr0.org).mp3 (pattern repeated across all tracks))
curl https://api.brin.sh/domain/2167856495.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2167856495.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.