Skip to content
skopnix
← Sigma detections

Sigma · Actor indicator sweep

Whitefly file hash indicators (historical, hunt only)

severity
low
confidence
75/100
generated
14 Nov 2026
Linked actors
Whitefly

2 file hash indicators skopnix attributes to Whitefly, named in published reports without live feed evidence. Retro-hunt only.

False-positive notes

HISTORICAL, HUNT ONLY: do not block on this. These indicators come from published reports and do not meet the bar of the live sweep. 2 indicators. Evidence: 2 with no threat-feed evidence (named in published reports only). No feed sighting date exists for any of them. Screened against reserved space, public known-good lists (CDN / cloud / scanners / top sites), internet-noise reputation when enriched, and sinkhole address lists. Re-validate against last_seen before blocking: infrastructure is re-assigned.

References

title: Skopnix - Whitefly file hash indicators (historical, hunt only)id: 6b390d03-1224-586a-aef0-9506fa74ea0estatus: experimentaldescription: 2 file hash indicators skopnix attributes to Whitefly, named in published reports without live feed evidence. Retro-hunt only.references:  - https://skopnix.com/actors/whiteflyauthor: skopnixdate: '2026-11-14'tags:  - attack.execution  - attack.t1204.002logsource:  category: process_creation  product: windowsdetection:  selection:    Hashes|contains:      - SHA256=7DE8B8B314F2D2FB54F8F8AD4BBA435E8FC58B894B1680E5028C90C0A524CCD9      - SHA256=263DC5A8121D20403BEEEEA452B6F33D51D41C6842D9D19919DEF1F1CB13226C  condition: selectionfalsepositives:  - A legitimate tool or installer carrying the same file hash (rare); verify the file's signer, path and parent process against skopnix confidence + last_seen  - 'Reused or re-registered infrastructure: these indicators are historical'level: low

skopnix-sigma-actor-whitefly-hash-hist-a092693a.yml

How to deploy on Sigma

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