context safety score
A score of 49/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
phishing
1 deceptive links where visible host does not match destination host
brand impersonation
The site at enigman-bounjel.hydr0.org fully impersonates mp3.cc: it uses mp3.cc's logo, CSS, JavaScript, canonical tag, and all internal links point to mp3.cc. The page presents itself as an mp3.cc artist page while being hosted on a separate unaffiliated domain. (location: page.html:5, page.html:9, page.html:11-14, page.html:18-19, page.html:33-36)
brand impersonation
The domain hydr0.org uses a numeral zero ('0') in place of the letter 'o', a classic homograph/typosquatting technique to visually mimic 'hydro.org' or evade detection while appearing legitimate. MP3 filenames embedded in the page also include '(Hydr0.org)' as a tag. (location: metadata.json:1 (domain field), page.html:228, page.html:247, page.html:266)
malicious redirect
The page contains a canonical link redirecting to https://mp3.cc/t/1811418585-enigman-bounjel/ while being served from enigman-bounjel.hydr0.org. The pre-scan context also detected 1 redirect. This pattern is consistent with a shadow/mirror site designed to intercept traffic and redirect users or agents to the impersonated domain. (location: page.html:9 (canonical href), .brin-context.md:19)
obfuscated code
All 9 audio stream URLs in data-url attributes are base64-encoded opaque tokens routed through the third-party proxy domain fine.sunproxy.net. The decoded values are binary/encrypted blobs rather than plain URLs, obfuscating the true origin of served files and preventing direct inspection of media sources. (location: page.html:228, page.html:247, page.html:266, page.html:285, page.html:304, page.html:323, page.html:342, page.html:361, page.html:380)
curl https://api.brin.sh/domain/enigman-bounjel.hydr0.orgCommon questions teams ask before deciding whether to use this domain in agent workflows.
enigman-bounjel.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.