context safety score
A score of 57/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
phishing
2 deceptive links where visible host does not match destination host
malicious redirect
The page is served from the subdomain drake-feat-omarion.hydr0.org but the canonical URL, all internal links, CSS, and JS assets point to mp3.cc. The serving domain acts as a mirror/proxy redirecting users to mp3.cc content, constituting a redirect relationship where the true origin differs from the presented domain. (location: page.html:9 - canonical href and all asset/link hrefs point to mp3.cc while served from hydr0.org)
malicious redirect
All audio file play URLs resolve through fine.sunproxy.net, a third-party proxy/CDN domain distinct from the presenting site (mp3.cc / hydr0.org). Users clicking play are directed through an unverified intermediary proxy that could intercept, modify, or log requests. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608 - data-url attributes referencing fine.sunproxy.net)
brand impersonation
The site presents itself as MP3.cc (title, logo, canonical URL, copyright footer) but is actually served from the unrelated domain drake-feat-omarion.hydr0.org. This constitutes impersonation of the MP3.cc brand to lend legitimacy to a shadow domain. (location: page.html:5 - title tag; page.html:633 - footer copyright; page.html:9 - canonical tag)
hidden content
12 suspicious base64 blobs were flagged in Tier 2 analysis. These are present in the data-url attributes of playlist play links (e.g., fine.sunproxy.net/file/<base64>). The base64 strings encode opaque file paths/tokens routed through sunproxy.net, obscuring the true destination of audio file requests and preventing direct inspection of the resolved URLs. (location: page.html:228,247,266 etc. - data-url base64-encoded path parameters in fine.sunproxy.net URLs)
social engineering
The deceptive link count of 2 flagged in Tier 2 corresponds to links that display artist/song names as anchor text but resolve to mp3.cc domains rather than the hydr0.org host. Users trusting the page context may not realize they are being funneled off the serving domain. Additionally, a link to looz.net (Online Radio) is embedded as a genre sidebar item styled identically to internal genre links, potentially misleading users into clicking an off-domain link they believe is internal navigation. (location: page.html:204 - looz.net link styled as genre item; general cross-domain link deception throughout playlist)
curl https://api.brin.sh/domain/drake-feat-omarion.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
drake-feat-omarion.hydr0.org currently scores 57/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.