context safety score
A score of 48/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
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
Page is served from apollo-brown-ras-kass-feat-4-rax.hydr0.org but presents itself entirely as MP3.cc: the page title reads 'MP3.cc', the logo links to https://mp3.cc/, all CSS/JS assets are loaded from mp3.cc, the canonical URL points to mp3.cc, and the footer copyright reads '© 2017 – 2026 MP3.cc'. The hydr0.org domain is operating a mirror/clone of the mp3.cc brand without being mp3.cc, constituting brand impersonation. (location: page.html:5, page.html:9, page.html:18-19, page.html:33, page.html:557)
malicious redirect
The page includes a redirect (1 redirect flagged in pre-scan) from the hydr0.org subdomain to content that presents as mp3.cc. The canonical tag (line 9) points to mp3.cc while the actual serving domain is hydr0.org, indicating a deceptive domain redirect pattern where users landing on hydr0.org are served a full mp3.cc clone. Additionally, all 16 audio play URLs route through fine.sunproxy.net, a third-party proxy domain, meaning media requests are silently redirected through an intermediary not disclosed to the user. (location: page.html:9, page.html:228, page.html:247, metadata.json (redirects: 1))
social engineering
MP3 filenames embedded in the sunproxy.net download URLs contain '(Hydr0.org)' branding (e.g., 'Ras_Kass_Apollo_Brown_feat._4_Rax_-_Roses_(Hydr0.org).mp3'), indicating the operator is embedding their own domain into redistributed copyrighted music files. This is a traffic-building and attribution manipulation tactic to drive users back to the hydr0.org ecosystem, and the deceptive link to looz.net (flagged as 1 deceptive link in pre-scan) is styled identically to legitimate genre navigation links, making it indistinguishable from on-site navigation. (location: page.html:204, page.html:228, page.html:247, page.html:266)
curl https://api.brin.sh/domain/apollo-brown-ras-kass-feat-4-rax.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
apollo-brown-ras-kass-feat-4-rax.hydr0.org currently scores 48/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.