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 hosted on 'backstret-boys-i-want-it-that-way.hydr0.org' (note typo: 'backstret' instead of 'backstreet') but the canonical URL, all internal links, CSS, JS, and branding all point to 'mp3.cc'. The subdomain acts as a redirect/mirror for mp3.cc content, with one redirect detected in the pre-scan context. Users navigating to the typosquat domain are silently served mp3.cc content, potentially enabling traffic hijacking or future content substitution. (location: page.html:9 (canonical), .brin-context.md (Redirects: 1))
brand impersonation
The domain 'backstret-boys-i-want-it-that-way.hydr0.org' is a typosquat of 'Backstreet Boys' (missing 'e' in 'Backstreet') combined with the song title. The page fully impersonates the mp3.cc brand including its logo, styling, and content. This pattern is consistent with SEO manipulation or brand-name abuse to attract users searching for the legitimate band or mp3.cc. (location: metadata.json (domain), page.html:5 (title), page.html:33-36 (MP3.cc logo and branding))
malicious redirect
All audio file playback URLs route through 'fine.sunproxy.net', a third-party proxy domain not affiliated with mp3.cc. The base64-encoded path parameters (12 suspicious blobs flagged) obfuscate the actual file destinations. Users clicking play have their requests proxied through an opaque intermediary that could log, redirect, or substitute content. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570 (data-url attributes))
hidden content
The base64-encoded segments in the sunproxy.net file URLs (12 flagged blobs) are opaque and cannot be verified as benign without decoding and resolving. They may encode real file paths or could contain redirect/tracking parameters designed to obscure final destinations from static analysis. (location: page.html: multiple data-url attributes on playlist-play anchors (lines 228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570))
curl https://api.brin.sh/domain/backstret-boys-i-want-it-that-way.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
backstret-boys-i-want-it-that-way.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.