Skip to content
skopnix
Detections · Rule
← IBM QRadar detectionsIBM QRadar · Actor indicator sweep

Kimsuky file hash indicators

AQLhighconfidence 72/100generated 2026-10-18

Any of 1 high-confidence file hash indicators skopnix attributes to Kimsuky.

ATT&CK
T1204.002 mitre ↗
Linked actors
Kimsuky
False positives
Every value is a skopnix indicator tied to Kimsuky with confidence >= 72 from >= 2 independent sources, warninglist-clean (reserved / CDN / cloud / scanners / top sites) — re-validate against last_seen before blocking.

AQL search

skopnix-qradar-actor-kimsuky-hash-660b548f.aqldownload .aql ↓
SELECT sourceip, username, QIDNAME(qid) AS event, LOGSOURCENAME(logsourceid) AS log_source, "File Hash"
FROM events
WHERE REFERENCESETCONTAINS('Skopnix: Kimsuky - file hashs', "File Hash")
LAST 7 DAYS

CRE rule (build in Offenses > Rules)

download .txt ↓
Rule name: "Skopnix: Kimsuky file hash match"
Rule type: Event
Test stack:
  - and when the event(s) were detected by one or more of [any]
  - and when any of File Hash is contained in any of Reference Set - "Skopnix: Kimsuky - file hashs"
  - and NOT when an event matches any of the following BB:Skopnix Known-Good Exclusions
Response: dispatch new event / create offense indexed by Username; annotate "Skopnix hash match".
FP-safety: BB:Skopnix Known-Good Exclusions = RFC1918 + the customer's known-good destinations; the set only ever holds skopnix high-confidence, multi-source, warninglist-clean indicators (time-to-live 730 days, timeout on last seen).

Reference set · Skopnix: Kimsuky - file hashs

download .json ↓
{
 "name": "Skopnix: Kimsuky - file hashs",
 "element_type": "ALNIC",
 "element_type_label": "AlphaNumeric (Ignore Case)",
 "time_to_live": "730 days",
 "timeout_type": "LAST_SEEN",
 "create": "POST /api/reference_data/sets?name=Skopnix%3A%20Kimsuky%20-%20file%20hashs&element_type=ALNIC&time_to_live=730%20days&timeout_type=LAST_SEEN",
 "load": "POST /api/reference_data/sets/bulk_load/Skopnix%3A%20Kimsuky%20-%20file%20hashs  (body: JSON array of the elements)",
 "feed": "skopnix publishes this set as a feed; load it via the QRadar Reference Data API on a schedule (or Admin > Reference Set Management > Import). Elements age out on the time-to-live, so a retired skopnix indicator stops matching without a manual purge.",
 "elements": [
  "a173a425d17b6f2362eca3c8ea4de9860b52faba414bbb22162895641dda0dc2"
 ]
}

1 element · one per line for a bulk import ↓

How to deploy on IBM QRadar

  1. 1.Create the reference set from its spec (Reference Data API, or Admin > Reference Set Management) and schedule the skopnix feed load.
  2. 2.Paste the AQL into Log Activity > Advanced Search to hunt the last seven days.
  3. 3.For alerting, build the CRE rule from the test stack shown and exclude your known-good building block.

Check · Custom properties ("URL Host", "URL", "File Hash", "Process CommandLine") come from your DSMs and content extensions; rename them if yours differ.

References