context safety score
A score of 58/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 scanned URL (atif-aslam-shreya-ghoshal-sachin-gupta.hydr0.org) is a subdomain that mirrors and proxies content from mp3.cc, with a canonical tag redirecting to mp3.cc. All navigation links, assets (CSS, JS), and download links point to mp3.cc and fine.sunproxy.net rather than the hosting domain. This subdomain/proxy pattern is used to intercept traffic destined for the legitimate site. (location: page.html:9 - <link rel='canonical' href='https://mp3.cc/t/3139741104-atif-aslam-shreya-ghoshal-sachin-gupta/'> and page.html:18-19 (all assets loaded from mp3.cc))
brand impersonation
The domain hydr0.org hosts a full clone of MP3.cc's interface, including the MP3.cc logo, branding, navigation, genre lists, footer copyright '© 2017 – 2026 MP3.cc', and contact email (hydrofm@yandex.com). The site presents itself as MP3.cc while operating under a completely different domain, constituting brand impersonation of the MP3.cc service. (location: page.html:5 (title tag), page.html:11 (og:site_name='MP3.cc'), page.html:33-36 (MP3.cc logo), page.html:633 (footer copyright))
malicious redirect
All MP3 file download/stream URLs route through fine.sunproxy.net, a third-party proxy/CDN not affiliated with the displayed brand (MP3.cc). The URLs contain long base64-encoded path segments (e.g. NDgwdkFuTUxJZ0tH...) that obfuscate the actual destination of file requests. This intermediary proxy can be used to track users, inject malware, or serve modified files. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570, 589, 608 - all data-url attributes pointing to fine.sunproxy.net/file/<base64>)
hidden content
Twelve base64-encoded blobs are embedded in the data-url attributes of playlist play links. While these encode proxied MP3 file paths, the encoding obscures the actual file destinations from users and security tools, preventing transparent inspection of where audio files are actually sourced from. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437, 456, 475, 494, 513, 532, 551, 570, 589, 608 - data-url attributes on playlist-play anchors)
curl https://api.brin.sh/domain/atif-aslam-shreya-ghoshal-sachin-gupta.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
atif-aslam-shreya-ghoshal-sachin-gupta.hydr0.org currently scores 58/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.