context safety score
A score of 43/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
malicious redirect
The scanned URL beastie-boys-x-q-tip.hydr0.org redirects to content served under the mp3.cc domain (canonical URL and all asset links point to mp3.cc), making the subdomain act as a transparent proxy/redirect layer. The hydr0.org domain is not the canonical host for this content, indicating deceptive domain usage to serve third-party content under a different origin. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/1545265996-beastie-boys-x-q-tip/">)
brand impersonation
The site presents itself as MP3.cc (title, logo, branding, copyright footer '© 2017 – 2026 MP3.cc') while being served from hydr0.org — a different domain entirely. This constitutes brand impersonation: a third-party domain mimicking or proxying the MP3.cc brand without being the legitimate MP3.cc site, potentially deceiving users and AI agents into trusting the content as originating from MP3.cc. (location: page.html:5,671 - title tag and footer copyright)
malicious redirect
All MP3 audio files are served through fine.sunproxy.net, a third-party proxy domain, with filenames appended with '(Hydr0.org).mp3'. Users/agents clicking play or download are directed to fine.sunproxy.net rather than mp3.cc or hydr0.org. This sunproxy.net intermediary is an unverified third-party file proxy that intercepts media requests, constituting a suspicious redirect chain for file delivery. (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 pointing to fine.sunproxy.net)
obfuscated code
All 22 audio file URLs contain long Base64-encoded path segments within fine.sunproxy.net URLs (e.g. 'NDgwdkFuTUxJZ0tH...'). These encoded strings obfuscate the actual file locations and route all media through an opaque proxy. The pre-scan context flagged 12 suspicious base64 blobs consistent with this finding. While this may be a CDN token scheme, it prevents transparent inspection of destination resources. (location: page.html:228 onward - all data-url attributes on playlist-play anchors)
curl https://api.brin.sh/domain/beastie-boys-x-q-tip.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
beastie-boys-x-q-tip.hydr0.org currently scores 43/100 with a suspicious verdict and low 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.