Skip to content
skopnix
← Sigma detections

Sigma · CVE exploitation

CVE-2026-96654 exploitation file hash indicators

severity
high
confidence
100/100
generated
18 Nov 2026
Linked CVE
CVE-2026-96654

2 file hash indicators threat feeds tag with CVE-2026-96654, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).

False-positive notes

2 indicators. Evidence: 2 listed by 2 or more independent non-scanner feed publishers. Listed by 2 independent sources in all. Newest feed sighting 2026-11-18, oldest 2026-11-18 (a live actor sweep accepts at most 90 days). 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 - CVE-2026-96654 exploitation file hash indicatorsid: 7ef547dc-6e6b-5b82-9586-a07d6015cda2status: experimentaldescription: 2 file hash indicators threat feeds tag with CVE-2026-96654, each backed by threat-feed evidence (see the FP-safety notes for the exact counts).references:  - https://skopnix.com/cve/CVE-2026-96654author: skopnixdate: '2026-11-18'tags:  - attack.execution  - attack.t1204.002logsource:  category: process_creation  product: linuxdetection:  selection:    Hashes|contains:      - SHA256=2D3C618B21A7E2F8BCD735DA188E44A7609FF3F204832DD0781CD09E4388C9DB      - SHA256=E4593F7938E76DFB40A3FE5358DFAE231EF539A02EF3FDA35BBCCD6D2B7CDC22  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_seenlevel: high

skopnix-sigma-cve-cve-2026-96654-hash-a97fe48d.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.