context safety score
A score of 76/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
malicious redirect
The page is served from subdomain bushido-saad.hydr0.org but all canonical links, assets (CSS/JS), and navigation point to mp3.cc. The canonical tag explicitly redirects to https://mp3.cc/t/2890054416-bushido-saad/, and the brin-context reports 1 redirect. This subdomain acts as a transparent proxy/mirror of mp3.cc content, which is a common pattern for typosquatting, SEO abuse, or cloaking — serving different content to bots vs. users (user-agent diff ratio: 0.10). (location: page.html:9 (canonical), metadata.json (domain: bushido-saad.hydr0.org))
brand impersonation
The site at bushido-saad.hydr0.org fully replicates the MP3.cc brand, including logo, title tag ('MP3.cc'), copyright notice '© 2017 – 2026 MP3.cc', and all navigation/content. It presents itself as MP3.cc while operating on an unrelated third-party domain (hydr0.org). This constitutes brand impersonation of MP3.cc on an independently operated subdomain. (location: page.html:5 (title), page.html:652 (copyright footer), page.html:33 (logo link))
malicious redirect
All MP3 audio files are proxied through fine.sunproxy.net rather than served directly from mp3.cc or the hosting domain. The data-url attributes for all playlist items point to fine.sunproxy.net/file/... with base64-encoded path tokens. This third-party proxy service (sunproxy.net) intercepts all audio download requests, enabling potential traffic monitoring, content substitution, or malware delivery via the proxied file endpoint. The brin-context flags 12 suspicious base64 blobs corresponding to these encoded proxy URLs. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627 (data-url attributes on playlist-play links))
curl https://api.brin.sh/domain/bushido-saad.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
bushido-saad.hydr0.org currently scores 76/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.