context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
7 deceptive links where visible host does not match destination host
brand impersonation
The page is served from a-ben.hydr0.org, a subdomain of hydr0.org (a typosquatted/lookalike domain for hydro.org or similar), while fully impersonating the MP3.cc brand: using its logo, CSS, JS, canonical URLs, og:site_name, og:url, and copyright notice. The actual canonical URL points to mp3.cc, but the content is hosted on a different domain entirely, constituting brand impersonation of MP3.cc. (location: page.html:<title>, <link rel='canonical'>, og:url, og:site_name — all referencing mp3.cc while served from a-ben.hydr0.org)
malicious redirect
The page sets a canonical href to https://mp3.cc/t/1113749548-a-ben/ while being served from https://a-ben.hydr0.org. This, combined with the brin-context noting 1 redirect, indicates the page redirects or represents content from mp3.cc hosted on a third-party domain (hydr0.org), which is consistent with traffic hijacking or content scraping with redirect behavior. (location: page.html:9 — <link rel='canonical' href='https://mp3.cc/t/1113749548-a-ben/'>)
malicious redirect
All audio file download/play URLs route through fine.sunproxy.net, a third-party proxy domain unaffiliated with the displayed MP3.cc brand. This proxy intercepts user requests for media files, potentially logging user activity, IP addresses, and browser fingerprints. The base64-encoded path parameters (12 suspicious blobs flagged by Tier 2) in each sunproxy URL obfuscate the final destination of requests. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627 — data-url attributes pointing to fine.sunproxy.net)
hidden content
The page contains 12 suspicious base64-encoded blobs embedded as opaque path segments within fine.sunproxy.net file URLs. While these appear to be encoded file tokens/keys for the proxy, they are not human-readable and cannot be independently verified without decoding, making them a vector for obfuscated payload delivery or tracking parameters. (location: page.html — data-url attributes, e.g. line 228: NDgwdkFuTUxJZ0tHbEJUVFE0QUZzMjJBeit2dnUvakFxNHBYWVA1cWR6... (repeated across all 22 playlist items))
social engineering
The page presents as a legitimate MP3 download service (MP3.cc) with familiar branding, genre navigation, and music listings to build trust and encourage users to click play/download links that actually route through the third-party proxy fine.sunproxy.net. This creates a false sense of legitimacy to induce users to interact with proxied content. (location: page.html — overall page layout, header logo, footer copyright referencing MP3.cc while served from hydr0.org)
curl https://api.brin.sh/domain/a-ben.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
a-ben.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.