context safety score
A score of 54/100 indicates minor risk signals were detected. The entity may be legitimate but has characteristics that warrant attention.
encoded payload
suspicious base64-like blobs detected in page content
malicious redirect
The page is hosted on subdomain 2016-alan-walker.hydr0.org but impersonates mp3.cc by loading all assets (CSS, JS, images, fonts) from mp3.cc and setting canonical URL, og:url, and og:site_name to mp3.cc. The actual serving domain (hydr0.org) is distinct from the branded domain (mp3.cc), indicating a content-mirroring/shadow-copy setup that proxies the legitimate site through an unrelated domain. The one redirect noted in Tier 2 signals is consistent with this pattern. (location: page.html:9 (canonical), page.html:14 (og:url), page.html:18-19 (asset URLs))
brand impersonation
The site at hydr0.org fully impersonates MP3.cc — a legitimate music download service — by mirroring its complete UI, branding, logo, and content. The title tag reads '2016 Alan Walker | Download mp3 free, listen music online - MP3.cc', og:site_name is 'MP3.cc', and the footer copyright reads '© 2017 – 2026 MP3.cc'. The actual serving domain hydr0.org has no affiliation with mp3.cc, constituting clear brand impersonation. (location: page.html:5 (title), page.html:11 (og:site_name), page.html:652 (footer copyright))
malicious redirect
All audio file playback URLs route through fine.sunproxy.net, a third-party proxy/CDN not affiliated with mp3.cc. The data-url attributes on all 20 playlist items point exclusively to fine.sunproxy.net/file/ endpoints with Base64-encoded path parameters. This intermediary proxy intercepts all media requests and could serve malware, track users, or substitute content. The 12 suspicious Base64 blobs flagged in Tier 2 correspond to these encoded file paths. (location: page.html:228 (first data-url), page.html:247, page.html:266 — all playlist items)
social engineering
The site presents itself as a free MP3 download portal offering copyrighted music (Alan Walker tracks) for free download. This is a classic lure tactic — attracting users with free content to expose them to the proxy infrastructure at fine.sunproxy.net and hydr0.org, which can deliver malicious payloads, track downloads, or serve as a phishing vector for users who may be prompted to register or install software during the download process. (location: page.html:229 (download links), page-text.txt:136 (download prompts))
curl https://api.brin.sh/domain/2016-alan-walker.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
2016-alan-walker.hydr0.org currently scores 54/100 with a caution 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.