context safety score
A score of 68/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The domain 2-chainz-x-kanye-west-x-brent-faiyaz.hydr0.org is a subdomain of hydr0.org acting as a redirect/proxy to mp3.cc. The canonical URL and all internal links point to mp3.cc, while the serving domain is different. This subdomain-based redirection pattern is used to obscure the true destination and evade URL-based blocklists. (location: page.html:9 - canonical link and all href attributes pointing to mp3.cc while served from hydr0.org subdomain)
brand impersonation
The page is served from hydr0.org (a third-party domain) but fully impersonates MP3.cc, including the logo, branding, site name, copyright notice, and all navigation links. The contact email hydrofm@yandex.com combined with a Yandex email address and MP3.cc branding impersonation suggests an unauthorized mirror or clone of MP3.cc designed to capture traffic under a different domain. (location: page.html:5,386 - title tag claims MP3.cc brand; footer shows MP3.cc copyright with hydrofm@yandex.com Yandex contact)
malicious redirect
All audio file download and play URLs route through fine.sunproxy.net, a third-party proxy service, rather than directly from mp3.cc or a known CDN. The data-url values in playlist items are all pointing to fine.sunproxy.net/file/ with base64-encoded path parameters. This proxy layer could be used for traffic interception, malware delivery, or ad injection. (location: page.html:228,247,266,285,304,323,342,361 - all data-url attributes use fine.sunproxy.net as proxy)
hidden content
Eight base64-encoded blobs were flagged in the pre-scan. These appear as encoded file path parameters in the fine.sunproxy.net URLs (e.g. NDgwdkFuTUxJZ0tHbEJUVFE0QUZzMjJBeit2dnUvakFx...). While the decoded values are likely obfuscated file paths, the use of base64 encoding to obscure proxy routing parameters prevents transparent inspection of the actual resource destinations. (location: page.html:228,247,266,285,304,323,342,361 - base64 path segments in fine.sunproxy.net file URLs)
curl https://api.brin.sh/domain/2-chainz-x-kanye-west-x-brent-faiyaz.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2-chainz-x-kanye-west-x-brent-faiyaz.hydr0.org currently scores 68/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.