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 page is hosted on a subdomain of hydr0.org (baby-keem-feat-brent-faiyaz.hydr0.org) but all canonical links, CSS, JS, and navigation point to mp3.cc. The canonical tag explicitly redirects crawlers/agents to https://mp3.cc/t/545341224-baby-keem-feat-brent-faiyaz/. The site acts as a traffic-capturing mirror that funnels users to the real mp3.cc domain, consistent with the 1 redirect detected in Tier 2 signals. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/545341224-baby-keem-feat-brent-faiyaz/">)
brand impersonation
The domain baby-keem-feat-brent-faiyaz.hydr0.org impersonates the legitimate MP3.cc service. The page clones MP3.cc's branding, logo, CSS, and JavaScript entirely from mp3.cc's CDN (mp3.cc/i/css/_main_min.css, mp3.cc/i/js/_main_min.js), presenting the hydr0.org domain as if it were the official MP3.cc site. The footer even displays the mp3.cc copyright notice and a contact email (hydrofm@yandex.com). (location: page.html:5,18,19,671)
malicious redirect
All audio file play URLs route through a third-party proxy domain fine.sunproxy.net using base64-encoded path parameters. These 12 base64 blobs (matching the 'Suspicious base64 blobs: 12' Tier 2 signal) obfuscate the actual file destinations. The proxy domain sunproxy.net is not affiliated with mp3.cc and intercepts all media requests, enabling traffic interception, tracking, or payload delivery. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - data-url attributes pointing to fine.sunproxy.net/file/<base64>)
hidden content
The deceptive link flagged in Tier 2 (deceptive link count: 1) corresponds to the sidebar link to looz.net styled with class 'z__important' and target='_blank', which opens an external radio site in a new tab without clear user indication that it leads off-domain. This is visually presented as a standard genre navigation item but is an outbound affiliate/partner link. (location: page.html:204 - <a href="https://looz.net/" class="z__important no-ajax" target="_blank">)
curl https://api.brin.sh/domain/baby-keem-feat-brent-faiyaz.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
baby-keem-feat-brent-faiyaz.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.