context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted on a subdomain of hydr0.org (eminem-feat-2pac-t-i-eazy-e-dr-dre-biggie-small-proof-the-game.hydr0.org) but contains a canonical URL pointing to mp3.cc, all internal links point to mp3.cc, and all resources (CSS, JS, images) are loaded from mp3.cc. The page is functionally a mirror/proxy of mp3.cc served from a different domain, redirecting user traffic and engagement to the third-party mp3.cc domain. (location: page.html:9 - canonical href; page.html:18-19 - external resource loading from mp3.cc)
brand impersonation
The domain hydr0.org hosts a page that fully impersonates mp3.cc, reproducing its branding (logo, site name 'MP3.cc'), layout, navigation, and content. The page title, og:site_name, copyright footer, and all links all reference MP3.cc, while the actual serving domain is hydr0.org. Users interacting with this page may believe they are on the legitimate mp3.cc site. (location: page.html:5 - title tag; page.html:11 - og:site_name; page.html:33-36 - logo linking to mp3.cc; page.html:671 - footer copyright MP3.cc)
malicious redirect
All MP3 audio file download/play URLs resolve through fine.sunproxy.net, a third-party proxy domain. The long base64-encoded path parameters in these URLs (12 suspicious base64 blobs flagged in pre-scan) route media requests through an intermediary server that could intercept traffic, track users, or serve altered content. Users clicking play or download are routed through fine.sunproxy.net rather than directly to mp3.cc infrastructure. (location: page.html:228 - data-url attribute; page.html:247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627,646 - all playlist-play data-url attributes pointing to fine.sunproxy.net)
hidden content
The HTML comment on line 224 contains a redundant inline comment echoing the page search query: '<!-- "eminem feat 2pac t i eazy e dr dre biggie small proof the game" -->'. While minor, this is a pattern sometimes used for SEO manipulation or to embed additional context invisible to users but visible to crawlers and AI agents. (location: page.html:224 - HTML comment inside music-list-wrapper)
social engineering
The page presents itself as a legitimate MP3 download service with a professional appearance, familiar branding (MP3.cc), and a large catalog of popular songs by well-known artists (Eminem, 2Pac, Dr. Dre, etc.) to establish trust. This facade encourages users to interact with download/play links that route through the third-party proxy fine.sunproxy.net, potentially exposing users to tracking or malware delivery. (location: page.html:5 - page title; page.html:224 - playlist content; page.html:671 - footer with mp3.cc copyright)
curl https://api.brin.sh/domain/eminem-feat-2pac-t-i-eazy-e-dr-dre-biggie-small-proof-the-game.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
eminem-feat-2pac-t-i-eazy-e-dr-dre-biggie-small-proof-the-game.hydr0.org currently scores 49/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.