context safety score
A score of 38/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
brand impersonation
The page is hosted on a third-party subdomain (anitta-swae-lee-josh-gudwin.hydr0.org) but fully impersonates MP3.cc — including its logo, branding, CSS/JS assets loaded from mp3.cc, canonical URL pointing to mp3.cc, and copyright notice. The actual serving domain (hydr0.org) is not MP3.cc, creating a deceptive brand impersonation of the legitimate MP3.cc service. (location: page.html:5-14, page.html:33-36, page.html:633)
malicious redirect
The canonical link tag redirects crawlers and agents to https://mp3.cc/t/4124886030-anitta-swae-lee-josh-gudwin/ (a different domain), while the actual page is served from hydr0.org. This is consistent with a cloaking/redirect pattern where the scraper site funnels SEO traffic while presenting itself as the legitimate domain. (location: page.html:9)
malicious redirect
All MP3 audio file URLs resolve through fine.sunproxy.net, a third-party proxy/CDN domain unrelated to either hydr0.org or mp3.cc. User audio requests are routed through this unknown intermediary, which could intercept traffic, serve malicious files, or track users. The filenames embedded in the proxy URLs contain '(Hydr0.org)' branding confirming deliberate repackaging. (location: page.html:228, page.html:247, page.html:266, page.html:285, page.html:304)
hidden content
The base64-encoded tokens embedded in all audio download URLs (via fine.sunproxy.net/file/<base64>) are opaque encoded path parameters. While consistent with proxy URL encoding, the 12 suspicious base64 blobs flagged by the scanner correspond to these tokens — they cannot be decoded to verify destination without execution, making the actual file destinations unverifiable. (location: page.html:228-619 (all data-url attributes))
social engineering
The site presents itself as a legitimate free MP3 download service (MP3.cc) but is operated from a separate domain (hydr0.org) with a Yandex contact email (hydrofm@yandex.com). This misrepresents the site's identity and operator to induce users into downloading files from an unverified proxy infrastructure (fine.sunproxy.net), a social engineering pattern to gain user trust for potentially malicious file delivery. (location: page.html:633, metadata.json:1)
curl https://api.brin.sh/domain/anitta-swae-lee-josh-gudwin.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
anitta-swae-lee-josh-gudwin.hydr0.org currently scores 38/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.