Techniques › T1204.005 › AN0699
AN0699 Analytic 0699
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Execution of
pip.exe, npm.cmd, or MSI installers within user context, followed by script interpreter startup (e.g., python.exe) or PowerShell with unusual child processes or file writes in %APPDATA%, %TEMP%, or %LOCALAPPDATA%. Defender correlates command-line install tools with Sysmon and Event Logs to trace downstream behavior.</p>- Detects
- T1204.005 Malicious Library
- Part of
- DET0252 User-Initiated Malicious Library Installation via Package Manager (T1204.005)
Log sources and channels
Exactly as MITRE states them in x_mitre_log_source_references. Where a channel is vague, it is vague in the source; kevmap does not tidy it.
| Log source | Channel | Data component |
|---|---|---|
| WinEventLog:Sysmon | EventCode=1 | DC0032 Process Creation |
| WinEventLog:Sysmon | EventCode=11 | DC0039 File Creation |
Mutable elements
Parameters MITRE marks as environment-specific. These are the knobs you are expected to tune; they are why an analytic is not a rule.
| Field | Description |
|---|---|
AllowedParentProcesses | Filter expected automation tools (e.g., enterprise installers, known IDEs) |
InstallPathsToWatch | Suspicious post-install write paths (e.g., %APPDATA%, %TEMP%) |
ExecutableEntropyThreshold | Used for evaluating if dropped files are packed/obfuscated |