context safety score
A score of 44/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The page is hosted on a subdomain of hydr0.org (ch31d-dj-ice-orig-shawn-mendes-camilla-cabello.hydr0.org) but presents itself as MP3.cc, including the MP3.cc logo, branding, site name, copyright notice, and canonical URLs pointing to mp3.cc. The actual serving domain is a third-party site impersonating or mirroring the MP3.cc brand without being the legitimate mp3.cc domain. (location: page.html:5,9,11,14,595 — <title>, canonical link, og:site_name, og:url, footer copyright all reference MP3.cc while domain is hydr0.org)
malicious redirect
The canonical link tag redirects crawlers and AI agents to https://mp3.cc/t/742193904-ch31d-dj-ice-orig-shawn-mendes-camilla-cabello/ rather than the actual serving URL. This combined with the 1 redirect detected in Tier 2 signals indicates the page is designed to appear associated with mp3.cc while the actual content is served from hydr0.org, a pattern consistent with SEO hijacking or traffic interception. (location: page.html:9 — <link rel="canonical" href="https://mp3.cc/t/742193904-ch31d-dj-ice-orig-shawn-mendes-camilla-cabello/">)
malicious redirect
All MP3 audio files are served via fine.sunproxy.net, a third-party proxy domain rather than mp3.cc. Users clicking play are routed through sunproxy.net which could intercept traffic, inject content, or serve malicious files. The base64-encoded file paths (12 suspicious blobs flagged in Tier 2) obscure the actual destination file paths, preventing inspection of what is actually being served. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532,551,570 — data-url attributes pointing to fine.sunproxy.net with base64-encoded paths)
social engineering
The page presents itself as a legitimate MP3 download service for popular artists (Shawn Mendes, Camila Cabello) to attract users searching for copyrighted music. By impersonating MP3.cc and using celebrity artist names in the subdomain and page content, the site socially engineers users into trusting it and downloading files through an unvetted third-party proxy (fine.sunproxy.net). (location: metadata.json — domain: ch31d-dj-ice-orig-shawn-mendes-camilla-cabello.hydr0.org; page.html:224 — artist names in h2 and playlist)
hidden content
The Tier 2 scan flagged 12 suspicious base64 blobs embedded in the page. These are the base64-encoded file paths in data-url attributes pointing to fine.sunproxy.net. While individually they appear to encode audio file URLs, the obfuscated nature of these paths prevents verification of actual content being served and could conceal malicious payloads or tracking parameters. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437 — data-url attributes containing long base64 strings like NDgwdkFuTUxJZ0tH...)
brand impersonation
One artist listing embeds a third-party domain reference within the artist name: 'Shawn Mendes & Camila Cabello [drivemusic.me]' — this injects the drivemusic.me domain name into visible page content and artist metadata, potentially for SEO poisoning or to redirect users to drivemusic.me. (location: page.html:556 — <span class="playlist-name-artist">Shawn Mendes & Camila Cabello [drivemusic.me]</span>)
curl https://api.brin.sh/domain/ch31d-dj-ice-orig-shawn-mendes-camilla-cabello.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
ch31d-dj-ice-orig-shawn-mendes-camilla-cabello.hydr0.org currently scores 44/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.