context safety score
A score of 48/100 indicates multiple risk signals were detected. This entity shows patterns commonly associated with malicious intent.
obfuscated code
All script tags use a non-standard type attribute value 'e7ac570dcef91683065e5569-text/javascript' and 'e7ac570dcef91683065e5569-module' instead of standard values. This is a known Cloudflare Rocket Loader technique, but it effectively defers and obscures script execution — the actual JS bundles and inline scripts are not executed by the browser until Rocket Loader re-enables them, hiding their true behavior from static analysis. (location: page.html:53, page.html:80, page.html:92, page.html:104)
obfuscated code
The page contains an inline script that overrides and locks window.JSON.parse using an iframe-sandboxed reference to prevent tampering detection. This technique is used to harden anti-debugging measures or to intercept/monitor all JSON parsing across the page, including responses from fetch/XHR calls. It polls every 50ms to enforce this lock, which is an active anti-analysis countermeasure. (location: page.html:53-78)
hidden content
A 1x1 hidden iframe (position absolute, visibility hidden, zero border) is injected into the document body by an inline Cloudflare challenge script. The iframe dynamically injects a script tag targeting '/cdn-cgi/challenge-platform/scripts/jsd/main.js'. While associated with Cloudflare bot detection, this pattern of hidden iframe + dynamic script injection is a common vector for loading additional payloads not visible in static analysis. (location: page.html:124)
obfuscated code
Domain 'komikcast05.com' is only 41 days old with a numeric suffix ('05'), strongly suggesting it is part of a domain rotation series (komikcast01, komikcast02, etc.), a common tactic used by piracy and malvertising operations to evade blocklists by cycling through numbered domains. This pattern is associated with sites that serve malicious ads or redirects. (location: metadata.json (domain_age_days: 41, domain: komikcast05.com))
curl https://api.brin.sh/domain/komikcast05.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
komikcast05.com 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.