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

Whitefly file hash indicators

SIGhighconfidence 76/100generated 2026-10-18

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

Linked actors
Whitefly
False positives
Every value is a skopnix indicator tied to Whitefly with confidence >= 76 from >= 2 independent sources, warninglist-clean (reserved / CDN / cloud / scanners / top sites) — re-validate against last_seen before blocking.

Sigma rule

skopnix-sigma-actor-whitefly-hash-8af8ba2b.ymldownload .yml ↓
title: Skopnix - Whitefly file hash indicators
id: cf1acfbf-c242-5bca-b3ec-68df723993c3
status: experimental
description: Any of 2 high-confidence file hash indicators skopnix attributes to Whitefly.
references:
  - https://skopnix.com/actors/whitefly
author: skopnix
date: '2026-10-18'
tags:
  - attack.execution
  - attack.t1204.002
logsource:
  category: process_creation
  product: windows
detection:
  selection:
    Hashes|contains:
      - SHA256=7DE8B8B314F2D2FB54F8F8AD4BBA435E8FC58B894B1680E5028C90C0A524CCD9
      - SHA256=263DC5A8121D20403BEEEEA452B6F33D51D41C6842D9D19919DEF1F1CB13226C
  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