context safety score
A score of 40/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
2 deceptive links where visible host does not match destination host
malicious redirect
The scanned URL (dr-dre-rick-ross-anderson-paak.hydr0.org) is a subdomain that mirrors content from mp3.cc, with a canonical tag pointing to https://mp3.cc/t/842747412-dr-dre-rick-ross-anderson-paak/. The page impersonates mp3.cc branding, logo, and navigation while being hosted on a different domain (hydr0.org). This constitutes a redirect/cloaking setup where the subdomain funnels traffic that belongs to mp3.cc, with 1 redirect confirmed in Tier 2 signals. (location: <link rel="canonical" href="https://mp3.cc/t/842747412-dr-dre-rick-ross-anderson-paak/"> — page.html:9)
brand impersonation
The page fully impersonates MP3.cc — including the MP3.cc logo, branding, navigation, footer copyright '© 2017 – 2026 MP3.cc', CSS/JS assets loaded from mp3.cc, and Open Graph metadata declaring og:site_name as 'MP3.cc'. This is done from a third-party domain (hydr0.org) without authorization, constituting brand impersonation of MP3.cc. (location: page.html:5,11,18,19,33-36,400-405)
malicious redirect
All audio file playback URLs route through a third-party proxy domain 'fine.sunproxy.net' using obfuscated base64-encoded file paths. This proxy intercepts all audio streaming traffic, potentially enabling traffic interception, tracking, or malware delivery. The 9 suspicious base64 blobs flagged in Tier 2 correspond to these 9 encoded proxy URLs. (location: data-url attributes in page.html:228,247,266,285,304,323,342,361,380)
social engineering
The site presents itself as a legitimate free MP3 download/streaming service (impersonating mp3.cc) on a deceptive subdomain (dr-dre-rick-ross-anderson-paak.hydr0.org) designed to attract users searching for these specific artists. Users are led to believe they are on a legitimate service while their traffic is routed through proxy infrastructure. The contact email 'hydrofm@yandex.com' (a Yandex address) is embedded in the footer alongside stolen MP3.cc copyright branding. (location: page.html:405 — footer copyright and contact email)
hidden content
Two deceptive links were flagged in Tier 2. One link in the 'Other listen' sidebar contains a raw YouTube URL as anchor text: 'https youtu be cqzhvb3igfq si nckhamcqvk6fmfbi', which is presented as a music search tag but encodes a YouTube video reference in an obfuscated manner as plain text within the tag list. (location: page.html:422 — tags_block sidebar list item)
curl https://api.brin.sh/domain/dr-dre-rick-ross-anderson-paak.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
dr-dre-rick-ross-anderson-paak.hydr0.org currently scores 40/100 with a suspicious verdict and low 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.