context safety score
A score of 42/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
6 deceptive links where visible host does not match destination host
brand impersonation
The site at anitta-feat-saweetie.hydr0.org fully impersonates MP3.cc: it uses the MP3.cc logo, title ('MP3.cc'), navigation, footer copyright '© 2017–2026 MP3.cc', and all internal links point to mp3.cc. The canonical tag explicitly references mp3.cc/t/2376114395-anitta-feat-saweetie/, confirming the hydr0.org domain is mirroring/scraping and presenting itself as the legitimate MP3.cc service. (location: page.html:5,9,33-36,557)
malicious redirect
The page includes 1 detected redirect (per Tier 2 signals) and serves a canonical URL from mp3.cc while the actual hosting domain is anitta-feat-saweetie.hydr0.org. Users and crawlers arriving at the hydr0.org URL are served content impersonating mp3.cc, with the canonical tag attempting to pass SEO authority to the legitimate domain while the mirror captures traffic. (location: page.html:9 (canonical link))
malicious redirect
All 17 audio stream URLs presented as mp3.cc content are silently redirected through a third-party proxy at fine.sunproxy.net. The play links use javascript:void(0) with data-url attributes pointing to fine.sunproxy.net encoded paths, meaning audio is served through an intermediary that could perform traffic interception, inject ads, or track users without their knowledge. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456,475,494,513,532)
hidden content
The robots meta tag is set to 'noarchive', preventing search engines and archiving services (e.g. Wayback Machine) from caching the page. This is a common evasion technique used by piracy/impersonation sites to avoid forensic archiving and reduce accountability. (location: page.html:8)
social engineering
Audio filenames embedded in all 17 proxy URLs contain the watermark '(Hydr0.org)' (e.g. 'Anitta_feat_Saweetie_-_Faking_Love_Marcos_Ferrari_Remix_(Hydr0.org).mp3'), branding downloaded files with hydr0.org to drive traffic back to the piracy mirror. The page presents this pirated content as freely downloadable in a way designed to appear as a legitimate licensed service. (location: page.html:228,247,266,285,304 (data-url filenames))
brand impersonation
The footer contact email is hydrofm@yandex.com (a Russian webmail provider), while the copyright claims to be MP3.cc. This mismatch indicates the site operator is unaffiliated with mp3.cc but is using its brand identity. The email ties the operation to a Yandex account rather than any legitimate mp3.cc domain email. (location: page.html:557)
curl https://api.brin.sh/domain/anitta-feat-saweetie.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
anitta-feat-saweetie.hydr0.org currently scores 42/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.