context safety score
A score of 53/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted at beatmount-x-oneil.hydr0.org but all canonical URLs, links, assets, and download targets redirect to mp3.cc (a third-party MP3 piracy site). The domain hydr0.org acts as a proxy/mirror that funnels users to mp3.cc content. The brin-context notes 1 redirect detected. (location: page.html:9 - canonical href and throughout all href attributes)
malicious redirect
All audio file streaming URLs route through fine.sunproxy.net, a proxy/relay service that intercepts media requests. The base64-encoded path parameters in each URL (12 suspicious base64 blobs flagged) obscure the true file destinations routed through this intermediary proxy. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551 - data-url attributes on playlist-play anchors)
brand impersonation
The site beatmount-x-oneil.hydr0.org fully impersonates mp3.cc, reproducing its complete UI, branding, logo, stylesheets, and JavaScript from mp3.cc CDN assets. It presents itself as an official MP3.cc page while operating under a deceptive subdomain of hydr0.org. The page title explicitly includes 'MP3.cc' and the canonical link points to mp3.cc. (location: page.html:5 - title tag; page.html:9 - canonical link; page.html:11 - og:site_name; page.html:18-19 - external CSS/JS from mp3.cc)
hidden content
12 suspicious base64 blobs are embedded in the data-url attributes of audio play links. These base64 strings encode obfuscated URLs routing through fine.sunproxy.net and are not visible to users in the rendered page, concealing the true media proxy destinations. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - data-url base64 values in playlist-play anchor tags)
curl https://api.brin.sh/domain/beatmount-x-oneil.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
beatmount-x-oneil.hydr0.org currently scores 53/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.