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 subdomain 21-savage-metro-boomin-feat-young-thug.hydr0.org but all content, canonical links, CSS, JS, and navigation links point to mp3.cc. The canonical tag explicitly redirects search engines and agents to https://mp3.cc/t/1997508468-21-savage-metro-boomin-feat-young-thug/. This is a shadow/doorway domain that masquerades as mp3.cc content while operating under a different domain (hydr0.org), constituting a deceptive redirect pattern. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/1997508468-21-savage-metro-boomin-feat-young-thug/">)
brand impersonation
The site at hydr0.org fully impersonates mp3.cc by copying its branding, logo, CSS, JavaScript, and content structure. The page title, og:site_name, footer copyright, and all navigation links present the site as MP3.cc while being served from a different domain (hydr0.org). This is a deceptive brand impersonation of mp3.cc. (location: page.html:5,11,18,19,671 - title, og:site_name, stylesheet/script src, and footer copyright all reference mp3.cc while domain is hydr0.org)
malicious redirect
All MP3 audio files are served through a third-party proxy domain 'fine.sunproxy.net' using base64-encoded file paths. The 12 suspicious base64 blobs flagged in Tier 2 analysis correspond to these encoded URLs in data-url attributes. Users clicking play are routed through an intermediary proxy that could intercept connections, serve malware, or track users, rather than receiving files directly. (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 - all data-url attributes pointing to fine.sunproxy.net/file/<base64>)
social engineering
The site offers free MP3 downloads of copyrighted music, a common lure used on piracy/warez sites to attract users who then may be exposed to malicious ads, unwanted software, or further redirects. The contact email hydrofm@yandex.com (a Russian email provider) in the footer is notable given the overall deceptive domain structure. (location: page.html:671 - footer copyright with yandex.com email; page.html:228-660 - download links for copyrighted content)
curl https://api.brin.sh/domain/21-savage-metro-boomin-feat-young-thug.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
21-savage-metro-boomin-feat-young-thug.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.