Evil-WinRM
Associated threat actors
3 distinct threat actors Mallory has associated with this family across public reporting. Open in Mallory to see the full evidence chain and overlapping campaigns.
“The upload routine matches the PowerShell artifacts of winrm-fs, the library that evil-winrm uses, which makes evil-winrm the most likely tool-transfer framework.”
Attackers deliver the backdoors and their configuration files to compromised systems over WinRM using open-source tools including Evil-WinRM.
Techniques & procedures
10 distinct techniques documented for this family, organized by ATT&CK tactic.
Initial Access
1 technique
Initial Access
`evil-winrm -i 192.168.13.110 -u Administrator@thm-ad.local -H 2dfe...` and `xfreerdp ... /u:Administrator /pth:2dfe...`
Execution
2 techniques
Execution
Detects ... WinRM-related parent process ... spawns schtasks.exe with command-line arguments indicating remote scheduled task creation. This is a common persistence pattern...
The workflow uses PowerShell to download, load, and execute AMSI-bypass, Mimikatz, PowerUp, and NTDS/SAM-dumping scripts, including commands piped into Invoke-Expression.
Persistence
2 techniques
Persistence
Detects ... WinRM-related parent process ... spawns schtasks.exe with command-line arguments indicating remote scheduled task creation. This is a common persistence pattern...
`evil-winrm -i 192.168.13.110 -u Administrator@thm-ad.local -H 2dfe...` and `xfreerdp ... /u:Administrator /pth:2dfe...`
Privilege Escalation
2 techniques
Privilege Escalation
Detects ... WinRM-related parent process ... spawns schtasks.exe with command-line arguments indicating remote scheduled task creation. This is a common persistence pattern...
`evil-winrm -i 192.168.13.110 -u Administrator@thm-ad.local -H 2dfe...` and `xfreerdp ... /u:Administrator /pth:2dfe...`
Stealth
1 technique
Stealth
`evil-winrm -i 192.168.13.110 -u Administrator@thm-ad.local -H 2dfe...` and `xfreerdp ... /u:Administrator /pth:2dfe...`
Defense Impairment
1 technique
Defense Impairment
"We need to patch AMSI using our script" and "From now on, Defender doesn’t have access to your PowerShell sessions." The article also directs users to bypass the PowerShell execution policy with "powershell -ep bypass."
Credential Access
2 techniques
Credential Access
The operator extracted base64-encoded SAM, SYSTEM, and SECURITY registry hives from a Windows host for offline cracking. The dataset also contains a valid Active Directory database (ntds.dit).
Evil-WinRM history logs reveal attempts to copy the AD database from a tunneled domain controller, aiming for full domain compromise.
Lateral Movement
3 techniques
Lateral Movement
If you find any valid credentials via SMB, LFI, or OSINT, immediately attempt to login using evil-winrm to get a stable, interactive shell.
Post-exploitation: evil-winrm, dploot, donpapi, nxc –sam/–lsa on US target.
The walkthrough uses `-H` with Evil-WinRM and `/pth` with FreeRDP to authenticate as Administrator using an NTLM hash, and explicitly describes enabling RDP "via PTH."
Command and Control
1 technique
Command and Control
The harvester and the implant installer were uploaded over WinRM into the Domain Admin profile on the domain controller.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.