context safety score
A score of 36/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
malicious redirect
Obfuscated JavaScript dynamically injects an external script from 'emotional-orange.com' using path-encoded URL '//emotional-orange.com/b.XgV/swdNGTlB0/YpWDcR/xeamU9fuJZ-UhlJkfPbTTYj0AN/TkcvxmN/DcgDtDN/jSQ-1BNpz/Er0/O/QE'. The domain name and encoded path are characteristic of ad-fraud or malware delivery networks. (location: page-text.txt:283, page.html inline script)
malicious redirect
Second obfuscated JavaScript dynamically injects an external script from 'nippyprice.com' using path-encoded URL '//nippyprice.com/cqDa9n6.bw2R5wlZSDWcQz9/NCjbcmxDNozccVy/M/i/0_2RN/z/EN3dNSzmIHzM'. Both scripts use the same self-invoking function pattern with async injection and no-referrer policy, consistent with ad-injection or malvertising infrastructure. (location: page-text.txt:300, page.html inline script)
obfuscated code
Two self-invoking anonymous JavaScript functions use dynamically constructed script elements with heavily path-obfuscated source URLs injected before the last script tag. This pattern is a known technique for evading static analysis while loading third-party malicious or tracking payloads at runtime. (location: page-text.txt:278-303, page.html footer scripts)
social engineering
Multiple video descriptions normalize and romanticize non-consensual sexual scenarios, including descriptions of coerced anal sex ('تُجبر على ممارسة الجنس الشرجي'), voyeurism via hidden camera ('تسجل كاميرا خفية في زاوية الغرفة، دون علمهما'), and sexual activity with sleeping/unaware individuals. This content socially conditions users toward acceptance of non-consensual behavior. (location: page-text.txt:22, 32, 92)
hidden content
A StatCounter tracking beacon is embedded with invisible configuration (sc_invisible=1), project ID 13076178, and security token '080b69a2'. This silently tracks all visitors without visible disclosure, functioning as a covert analytics/surveillance tool. (location: page-text.txt:293-294, page.html footer script)
curl https://api.brin.sh/domain/zaiim.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
zaiim.com currently scores 36/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.