HackTool: Default PowerSploit and Empire scheduled task persistence
PowerSploit and Empire utilize predictable command-line patterns when creating scheduled tasks for persistence, which can be identified via process creation telemetry.
Triage facts
Revision 1- Applicability
- Windows
- Evidence
- Unknown
- Severity
- High
- Action
- Elevated
- Sources
- 3 public sources
- Freshness
- Revision 1Nov 10, 02:51 UTC
- Detection
- 1 rule
- Source quality
- A2Roughly even chance
PowerSploit and Empire frameworks include modules for maintaining persistence on compromised Windows systems by creating scheduled tasks. These modules often employ default naming conventions and execution flags, specifically targeting task names like 'Updater' and executing PowerShell commands with non-interactive flags. This behavior is observable through process creation logs when schtasks.exe is spawned by powershell.exe or pwsh.exe with specific command-line arguments.
Impact
Successful execution of these modules establishes persistence, allowing attackers to maintain access across system reboots or user logons without requiring manual re-exploitation.
Recommendation
- Deploy the provided Sigma rule to detect the use of default persistence task creation patterns.
- Audit existing scheduled tasks for entries named 'Updater' that execute encoded or base-level PowerShell scripts.
- Review environment-wide use of
schtasks.exespawned by PowerShell to identify potentially unauthorized persistence mechanisms.
Immediate actions
Deploy Sigma rule 56c217c3-2de2-479b-990f-5c109ba8458f to SIEM.
Threat Hunt
Hunt for scheduled tasks named "Updater" or containing "-NonI" and "powershell" in the command line.
Data: Endpoint scheduled task inventory or process creation telemetry
Detection coverage 1
Detect Default PowerSploit/Empire Scheduled Task Creation
highDetects the creation of scheduled tasks using default parameters associated with PowerSploit or Empire persistence modules.
Detection queries are available on the platform. Get full rules →