context safety score
A score of 34/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
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The page is hosted on cakal-arem-ozguc-arman-aydin.hydr0.org but fully impersonates MP3.cc, copying its branding, logo, CSS, JS, canonical URL, og:site_name, and footer copyright. All navigation links and download links point to mp3.cc, making this a mirror/clone site operating under a different domain. (location: page.html:5-14, page.html:33-36, page.html:386)
malicious redirect
The canonical link tag and all internal links redirect users to mp3.cc (https://mp3.cc/t/4110151282-cakal-arem-ozguc-arman-aydin/) from a third-party domain (hydr0.org). This subdomain acts as a traffic capture and redirect layer, potentially for SEO manipulation, ad injection, or referral fraud before forwarding users to the real site. (location: page.html:9 (canonical href), page.html:229, page.html:234)
malicious redirect
All MP3 audio file streams are served through a third-party proxy domain 'fine.sunproxy.net' rather than directly from mp3.cc or any legitimate CDN. The proxy URLs contain long base64-encoded path components that obscure the actual file routing, representing an off-domain intermediary for all media content delivery. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361)
hidden content
8 suspicious base64 blobs were flagged by pre-scan heuristics. These appear embedded within the data-url attributes of playlist play links (e.g., NDgwdkFuTUxJZ0tHbEJUVFE0QUZzeU50Smt3cnFoanUyVFdycUE0OVNpQjZNMno0...), used as obfuscated proxy routing tokens for fine.sunproxy.net file URLs. While not injecting commands, this pattern obscures the true file destination from both users and automated scanners. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361 (data-url attributes))
brand impersonation
The page title, meta description, og:site_name, og:image, og:url, and footer copyright all explicitly claim to be 'MP3.cc' while being served from a completely different domain (hydr0.org). This constitutes deliberate misrepresentation of the site's identity and origin. (location: page.html:5, page.html:11, page.html:14, page.html:386)
curl https://api.brin.sh/domain/cakal-arem-ozguc-arman-aydin.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
cakal-arem-ozguc-arman-aydin.hydr0.org currently scores 34/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.