context safety score
A score of 47/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
brand impersonation
The domain ahadadream-priya-ragu-skrillex.hydr0.org hosts a full clone of MP3.cc, including its logo, branding, stylesheet, canonical URLs, og:site_name, and all navigation links pointing to mp3.cc. The site presents itself visually as MP3.cc while operating under a completely different domain (hydr0.org), deceiving users into believing they are on the legitimate MP3.cc service. (location: page.html: <title>, <link rel='canonical'>, og:site_name, og:url, header logo href, all navigation links, footer copyright)
malicious redirect
The canonical link tag redirects to https://mp3.cc/t/1159925114-ahadadream-priya-ragu-skrillex/ and all download/artist links point to mp3.cc, meaning users clicking links are silently redirected off the impersonating domain to the real mp3.cc. This redirect pattern is consistent with SEO cloaking or traffic interception schemes where the hydr0.org domain captures search traffic then funnels it elsewhere. (location: page.html line 9: <link rel='canonical' href='https://mp3.cc/t/1159925114-ahadadream-priya-ragu-skrillex/'>, all playlist-down and playlist-name links)
hidden content
All 20 audio file URLs use opaque base64-encoded path tokens served through the third-party proxy domain fine.sunproxy.net. These tokens obscure the actual file paths and route media delivery through an intermediary, making it impossible to verify the true origin or content of downloaded files. This is consistent with the 12 suspicious base64 blobs flagged in Tier 2 analysis. (location: page.html lines 228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589: data-url attributes containing base64-encoded paths on fine.sunproxy.net)
social engineering
An external link to looz.net is embedded within the site's genre navigation list, styled identically to legitimate genre links and labeled 'Online Radio'. It uses target='_blank' to open in a new tab and is marked with a 'z__important' CSS class, indicating intentional prominence. This disguises an off-domain commercial link as a native site feature to drive traffic to a third-party site. (location: page.html line 204: <a href='https://looz.net/' class='z__important no-ajax' target='_blank'>Online Radio</a>)
curl https://api.brin.sh/domain/ahadadream-priya-ragu-skrillex.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
ahadadream-priya-ragu-skrillex.hydr0.org currently scores 47/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.