Search Victims
Search victim summaries keyed by log_id.
Successful responses use the standard search envelope.
The same route also accepts POST when you want to send filter or filter_id
in the JSON request body instead of the query string.
What is Victims Search?
Victims search returns compromised-device summaries rather than individual credential records. Each result is keyed bylog_id, which you can use to fetch the manifest or inspect files.
Use GET for normal query params. Use POST to the same route when you want to send { filter, filter_id } in the request body.
See Structured Filters for a simpler step-by-step guide with examples for flat params, POST body mode, AI filters, and query_config.
Victims Search vs Stealer Search
| Feature | Stealer Search | Victims Search |
|---|---|---|
| Primary record | Credential-style document | Device or log summary |
| Common pivots | domain, username, password, log_id | IP, HWID, device email, Discord ID, total docs |
| Next step | review the credential hit | fetch the manifest or files for that log_id |
Response Format
Successful responses use the standard search envelope. The victim results live underdata.items.
Key Fields
| Field | Description |
|---|---|
log_id | Unique identifier for this victim profile |
device_user_str | Usernames found on the device |
hwids_str | Hardware identifiers found on the device |
device_ips | Device IP addresses |
device_emails_str | Email addresses present on the device |
discord_ids | Discord IDs found on the device |
total_docs | Number of files or documents in the log |
pwned_at | When the device was compromised |
indexed_at | When OathNet indexed the log |
Next Step
Once you have alog_id, fetch the Victim Manifest to inspect the file tree, then request specific files or the archive as needed.Authorizations
API key for authentication (lowercase header name)
Query Parameters
indexed_at, pwned_at JSON-encoded structured filter tree.
Use leaf nodes with field, operator, and value, or compound nodes with and / or.
If you would rather send the filter as a real JSON object, use POST on the same /search route.
See /guides/structured-filters for the full grammar, operators, limits, and examples.
24-character transient filter context ID returned by POST /service/v2/ai/filter
or a previous search response.
24-character transient filter context ID.
^[0-9a-fA-F]{24}$"0123456789abcdef01234567"