Explore our new Cybersecurity Terms Glossary, explained by our experts.

View the Glossary View the Glossary
PRIVIA

Cybersecurity Terms Glossary

What Is Evil-WinRM?

Evil-WinRM is a testing client for Windows Remote Management that turns valid credentials into an interactive PowerShell session with file transfer and in-memory execution built in.

Illustration for the cybersecurity term Evil-WinRM
Home / Blog / Cybersecurity Terms / What Is Evil-WinRM?
17 November 2026

What Is Evil-WinRM?

What Is Evil-WinRM?

Evil-WinRM is a command-line client for Windows Remote Management, written in Ruby and maintained by the Hackplayers project. It does nothing that Windows does not already permit. WinRM is Microsoft’s implementation of the WS-Management protocol, it listens on TCP 5985 for HTTP and 5986 for HTTPS, and it is enabled by default on Windows Server. What Evil-WinRM adds is a client built for offensive work rather than for administration.

This is the characteristic shape of modern lateral movement. No exploit, no malware dropped, no vulnerability. A valid credential and a management service that is supposed to be used this way.

What It Requires and What It Provides

Access needs a valid account that is either a local administrator on the target or a member of the Remote Management Users group. Authentication can be by password, by NTLM hash in a pass-the-hash arrangement, or by Kerberos ticket, which matters because a hash recovered from one machine becomes an interactive session on another without the password ever being known.

Once connected, the operator gets a full PowerShell session, plus conveniences that native remoting lacks:

In practice it is often used after credentials are recovered by another tool. A hash dumped by Mimikatz, or an account identified as having WinRM access by NetExec, becomes a shell here.

Why Defenders Should Care About WinRM Specifically

WinRM is unusual among remote access paths in that it is frequently enabled estate-wide and rarely restricted. Group Policy turns it on for manageability, nobody scopes which hosts can originate connections, and the Remote Management Users group accumulates members over the years. The result is a protocol that permits code execution on nearly every Windows host, authenticates with hashes, and is often absent from the network monitoring baseline because it is management traffic.

It is also comparatively quiet. Unlike PsExec-style movement, it does not create a service, so the familiar event 7045 service installation alert does not fire.

Detection

The telemetry exists, but most of it needs enabling.

Hardening

Restrict WinRM listeners to the hosts that need them and limit the source addresses permitted to connect, using the Windows Firewall or IPsec. Audit the Remote Management Users group and remove anyone without a current operational need. Deploy Just Enough Administration so that delegated remote sessions run in a constrained endpoint exposing only the commands a role requires, rather than a full shell. Enforce tiered administration so that a credential recovered from a workstation cannot authenticate to a server, and use LAPS so that local administrator passwords are unique per host. Require HTTPS listeners where WinRM must traverse untrusted segments.

Together these turn an estate-wide execution path into a narrow, monitored one, which is the realistic objective.

At Privia Security, our Infrastructure Security Testing Services test exactly these credential and management path assumptions from inside a Windows domain.

FAQ – Frequently Asked Questions

Is Evil-WinRM an Exploit?

No. It is a client for a management protocol that Windows enables by design, and it requires a valid credential with the right group membership before it does anything. There is no vulnerability involved. That is what makes it effective: the activity resembles legitimate administration, and detection has to rest on who is connecting, from where, and what they run afterwards.

Should We Disable WinRM Entirely?

Rarely practical, since remote management depends on it. The better approach is to narrow it: restrict listeners to hosts that need them, limit permitted source addresses by firewall rule, audit the Remote Management Users group, and deploy Just Enough Administration so delegated sessions expose only the commands a role requires rather than a full PowerShell shell.

Which Log Tells Us Someone Used It?

The Microsoft-Windows-WinRM/Operational log records session creation on the target, and event 4624 with logon type 3 shows the authentication. The most useful signal is process lineage: anything spawned by wsmprovhost.exe is remote execution. PowerShell script block logging, event 4104, captures the script content that was never written to disk.

Does Pass-the-Hash Work Over WinRM?

Yes, when NTLM authentication is permitted, which is why a hash recovered from one machine can produce an interactive session on another without the password ever being recovered. Mitigations are the standard credential hygiene set: tiered administration so workstation credentials cannot reach servers, LAPS for unique local administrator passwords, and the Protected Users group for privileged accounts.

Related Terms

You May Be Interested In These

What Is the Raccoon Attack?

Cybersecurity Terms

17 November 2026

What Is the Raccoon Attack?

Read More
What Is Residual Risk?

Cybersecurity Terms

17 November 2026

What Is Residual Risk?

Read More
What Is a Cloud Cost Anomaly?

Cybersecurity Terms

17 November 2026

What Is a Cloud Cost Anomaly?

Read More