Overview
Victim workflows start after you have alog_id from stealer search,
investigation search, file metadata, or a saved result. The victim APIs help you
move from “this log exists” to “what is inside this log?”
There are three response styles to keep straight:
- victim search returns the standard
success,message,data, and_metaenvelope - manifests return raw JSON because they are file trees, not search result pages
- file reads and archive downloads return raw text, bytes, or ZIP streams
Search Victim Summaries
Victim search returns aggregated metadata that helps you decide which logs to inspect next.Response Example
filter and filter_id system as the other V2 search endpoints. See Structured Filters for the operator matrix and the victims-specific field aliases.
Get The Manifest
The manifest endpoint is different: it returns raw JSON withlog_id, optional log_name, and victim_tree. There is no {success, data} wrapper.
If the log came from a search session, pass the same search_id so the follow-up request stays attached to that investigation.
Get A File
GET /service/v2/victims/{log_id}/files/{file_id} returns the file itself. For text files, read .text. For binary files, read bytes.
Always URL-encode log_id and file_id if they contain slashes, spaces, or path-like names from the manifest.
Download The Archive
GET /service/v2/victims/{log_id}/archive streams a ZIP archive. Treat it as a download, not JSON.
Stealer Search
Find credential rows that include
log_idFile Search
Search inside selected logs before downloading files
Exports
Export larger result sets after a search workflow
API Reference
Use OpenAPI for exact paths, parameters, schemas, and stream responses