context safety score
A score of 49/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
malicious redirect
The domain 2-loops.hydr0.org serves content that is a near-identical clone of mp3.cc, with canonical URLs, og:url, og:site_name, CSS, JS, and all internal links pointing to mp3.cc. The subdomain hydr0.org is used as a shadow/mirror domain to serve the mp3.cc brand under a different host, constituting a redirect/cloaking setup. The pre-scan context also confirms 1 redirect was detected. (location: page.html:9 (canonical href), page.html:14 (og:url), page.html:18-19 (external CSS/JS from mp3.cc))
brand impersonation
The site at 2-loops.hydr0.org fully impersonates mp3.cc: it replicates the MP3.cc title, logo, branding, site structure, footer copyright ('© 2017–2026 MP3.cc'), and contact email (hydrofm@yandex.com), while operating under the unrelated hydr0.org domain. Users and automated agents would believe they are interacting with the legitimate mp3.cc service. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:33-36 (logo), page.html:652 (footer copyright))
malicious redirect
All MP3 file download/play URLs route through fine.sunproxy.net, a third-party proxy domain not affiliated with mp3.cc. Audio file requests are proxied through this domain with base64-encoded parameters, potentially allowing traffic interception, substitution of content, or tracking of user behavior without disclosure. (location: page.html:228 (data-url on playlist-play anchors), all playlist items use https://fine.sunproxy.net/file/... URLs)
hidden content
Twelve suspicious base64 blobs were flagged by Tier 2 analysis. These correspond to the base64-encoded path segments in the fine.sunproxy.net MP3 URLs (e.g., NDgwdkFuTUxJZ0tH...). While these appear to be obfuscated file routing tokens rather than injected payloads, they conceal the true destination/identity of audio files being served and prevent transparent URL inspection. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437 (data-url attributes))
social engineering
The site presents itself as a free MP3 download platform ('Download mp3 free, listen music online') using the branding and content of a legitimate service (mp3.cc), which may induce users to download files from an unverified third-party proxy (fine.sunproxy.net) under false pretense of legitimacy. The deceptive link flagged in Tier 2 (count: 1) is consistent with the canonical/og:url mismatch between the serving domain and the branded domain. (location: page.html:5 (title tag), page.html:9 (canonical link mismatch with serving domain))
curl https://api.brin.sh/domain/2-loops.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2-loops.hydr0.org currently scores 49/100 with a suspicious 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.