context safety score
A score of 39/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
malicious redirect
The page is hosted at 2cellos-feat-sky-ferreira.hydr0.org but all canonical URLs, links, CSS, and JS assets point to mp3.cc. The subdomain acts as a mirror/redirect front for mp3.cc, masking the true origin of the content and potentially used for SEO manipulation or traffic interception. (location: page.html:9 - <link rel='canonical' href='https://mp3.cc/t/2145312358-2cellos-feat-sky-ferreira/'>)
malicious redirect
All 12 audio stream URLs resolve through fine.sunproxy.net, a third-party proxy/CDN not affiliated with mp3.cc or hydr0.org. Traffic is silently routed through this intermediary, which could intercept requests, log user activity, or serve malicious payloads instead of audio files. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 - data-url attributes pointing to fine.sunproxy.net)
brand impersonation
The site impersonates MP3.cc by mirroring its full UI, branding, logo, content, and navigation while operating from a completely different domain (hydr0.org subdomain). Users and AI agents following links to this domain would believe they are on mp3.cc. (location: page.html:5 - <title>; page.html:11 - og:site_name 'MP3.cc'; page.html:33-36 - MP3.cc logo and header)
social engineering
The site presents itself as a legitimate free MP3 download/streaming service to entice users into clicking play/download links that route all traffic through the third-party sunproxy.net intermediary, potentially exposing users to malware or tracking. (location: page.html:228-451 - playlist items with play/download links routing through fine.sunproxy.net)
curl https://api.brin.sh/domain/2cellos-feat-sky-ferreira.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2cellos-feat-sky-ferreira.hydr0.org currently scores 39/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.