Sysmon event 26
FileDeleteDetected (File Delete logged)
Channel: Microsoft-Windows-Sysmon/Operational. Category: File Deletion.
What it records
Logs a file deletion, functioning like Event 23 (FileDelete) but without archiving a copy of the deleted file, reducing disk overhead compared to the archiving variant.
Why it matters
Gives the same anti-forensic-cleanup visibility as Event 23 (spotting attackers or malware deleting tools/evidence) without the storage cost of retaining every deleted file, making it more practical for continuous monitoring at scale.
What triggers it
Routine file cleanup/uninstall, plus malware or an intruder deleting dropped tools, staged data, or logs to cover their tracks.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Image | The process that deleted the file. Same investigative value as Event 23, without an archived copy to recover. |
| TargetFilename | The full path of the deleted file. The record of what was destroyed, even though the content itself isn't preserved. |
| Hashes | The hash of the deleted file's content: still lets you match against known-malware hash sets even without the file itself. |
In practice
Image cmd.exe, spawned moments earlier by a suspicious PowerShell process, deletes TargetFilename C:\Users\jsmith\AppData\Local\Temp\stage2.exe right after it finishes executing. Because Event 26 doesn't archive the file like Event 23 does, the analyst is left with only the logged Hashes value to check the deleted binary against threat-intel hash sets, since the content itself can't be recovered from a Sysmon archive.
Sample record
File Delete logged:
RuleName: -
UtcTime: 2024-02-11 09:47:14.409
ProcessGuid: {a1b2c3d4-1234-65a1-0000-0011223344aa}
ProcessId: 6120
User: CORP\jdoe
Image: C:\Windows\Temp\stager.exe
TargetFilename: C:\Users\jdoe\AppData\Local\Temp\payload.tmp
Hashes: SHA256=A1B2C3D4E5F60718293A4B5C6D7E8F90112233445566778899AABBCCDDEEFF00
IsExecutable: falseATT&CK techniques
- T1070.004: T1070.004
Sources
Paste a record into Event XML or open a log in EVTX Reader.