Techniques › T1546.013 › AN1245
AN1245 Analytic 1245
Windows · attack.mitre.org · ATT&CK Enterprise v19.2
<p>Defenders can identify PowerShell profile-based persistence by correlating file creation or modification in known profile locations with subsequent PowerShell process launches that do not use the
-NoProfile flag. Profile scripts loading unusual modules or launching external programs, particularly under elevated contexts, are suspicious and may represent adversary persistence or privilege escalation.</p>- Detects
- T1546.013 PowerShell Profile
- Part of
- DET0451 Detection Strategy for PowerShell Profile Persistence via profile.ps1 Modification
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=11 | DC0039 File Creation |
| WinEventLog:Sysmon | EventCode=2 | DC0061 File Modification |
| WinEventLog:Sysmon | EventCode=1 | DC0032 Process Creation |
| WinEventLog:PowerShell | Execution of PowerShell without -NoProfile flag | DC0064 Command Execution |
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 |
|---|---|
ProfilePathList | Custom PowerShell host profiles or redirection to alternate profile paths |
ExecutionContext | Whether profile execution occurs under elevated user (e.g., Administrator, SYSTEM) |
ModuleOrScriptName | Specific modules or external programs loaded within profile |
TimeWindow | Correlation time between profile modification and PowerShell process start |