context safety score
A score of 48/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-kendrick-lamar.hydr0.org) but the canonical URL and all internal links point to mp3.cc. This indicates the hydr0.org domain is acting as a redirect/proxy layer that routes users to mp3.cc content, obscuring the true origin of the site from users and crawlers. (location: page.html:9 - canonical href='https://mp3.cc/t/3642002000-baby-keem-kendrick-lamar/' vs actual URL https://baby-keem-kendrick-lamar.hydr0.org)
brand impersonation
The site at hydr0.org fully impersonates the MP3.cc brand: uses the MP3.cc logo, title, copyright notice ('© 2017 – 2026 MP3.cc'), and loads all CSS/JS assets directly from mp3.cc. The domain hydr0.org is not mp3.cc, so the site is presenting itself as a known brand from a different domain, which is a form of brand impersonation or unauthorized mirroring. (location: page.html:5,18,19,671 - title 'MP3.cc', assets from mp3.cc, copyright 'MP3.cc', contact email hydrofm@yandex.com)
social engineering
The site offers free MP3 downloads of copyrighted music (Kendrick Lamar, Baby Keem, etc.) through an unofficial third-party proxy domain (hydr0.org), which may be used to attract users into downloading files from untrusted third-party proxy servers (fine.sunproxy.net) under the guise of a legitimate music service. (location: page.html:228,247,266 - data-url attributes pointing to fine.sunproxy.net for all audio file downloads)
malicious redirect
All audio file playback URLs resolve through fine.sunproxy.net, a third-party proxy service, rather than directly from mp3.cc or the hosting domain. This intermediary proxy could intercept, log, or substitute file downloads without user awareness. The base64-encoded path parameters (12 suspicious blobs flagged by Tier 2 scan) in each sunproxy URL obfuscate the true file destination. (location: page.html:228 - data-url='https://fine.sunproxy.net/file/NDgwd...' (and all subsequent playlist-play elements))
curl https://api.brin.sh/domain/baby-keem-kendrick-lamar.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
baby-keem-kendrick-lamar.hydr0.org currently scores 48/100 with a suspicious 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.