Sysmon event 27
FileBlockExecutable
Channel: Microsoft-Windows-Sysmon/Operational. Category: File Block.
What it records
Logs when Sysmon detects and actively blocks the creation of an executable (PE-format) file, preventing it from being written.
Why it matters
This is a rare Sysmon feature that goes beyond passive logging into active blocking, giving defenders a way to stop a dropped payload from ever landing on disk, with the attempt still fully logged for investigation.
What triggers it
Triggered when a monitored process attempts to write a new PE executable to a path covered by a block rule: most notably malware droppers writing a payload.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Image | The process that attempted to write the executable, which identifies the dropper that Sysmon blocked. |
| TargetFilename | The path the blocked executable was being written to, which shows exactly where the payload would have landed. |
| Hashes | The hash of the blocked file's content, also used as its archive filename, which lets you retrieve and analyze the payload Sysmon prevented from landing. |
In practice
A macro-enabled document opened via WINWORD.EXE spawns a downloader that attempts to write TargetFilename C:\Users\Public\svchost_update.exe. Sysmon's configured block rule intercepts the write before it lands on disk, logs Image as the downloader process, and stores the payload under its Hashes value in the block archive so the analyst can still retrieve and analyze the executable that was stopped.
Sample record
File Block Executed:
RuleName: -
UtcTime: 2024-02-11 09:48:02.775
ProcessGuid: {a1b2c3d4-1234-65a1-0000-0011223344bb}
ProcessId: 4820
User: CORP\jdoe
Image: C:\Windows\System32\cmd.exe
TargetFilename: C:\Users\jdoe\Downloads\invoice.exe
Hashes: SHA256=A1B2C3D4E5F60718293A4B5C6D7E8F90112233445566778899AABBCCDDEEFF00Sources
Paste a record into Event XML or open a log in EVTX Reader.