WMI Persist With Event Filters
Automation
There are many great automated ways to do this.
Metasploit post module
exploit/windows/local/wmi_persistence
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
CALLBACK_INTERVAL 1800000 yes Time between callbacks (In milliseconds). (Default: 1800000).
CLASSNAME UPDATER yes WMI event class name. (Default: UPDATER)
EVENT_ID_TRIGGER 4625 yes Event ID to trigger the payload. (Default: 4625)
PERSISTENCE_METHOD EVENT yes Method to trigger the payload. (Accepted: EVENT, INTERVAL, LOGON, PROCESS, WAITFOR)
PROCESS_TRIGGER CALC.EXE yes The process name to trigger the payload. (Default: CALC.EXE)
SESSION yes The session to run this module on.
USERNAME_TRIGGER BOB yes The username to trigger the payload. (Default: BOB)
WAITFOR_TRIGGER CALL yes The word to trigger the payload. (Default: CALL)
Manual Mode
Check if WMI is enabled, if it is not any
WMIcommand that you execute will attempt to downloadWMIThis download process does log in the
WMI LogCheck if WMI is enabled on the remote system
Check for existing entries
Check for existing event filter consumer bindings that are on the system
Ensure the system is logging event logs for the type of event you want to use
Create your own filter and consumer
Now create the triggering event
Now create your event filter
Create the event consumer
Combine the filter and the comsumer
Ensure Its all working and correct
IOCs Left Behind
Other Logs
Last updated
