context safety score
A score of 65/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
brand impersonation
The page is served from baddies-only-x-morry.hydr0.org but fully impersonates mp3.cc: the title reads 'MP3.cc', canonical URL points to mp3.cc, all CSS/JS assets load from mp3.cc, and all navigation links reference mp3.cc — creating a convincing fake mirror of the legitimate mp3.cc service. (location: page.html:5, page.html:9, page.html:14, page.html:18-19)
malicious redirect
The pre-scan context reports 1 redirect. The page canonical tag and OG URL both point away from the actual serving domain (hydr0.org) to mp3.cc, consistent with a redirect chain used to funnel users through an intermediary domain before landing on or proxying content from the legitimate site. (location: .brin-context.md:19, page.html:9)
obfuscated code
The audio play URL routes through fine.sunproxy.net with a long base64-encoded path token: 'NDgwdkFuTUxJZ0tH...UlY9'. Decoding reveals a further encrypted/obfuscated binary payload (not a plain URL), suggesting the actual media source is deliberately hidden behind a proxy with obfuscated routing — potentially to conceal traffic destination or enable dynamic payload substitution. (location: page.html:228)
curl https://api.brin.sh/domain/baddies-only-x-morry.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
baddies-only-x-morry.hydr0.org currently scores 65/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.