← Sigma detectionsSigma · Actor indicator sweep

Predatory Sparrow file hash indicators

SIGhighconfidence 72/100generated 2026-10-18

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

ATT&CK: T1204.002 mitre ↗
Linked actors: Predatory Sparrow
False positives: Every value is a skopnix indicator tied to Predatory Sparrow 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-predatory-sparrow-hash-a3230df5.ymldownload .yml ↓

title: Skopnix - Predatory Sparrow file hash indicators
id: 6fc290bd-7384-5d53-88cd-d69c738fed31
status: experimental
description: Any of 2 high-confidence file hash indicators skopnix attributes to Predatory Sparrow.
references:
  - https://skopnix.com/actors/predatory-sparrow
author: skopnix
date: '2026-10-18'
tags:
  - attack.execution
  - attack.t1204.002
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Hashes|contains:
      - MD5=837E9BB07D884385D077D4EA77797DF8
      - MD5=B86678403D77EFBDBA3D2B1C93500DFC
  condition: selection
falsepositives:
  - Legitimate services sharing the address; verify against skopnix confidence + last_seen
level: high

How to deploy on Sigma

1.Convert for your SIEM with sigma-cli / pySigma, e.g. sigma convert -t splunk -p sysmon rule.yml.
2.Run it as a hunt first: every rule ships as status experimental.
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

skopnix.com/actors/predatory-sparrow ↗