/ransomware/groups/hunting_queries

POST /api/ransomware/groups/hunting_queries

Price: 35 credits

Get the KQL threat-hunting queries published for a ransomware group: title, MITRE ATT&CK tactic and technique, target platform, data source, what the query detects and the full query text

How to use it

The query field is Kusto (KQL) for the platform named in platform. A group with no published query returns an empty list; an unknown group name answers 412.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• group string required — ransomware.live group name or the group page URL (examples: "akira", "https://www.ransomware.live/group/lockbit3"; minLength: 1; maxLength: 200)
• count integer required — Max number of results (examples: 20; min: 1)

Response

• @type string (default: "RansomwareHuntingQuery")
• id string required
• url string required
• group_alias string required
• tactic string nullable
• platform string nullable
• technique_id string nullable
• technique_name string nullable
• data_source string nullable
• added_date string nullable
• updated_date string nullable
• source string nullable
• description string nullable
• query string required

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — ransomware.live has no group under this name Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.