context safety score
A score of 48/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
Page is served from coco-1990.hydr0.org but is entirely branded as MP3.cc — the page title, canonical link, og:site_name, og:url, all navigation links, CSS/JS resources, and copyright footer all reference mp3.cc. The site operates as an unauthorized mirror/proxy of mp3.cc under a different domain. (location: page.html:5,9,11,14,18,19,33,324,329)
malicious redirect
One redirect was recorded in the pre-scan (brin-context: Redirects=1). The serving domain coco-1990.hydr0.org proxies mp3.cc content, meaning users who arrive via a link or search result are silently redirected to this impersonating domain while believing they are on mp3.cc. (location: metadata.json, .brin-context.md:19)
hidden content
Audio file download URLs served via fine.sunproxy.net contain base64-encoded path segments (5 blobs detected). Decoded content resolves to encrypted/obfuscated binary tokens rather than plain file paths, obscuring the actual resource routing and tracking infrastructure behind the proxy. (location: page.html:228,247,266,285,304)
curl https://api.brin.sh/domain/coco-1990.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
coco-1990.hydr0.org currently scores 48/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.