Skip to content
The ultimate WinRM shell for hacking/pentesting
Branch: master
Clone or download
Latest commit 3f56164 Aug 15, 2019
Type Name Latest commit message Commit time
Failed to load latest commit information.
resources Added logo Aug 14, 2019
.gitignore Added .gitignore file May 28, 2019 Added logo Aug 14, 2019
LICENSE Initial commit May 28, 2019 Added logo Aug 14, 2019
evil-winrm.rb Added certificates support Aug 14, 2019

Evil-WinRM Version-shield Ruby2.3-shield Gem-Version License-shield

The ultimate WinRM shell for hacking/pentesting


Description & Purpose

This shell is the ultimate WinRM shell for hacking/pentesting.

WinRM (Windows Remote Management) is the Microsoft implementation of WS-Management Protocol. A standard SOAP based protocol that allows hardware and operating systems from different vendors to interoperate. Microsoft included it in their Operating Systems in order to make life easier to system adminsitrators.

This program can be used on any Microsoft Windows Servers with this feature enabled (usually at port 5985), of course only if you have credentials and permissions to use it. So we can say that it could be used in a post-exploitation hacking/pentesting phase. The purpose of this program is to provide nice and easy-to-use features for hacking. It can be used with legitimate purposes by system administrators as well but the most of its features are focused on hacking/pentesting stuff.


  • Command History
  • WinRM command completion
  • Local files completion
  • Upload and download files
  • List remote machine services
  • Load Powershell scripts
  • Load in memory dll files bypassing some AVs
  • Load in memory C# (C Sharp) compiled exe files bypassing some AVs
  • Colorization on output messages (can be disabled optionally)
  • SSL and certificates support


Usage: evil-winrm -i IP -u USER [-s SCRIPTS_PATH] [-e EXES_PATH] [-P PORT] [-p PASS] [-U URL] [-S] [-c PUBLIC_KEY_PATH ] [-k PRIVATE_KEY_PATH ]
    -S, --ssl                        Enable SSL
    -c, --pub-key PUBLIC_KEY_PATH    Local path to public key certificate
    -k, --priv-key PRIVATE_KEY_PATH  Local path to private key certificate
    -s, --scripts PS_SCRIPTS_PATH    Powershell scripts local path
    -e, --executables EXES_PATH      C# executables local path
    -i, --ip IP                      Remote host IP or hostname (required)
    -U, --url URL                    Remote url endpoint (default /wsman)
    -u, --user USER                  Username (required)
    -p, --password PASS              Password
    -P, --port PORT                  Remote host port (default 5985)
    -V, --version                    Show version
    -h, --help                       Display this help message


Ruby 2.3 or higher is needed. Some ruby gems are needed as well: winrm >=2.3.2, winrm-fs >=1.3.2, stringio >=0.0.2 and colorize >=0.8.1.

~$ sudo gem install winrm winrm-fs colorize stringio

Installation & Quick Start

  • Step 1. Clone the repo: git clone
  • Step 2. Ready. Just launch it! ~$ cd evil-winrm && ruby evil-winrm.rb -i -u Administrator -p 'MySuperSecr3tPass123!' -s '/home/foo/ps1_scripts/' -e '/home/foo/exe_files/'

If you don't want to put the password in clear text, you can optionally avoid to set -p argument and the password will be prompted preventing to be shown.

To use IPv6, the address must be added to /etc/hosts.

Alternative installation method as ruby gem
  • Step 1. Install it: gem install evil-winrm
  • Step 2. Ready. Just launch it! ~$ evil-winrm -i -u Administrator -p 'MySuperSecr3tPass123!' -s '/home/foo/ps1_scripts/' -e '/home/foo/exe_files/'


Basic commands

  • upload: local files can be auto-completed using tab key. It is recommended to use absolute path for destination to avoid errors. Otherwise you could get uncontrolled errors due Winrm-fs limitations.
    • usage: upload local_path remote_absolute_path
  • download: It is recommended to use absolute paths to avoid errors. Otherwise you could get uncontrolled errors due Winrm-fs limitations.
    • usage: download remote_absolute_path local_path

Note about paths (upload/download): If the file to download is in the initial remote dir, absolute path on first parameter can be avoided in order to use simple file name. Relative paths are not recommended to use and can cause errors on download/upload. Second argument (destination for upload/download) can be blank and in that case it will be uploaded/downloaded to current local dir or initial (landing dir once connected) remote dir.

  • services: list all services. No administrator permissions needed.

  • menu: load the Invoke-Binary and l04d3r-LoadDll functions that we will explain below. When a ps1 is loaded all its functions will be shown up.


Load powershell scripts

  • To load a ps1 file you just have to type the name (auto-completion usnig tab allowed). The scripts must be in the path set at -s argument. Type menu again and see the loaded functions.


Advanced commands

  • Invoke-Binary: allows exes compiled from c# to be executed in memory. The name can be auto-completed using tab key and allows up to 3 parameters. The executables must be in the path set at -e argument.


  • l04d3r-LoadDll: allows loading dll libraries in memory, it is equivalent to: [Reflection.Assembly]::Load([IO.File]::ReadAllBytes("pwn.dll"))

    The dll file can be hosted by smb, http or locally. Once it is loaded type menu, then it is possible to autocomplete all functions.

    l04d3r-LoadDll1 l04d3r-LoadDll2

Extra features

  • To disable colors just modify on code this variable $colors_enabled. Set it to false: $colors_enabled = false


Changelog and project changes can be checked here:


Main author:

Collaborators, developers, documenters, testers and supporters:

Hat tip to:

  • Alamot for his original code.
  • 3v4Si0N for his awesome dll loader.

Disclaimer & License

This script is licensed under LGPLv3+. Direct link to License.

Evil-WinRM should be used for authorized penetration testing and/or nonprofit educational purposes only. Any misuse of this software will not be the responsibility of the author or of any other collaborator. Use it at your own servers and/or with the server owner's permission.

You can’t perform that action at this time.