context safety score
A score of 42/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
obfuscated code
Multiple instances of a heavily obfuscated inline script using URL-encoding, character-code arithmetic (Caesar-style shift cipher with position-based offset), and array slicing to conceal its true payload and behavior. The script decodes a URI-encoded string at runtime and reassembles it using index offsets before executing. This pattern is a known technique to hide ad-injection, redirect, or malware delivery logic from static scanners. Appears three times identically in the page. (location: page.html lines 490, 738; page-text.txt line 376, 622)
malicious redirect
External script loaded from '//frozenpayerpregnant.com/bn.js' — a suspicious third-party domain with no legitimate affiliation to the site. The domain name itself ('frozen payer pregnant') is characteristic of ad-fraud or traffic-redirect networks. Loaded with data-cfasync='false' to bypass Cloudflare scrutiny, with onerror/onload callbacks ('xyiyotp(16)') that invoke functions defined within the obfuscated inline script, indicating coordinated execution. (location: page.html line 491)
malicious redirect
External script loaded from '//bundlemoviepumice.com/on.js' — another suspicious third-party domain with no legitimate affiliation. Also loaded with data-cfasync='false' and onerror/onload callbacks ('uebsqhio(15)') tied to the obfuscated inline script. 'bundlemoviepumice.com' is consistent with ad-fraud/redirect network domain naming conventions. (location: page.html line 739)
hidden content
Cloudflare Rocket Loader is used (rocket-loader.min.js) and all first-party scripts have their type attribute set to a non-standard MIME type 'c98864843f74d0db5eecb4d7-text/javascript' instead of 'text/javascript'. This prevents browsers from executing them until Rocket Loader re-enables them, but it also obscures which scripts are active during initial page load and can be used to hide the sequencing of script execution from security scanners. (location: page.html lines 75-76, 710-713, 720)
obfuscated code
A hidden 1x1 pixel invisible iframe is injected via inline script (Cloudflare challenge script) with position:absolute, top:0, left:0, visibility:hidden. While this is a standard Cloudflare bot-detection technique, the iframe injects a child script ('window.__CF$cv$params') dynamically via innerHTML into its document head, which is an unusual code execution pattern that could be abused for cross-frame scripting in a compromised or spoofed environment. (location: page.html line 742)
curl https://api.brin.sh/domain/kimochi.infoCommon questions teams ask before deciding whether to use this domain in agent workflows.
kimochi.info currently scores 42/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.