context safety score
A score of 67/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 page is hosted on destiny-s-child-feat-wyclef-jean.hydr0.org but all canonical URLs, asset links (CSS/JS), and navigation links point to mp3.cc. The subdomain uses the hydr0.org domain (noted in all MP3 filenames as '(Hydr0.org)') while the actual content infrastructure belongs to mp3.cc. This represents a domain redirect/proxy arrangement where the scanned domain is a front for mp3.cc content, confirmed by the canonical tag: <link rel='canonical' href='https://mp3.cc/t/1115560536-destiny-s-child-feat-wyclef-jean/'> (location: page.html:9 - canonical tag; page.html:18-19 - external CSS/JS assets from mp3.cc)
malicious redirect
All MP3 audio file downloads are proxied through fine.sunproxy.net, a third-party proxy domain not affiliated with either the hosting domain (hydr0.org) or the branded site (mp3.cc). Users clicking play are streamed audio from fine.sunproxy.net which could intercept requests, inject ads, or track users. The data-url attributes contain base64-encoded tokens passed to this proxy service. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627 - all playlist-play data-url attributes)
brand impersonation
The site impersonates or mirrors the legitimate MP3.cc brand: it uses MP3.cc's logo, CSS, JavaScript, navigation, footer copyright ('2017-2026 MP3.cc'), and content layout, but is served from hydr0.org subdomain. Users would reasonably believe they are on mp3.cc when they are actually on a third-party domain. The site presents itself as MP3.cc throughout all UI elements. (location: page.html:5 - title tag; page.html:11 - og:site_name; page.html:35 - logo text; page.html:652 - footer copyright)
social engineering
The site offers free MP3 downloads of copyrighted music (Destiny's Child, Wyclef Jean tracks), which is a common social engineering lure used to attract users to piracy/proxy sites that may serve malware or unwanted software. The contact email hydrofm@yandex.com in the footer uses a Russian email provider (Yandex), which combined with the hydr0.org domain is consistent with operations based in regions with lax copyright enforcement. (location: page.html:652 - footer with hydrofm@yandex.com; page.html:224 - music download playlist)
hidden content
The 12 suspicious base64 blobs flagged by Tier 2 analysis are the base64-encoded tokens embedded in the data-url attributes for each track's play link (e.g., 'YVlGMWFTTXN3M0VjVThHdEhvZHd2aEUvN0prK0gv...'). These are passed to fine.sunproxy.net to authorize file access. While functionally used for proxy authentication, they are opaque encoded strings that obscure the actual file URLs and server-side token validation logic from users and scanners. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570,589,608,627 - data-url base64 tokens in playlist-play anchors)
curl https://api.brin.sh/domain/destiny-s-child-feat-wyclef-jean.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
destiny-s-child-feat-wyclef-jean.hydr0.org currently scores 67/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.