← Sigma detections
Sigma · Actor indicator sweep
Tortoiseshell file hash indicators (historical, hunt only)
- severity
- low
- confidence
- 75/100
- generated
- 14 Nov 2026
- Linked actors
- Tortoiseshell
4 file hash indicators skopnix attributes to Tortoiseshell, 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. 4 indicators. Evidence: 4 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 - Tortoiseshell file hash indicators (historical, hunt only)id: efebd61d-307f-5c03-bb0c-f558620e8826status: experimentaldescription: 4 file hash indicators skopnix attributes to Tortoiseshell, named in published reports without live feed evidence. Retro-hunt only.references: - https://skopnix.com/actors/tortoiseshellauthor: skopnixdate: '2026-11-14'tags: - attack.execution - attack.t1204.002logsource: category: process_creation product: windowsdetection: selection: Hashes|contains: - SHA256=02A3296238A3D127A2E517F4949D31914C15D96726FB4902322C065153B364B2 - SHA256=07D123364D8D04E3FE0BFA4E0E23DDC7050EF039602ECD72BAED70E6553C3AE4 - SHA256=D9AC9C950E5495C9005B04843A40F01FA49D5FD49226CB5B03A055232FFC36F3 - SHA256=F71732F997C53FA45EEF5C988697EB4AA62C8655D8F0BE3268636FC23ADDD193 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: lowskopnix-sigma-actor-tortoiseshell-hash-hist-8a0e0ae1.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.