context safety score
A score of 39/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 identical heavily obfuscated JavaScript blocks using a custom Caesar-cipher-like character rotation over a URL-decoded string. The script decodes URLs, builds function/variable names at runtime, and dynamically loads external ad scripts. This pattern is used to evade static analysis and hide the true behavior of ad injection or redirect logic. (location: page.html lines 72, 74-75, 127 (inline script blocks with data-cfasync=false))
malicious redirect
Three third-party scripts loaded from suspicious low-reputation domains: oversizedsixtieswiry.com/on.js, anytimebananarecoil.com/in.js, and doctrinekettleworsening.com/bn.js. These are randomly-worded nonsense domains typical of malvertising networks that serve drive-by redirects, exploit kits, or unwanted software. Each is loaded with the same obfuscated bootstrap code. (location: page.html lines 73, 76, 128)
malicious redirect
The page is hosted at viet69.cm but all canonical links, AJAX endpoints, CDN assets, and navigation point to viet69.ke, and the site displays an announcement that VIET69.NET has moved to VIET69.KE. The visited domain (viet69.cm) is a shadow/redirect domain used to funnel users to the primary domain, obscuring the true origin and enabling traffic laundering. (location: page.html lines 13-14, 20-21, 43-46, 85, 125; metadata.json url field)
hidden content
The site description element carrying the text 'VIET69' is given the CSS class 'hidden' (h2#site-description.hidden), suppressing it from visual rendering while keeping it in the DOM for SEO/crawler manipulation purposes. (location: page.html line 89)
social engineering
Multiple video titles describe scenarios of non-consensual recording, covert filming ('hack camera' category), and sharing of intimate content without apparent consent (e.g., 'Anh đăng lên mạng nhớ che mặt em đi' — 'When you post online remember to cover my face'). The site hosts a 'Camera, Hack camera' category explicitly labeled for voyeuristic/non-consensual content, normalizing image-based sexual abuse. (location: page.html lines 115, 295-297; page-text.txt lines 37, 234)
curl https://api.brin.sh/domain/viet69.cmCommon questions teams ask before deciding whether to use this domain in agent workflows.
viet69.cm currently scores 39/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.