Skip to content
skopnix
Detections · Rule
← Sigma detectionsSigma · Actor indicator sweep

TA402 file hash indicators

SIGhighconfidence 72/100generated 2026-10-18

Any of 2 high-confidence file hash indicators skopnix attributes to TA402.

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

Sigma rule

skopnix-sigma-actor-ta402-hash-47a556f6.ymldownload .yml ↓
title: Skopnix - TA402 file hash indicators
id: b2ca923c-31d9-5904-b018-e2929897ebb3
status: experimental
description: Any of 2 high-confidence file hash indicators skopnix attributes to TA402.
references:
  - https://skopnix.com/actors/ta402
author: skopnix
date: '2026-10-18'
tags:
  - attack.execution
  - attack.t1204.002
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Hashes|contains:
      - SHA256=2E4671C517040CBD66A1BE0F04FB8F2AF7064FEF2B5EE5E33D1F9D347E4C419F
      - SHA256=925AFF03AB009C8E7935CFA389FC7A34482184CC310A8D8F88A25D9A89711E86
  condition: selection
falsepositives:
  - Legitimate services sharing the address; verify against skopnix confidence + last_seen
level: high

How to deploy on Sigma

  1. 1.Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
  2. 2.Run it as a hunt first: every rule ships as status experimental.
  3. 3.Promote to an alert once a week of results is clean on your data.

Check · The processing pipeline must map the logsource (firewall, dns, proxy, webserver, process_creation) to your field names.

References