context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
2 deceptive links where visible host does not match destination host
brand impersonation
The page is hosted on hydr0.org (27-akon-feat-styles-p.hydr0.org) but fully impersonates MP3.cc: the title, logo, all navigation links, canonical tag, og:url, CSS, and JS all reference mp3.cc. The footer copyright reads '© 2017 – 2026 MP3.cc' while the actual serving domain is hydr0.org. This is a clone/mirror site passing itself off as the legitimate MP3.cc service. (location: page.html:5, page.html:9, page.html:11-14, page.html:671)
malicious redirect
The canonical URL (https://mp3.cc/t/3565651149-27-akon-feat-styles-p/) diverges from the actual serving domain (https://27-akon-feat-styles-p.hydr0.org). A redirect was detected in the scan (Redirects: 1). Users or agents following canonical/og:url references will be redirected between domains, obscuring which domain is actually serving content and enabling traffic interception on the shadow domain. (location: metadata.json, page.html:9, page.html:14, .brin-context.md:19)
phishing
The site scrapes and mirrors MP3.cc content on an unrelated domain (hydr0.org) with subdomain names matching search queries (27-akon-feat-styles-p). This pattern is consistent with SEO poisoning / typosquat infrastructure used to intercept users searching for music downloads and expose them to ads, malware, or credential harvesting on a domain that appears identical to the legitimate site. (location: page.html, metadata.json domain=27-akon-feat-styles-p.hydr0.org)
hidden content
12 suspicious base64 blobs were detected in the page (all media file URLs served via fine.sunproxy.net using base64-encoded path parameters, e.g. NDgwdkFuTUxJZ0tH...). While these appear to be proxied audio file paths rather than injected payloads, routing all media through a third-party proxy (fine.sunproxy.net) obfuscates actual file origins and could facilitate content substitution or tracking. (location: page.html:228, 247, 266, 285, 304, 323, 342, 361, 380, 399, 418, 437 (data-url attributes))
social engineering
An external link to looz.net is styled with class 'z__important' and opens in a new tab (_blank), suggesting it is given visual or functional priority to drive users off the clone domain to a third-party site. The CSS class name implies intentional emphasis to influence user clicks toward an off-domain destination. (location: page.html:204)
curl https://api.brin.sh/domain/27-akon-feat-styles-p.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
27-akon-feat-styles-p.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.