Search Victim Profiles
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.
Dashboard victim filters:
- Identity and contact:
email,email_domain,username,discord_id,phone,steam_id,steam_name. - Device and network:
ip,victim_ip,hwid,os,antivirus,infection_path. - Geography and service:
country,city,domain,subdomain,service,identity_state. - Volume and richness:
total_docs_min,total_docs_max,service_count_min,service_count_max. - Metadata:
log_id, date range viafrom/toanddate_field(pwned_atorindexed_at).
Structured filters can use the same bare victim field names above. When a
filter is built from the full stealer investigation view, namespaced fields
such as victims.country, victims.service, and victims.total_docs are
projected to country, service, and total_docs for this direct victim
search endpoint.
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"
enriched Search session ID from POST /service/search/init.