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
credential harvesting
credential form posts to an off-domain endpoint (may be legitimate SSO/OAuth)
cloaking
Page checks user-agent for bot/crawler strings to serve different content
cloaking
Page loads content in transparent or zero-size iframe overlay
js obfuscation
JavaScript uses Function constructor for runtime code generation
brand impersonation
The scanned domain wavevms.com serves a full replica of the official Hanwha Vision America Wisenet WAVE VMS product page. The canonical URL, og:url, og:site_name, all internal navigation links, images, and scripts all reference hanwhavisionamerica.com, while the page is actually delivered from the unrelated domain wavevms.com. This constitutes impersonation of the Hanwha Vision brand from an unofficial domain. (location: page.html:22 (canonical: https://hanwhavisionamerica.com/wisenet-wave-vms/), metadata.json (domain: wavevms.com))
malicious redirect
The page served at wavevms.com sets a canonical tag pointing to hanwhavisionamerica.com/wisenet-wave-vms/, redirecting search engine authority and potentially users to the official site while the impersonating domain collects traffic and form submissions. Additionally, links to sync.wavevms.com/ipvd and wavevms.com/wave-help/ route users to wavevms.com subdomains rather than official Hanwha infrastructure. (location: page.html:22 (canonical meta), page.html:4637 (sync.wavevms.com/ipvd), page.html:4676 (wavevms.com/wave-help/))
credential harvesting
A Gravity Forms form (ID 100) is embedded and gates a Wisenet WAVE VMS software download behind collection of: Region, Country, State/Province, Zip Code, First Name, Last Name, Company Email, Phone, role descriptor ('Which best describes you?'), and Operating System. This PII is collected on a non-official domain (wavevms.com) impersonating Hanwha Vision, creating high risk that submitted data is routed to an unauthorized party rather than Hanwha. (location: page-hidden.txt:6-8, page.html (gform_wrapper_100))
hidden content
The download form (ID 100) contains a hidden field labeled 'Lead Source' with a default value of 'Web Site' and a second hidden default 'WAVE VMS - Download'. These fields are not visible to users and covertly tag submitted leads with tracking metadata without user disclosure. (location: page.html:5380 (gf_form_conditional_logic defaults: {"16":"Web Site","17":"WAVE VMS - Download"}), page-hidden.txt:8 ('This field is hidden when viewing the form Lead Source'))
curl https://api.brin.sh/domain/wavevms.comCommon questions teams ask before deciding whether to use this domain in agent workflows.
wavevms.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.