context safety score
A score of 68/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
malicious redirect
The page is served from bad-boy-timz-bnxn.hydr0.org but all canonical links, assets (CSS/JS), and navigation point to mp3.cc. The subdomain acts as a mirror/proxy that redirects or impersonates the mp3.cc brand without being the legitimate domain. The brin-context notes 1 redirect was detected. (location: metadata.json:url, page.html:9 (canonical href), page.html:18-19 (external asset loads))
brand impersonation
The site at bad-boy-timz-bnxn.hydr0.org fully clones the MP3.cc interface including logo, branding, CSS, JS, and canonical tags pointing back to mp3.cc. The page title and og:site_name both declare 'MP3.cc' while the actual serving domain is hydr0.org — a clear impersonation of the legitimate mp3.cc service. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:14 (og:url), page.html:33-36 (logo linking to mp3.cc))
malicious redirect
MP3 file playback URLs route through fine.sunproxy.net with base64-encoded path parameters. This third-party proxy (sunproxy.net) intercepts media requests and the encoded blobs match the 3 'suspicious base64 blobs' flagged in the pre-scan context. Users clicking play have their requests routed through an opaque proxy rather than the canonical mp3.cc infrastructure. (location: page.html:228 (data-url fine.sunproxy.net), page.html:247, page.html:266; .brin-context.md:26 (suspicious base64 blobs: 3))
social engineering
The site presents itself as a free MP3 download/streaming service, a common lure to get users to click download links that route through third-party proxy infrastructure (fine.sunproxy.net / sunproxy.net). The filenames in the proxied URLs include 'Hydr0.org' branding embedded in the MP3 filename strings, suggesting deliberate watermarking/attribution to the piracy operation. (location: page.html:228 (Bad_Boy_Timz_EMPIRE_-_Faya_(Hydr0.org).mp3), page.html:247, page.html:266)
curl https://api.brin.sh/domain/bad-boy-timz-bnxn.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bad-boy-timz-bnxn.hydr0.org currently scores 68/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.