context safety score
A score of 49/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
malicious redirect
The page is hosted on 'endless-sky-original-edit.hydr0.org' but all canonical links, assets (CSS, JS), and navigation point to 'mp3.cc'. The canonical tag explicitly redirects to 'https://mp3.cc/t/2398417546-endless-sky-original-edit/'. This subdomain acts as a shadow/mirror site that impersonates the legitimate mp3.cc service, with the actual domain being a third-party host (hydr0.org) not affiliated with mp3.cc. (location: page.html:9 - <link rel="canonical" href="https://mp3.cc/t/2398417546-endless-sky-original-edit/">)
brand impersonation
The page at 'endless-sky-original-edit.hydr0.org' fully clones the MP3.cc brand identity including logo, site name, CSS/JS assets loaded directly from mp3.cc, and footer copyright '© 2017–2026 MP3.cc'. The domain 'hydr0.org' is not the legitimate mp3.cc domain. This constitutes brand impersonation of the MP3.cc service, potentially used to intercept user traffic or serve malicious downloads. (location: page.html:5,18,19,481 - title tag, asset links, footer copyright)
malicious redirect
All MP3 audio file download/play URLs route through 'fine.sunproxy.net', a third-party proxy domain. All 13 playable tracks use data-url values pointing to 'https://fine.sunproxy.net/file/...' with encoded path parameters. This intermediary proxy can intercept, modify, or replace audio files with malicious payloads, or track users, without their knowledge. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456 - data-url attributes on playlist-play anchors)
obfuscated code
All 13 audio file URLs contain long Base64-encoded path segments embedded within the 'fine.sunproxy.net/file/' URL paths (e.g., 'YVlGMWFTTXN3M0VjVThHdEhvZHd2dHhyWDZqYlJHSGE3bDNEMUdscEZ5...'). These opaque encoded blobs obscure the true destination of file requests. The pre-scan detected 12 suspicious base64 blobs, consistent with these findings. The encoding prevents static analysis of the actual file endpoints. (location: page.html:228,247,266,285,304,323,342,361,380,399,418,437,456 - data-url base64 path segments in fine.sunproxy.net URLs)
brand impersonation
The MP3 filenames embedded in the sunproxy URLs all contain '(Hydr0.org)' branding (e.g., 'Scotty_-_Endless_Sky_(Hydr0.org).mp3'), indicating the files were sourced or re-encoded by hydr0.org and rebranded, potentially replacing legitimate audio files with versions containing malicious audio watermarks, payloads, or modified metadata. (location: page.html:228,247,266 - MP3 filename parameters in sunproxy URLs contain '(Hydr0.org)' tag)
curl https://api.brin.sh/domain/endless-sky-original-edit.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
endless-sky-original-edit.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.