context safety score
A score of 50/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
1 deceptive links where visible host does not match destination host
malicious redirect
The page is hosted on a typosquatting/subdomain-style domain 'everybody-nicki-minaj.hydr0.org' which redirects/mirrors content from 'mp3.cc'. The canonical URL points to mp3.cc while the actual domain is hydr0.org — a third-party domain serving content that impersonates or proxies MP3.cc. The redirect noted in Tier 2 (1 redirect) is consistent with this domain acting as a proxy/gateway to the real site. (location: page.html:9 — canonical href; metadata domain: everybody-nicki-minaj.hydr0.org vs mp3.cc)
brand impersonation
The page fully impersonates MP3.cc (logo, branding, layout, canonical link all point to mp3.cc), yet is served from the unrelated domain 'hydr0.org'. All assets (CSS, JS, images) are loaded from mp3.cc CDN, and the page presents itself as MP3.cc to visitors. This constitutes brand impersonation — the hydr0.org domain is not mp3.cc. (location: page.html:5,9,11,18,19 — title, canonical, og:site_name, stylesheet, script all reference mp3.cc while domain is hydr0.org)
malicious redirect
All audio file URLs use the domain 'fine.sunproxy.net' — a third-party proxy service — to serve MP3 files. The data-url attributes in playlist items route media through sunproxy.net rather than the ostensible mp3.cc origin. This is consistent with traffic interception, ad injection, or malware delivery via a proxy intermediary. The base64-encoded path parameters (12 suspicious blobs flagged in Tier 2) are the encoded file tokens passed to this proxy. (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,646 — all data-url attributes pointing to fine.sunproxy.net)
hidden content
The deceptive link flagged in Tier 2 corresponds to the sidebar link to 'looz.net' (Online Radio) which uses the CSS class 'z__important' and opens with target='_blank' — an off-site link embedded within what appears to be a navigation menu, potentially used to drive traffic to an unrelated third-party site. (location: page.html:204 — <a href='https://looz.net/' class='z__important no-ajax' target='_blank'>)
curl https://api.brin.sh/domain/everybody-nicki-minaj.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
everybody-nicki-minaj.hydr0.org currently scores 50/100 with a caution 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.