Note: Call terminate allows you to specify an exit status in terms of a signed integer or a quoted negative value. Both methods essentially function the same by calling TerminateProcess.
Locate Possible Shellcode within process via Injected Thread
Obtain Possible Shellcode within process as Hex
Obtain Possible Shellcode within process as Hex
Remove ACE entries for “everyone”
Disable unwanted windows binaries (via Base64 encoding and removal)
Note: This is one method, not the only way.
Enable windows binaries (via Base64 decoding and removal)
Make multiple files visible and remove ‘superhidden’
Enable Date Accessed Timestamps
Remove BITSAdmin Persistence
Delete Windows Defender excluded files
Open File Extension (e.g. scripts) with certain application (elevated cmd)
Disable Command Prompt
Remediate malicious files
Powershell:
Remediate Persistent WMI Subscriptions
The most important aspect is to locate and remove the CommandLineEventConsumer. This has the malicious command stored within the value ‘CommandLineTemplate’. The below example searches for commands that contain ‘powershell’.
Malicious scheduled tasks
Powershell:
Registry Keys
Unload all users registry keys
Remediate Automatic Load/Run Reg Keys
Powershell:
Prevent Executable from Running.
Note: Load in hives and add particular SID to prevent users running named files, helps prevent for example your IIS service account from running cmd.exe or powershell.exe