context safety score
A score of 55/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
brand impersonation
The page is served from cash-cash-feat-christina-perri.hydr0.org but presents itself entirely as MP3.cc, with 83 internal links pointing to mp3.cc, the MP3.cc logo, branding, and canonical URL set to https://mp3.cc/t/3816369380-cash-cash-feat-christina-perri/. The hosting domain hydr0.org is a shadow mirror impersonating the mp3.cc brand to serve pirated content. (location: page.html:5,9,11,14,33 — title, canonical, og:site_name, og:url, logo href all reference mp3.cc while served from hydr0.org)
malicious redirect
The site registers 1 redirect and all audio playback is routed through fine.sunproxy.net, a third-party proxy domain, via 20 obfuscated URLs. Users clicking play are directed to an unknown third-party proxy service rather than the impersonated mp3.cc domain, enabling traffic interception and potential malware delivery through audio file downloads. (location: page.html:228,247,266,285,304 — all data-url attributes point to https://fine.sunproxy.net/file/<base64token>/filename.mp3)
obfuscated code
All 20 audio stream URLs embed base64-encoded tokens as path components in fine.sunproxy.net URLs. Decoding reveals a second layer of base64 (double-encoded binary data), obscuring the actual file identifiers and preventing URL analysis. This is consistent with anti-hotlinking obfuscation but also masks the true destination of streamed content. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589 — data-url attributes)
social engineering
A sidebar navigation link labeled 'Online Radio' with a radio icon links to https://looz.net/ (a different domain, flagged as the 1 deceptive link in pre-scan). The visual context implies it is part of the MP3.cc site navigation, but it redirects users to an unrelated third-party site. The z__important CSS class suggests it is intentionally highlighted. (location: page.html:204 — <a href="https://looz.net/" class="z__important no-ajax" target="_blank">Online Radio</a>)
curl https://api.brin.sh/domain/cash-cash-feat-christina-perri.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
cash-cash-feat-christina-perri.hydr0.org currently scores 55/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.