Sysmon event 29
FileExecutableDetected
Channel: Microsoft-Windows-Sysmon/Operational. Category: File Creation.
What it records
Logs when Sysmon detects the creation of a new executable (PE-format) file on disk, without blocking it.
Why it matters
Gives targeted visibility specifically into new binaries appearing on disk: a narrower, higher-signal alternative to monitoring all FileCreate events when the goal is catching dropped payloads or compiled tools.
What triggers it
Software installation/updates writing new executables, and malware droppers, downloaders, or living-off-the-land compilation techniques writing a new PE file to disk.
Fields that carry the answer
| Field | What it tells you |
|---|---|
| Image | The process that created the new executable file, which identifies what wrote the PE binary to disk. |
| TargetFilename | The full path of the new executable: the core artifact to inspect, especially if written outside expected install locations. |
| Hashes | Full hash of the new PE file, which supports immediate reputation/IOC matching against threat intel without needing to pull the file for analysis. |
In practice
An MSI installer (msiexec.exe) writes a new file to TargetFilename C:\Users\jsmith\Downloads\setup_tool.exe. Sysmon logs the PE creation along with its Hashes value, letting the analyst immediately check the hash against threat intel, useful for catching a downloader-dropped payload without having to monitor every FileCreate (Event 11) on the host.
Sample record
File Executable Detected:
RuleName: -
UtcTime: 2024-04-02 16:07:44.881
ProcessGuid: {c15c1a86-cc38-661d-9c04-000000002900}
ProcessId: 5320
User: CORP\jsmith
Image: C:\Windows\System32\msiexec.exe
TargetFilename: C:\Users\jsmith\Downloads\setup_tool.exe
Hashes: SHA256=3B5D9A1E7C4F6082A9E1D0C8B7F3A2E4D6C1B9F8A0E3D7C5B2A4F6E8D0C1B9A3Sources
Paste a record into Event XML or open a log in EVTX Reader.