Velociraptor is a forensic and incident-response platform built around Velociraptor Query Language. Its web interface can expose client inventories, collected files, hunts, notebooks, server-side queries, and API clients. A public title match is therefore a reason to review the authority of the whole server. The login page alone does not show that boundary.
Observation
At 07:50 on November 20, 2026 (UTC+8), a count-only ZoomEye SDK query used sub_type=all, page 1, and pagesize 1. app="Velociraptor" returned 0 matches. title="Velociraptor" returned 238 matches.
The product name can appear in documentation and public research pages, so 238 is an upper bound for title leads rather than a count of confirmed deployments. The absence of an application fingerprint means the title field is the only observed signal in this batch.
Organization scope matters
The Velociraptor security documentation warns that users with READ_RESULTS can read any file within the organization, including collections, hunts, exports, and notebooks. It also notes that notebook sharing controls GUI visibility while data in the organization can still be available through VQL to users who know identifiers.
That design is appropriate for an incident-response platform, but it makes organization boundaries important. Review the server's organizations, GUI users, API clients, roles, and explicit permission grants. Treat an API client that can run arbitrary server-side VQL as a high-authority principal. Check security.denied_plugins, artifact permissions, and any service-specific controls around outbound or file access.
Review the evidence path
Collected endpoint data may include credentials, browser history, files, or memory artifacts. The server should have a defined retention period, access log, download control, and secure backup. Review who can download collection data and whether users can export outside the approved evidence store.
Tests should include an investigator who can view a hunt but not alter roles, an API client limited to a narrow query, a former user whose token is being revoked, and an organization member who knows a notebook identifier but should not see its contents. Confirm both the interface and the API behavior.
The title query is useful for finding publicly visible candidates and comparing changes. The risk conclusion comes from the organization boundary, VQL permissions, and evidence retention choices on each verified host.