Install guide

How to put each package on a Windows or a Linux host — the package manager lines for Debian, Fedora, Arch and Alpine, the winget, Chocolatey and PowerShell equivalents, how to check the install worked, and how to take it off again. The same commands work on a range host, where the package manager is simulated and nothing is downloaded or executed. Each package also has its own page, linked from the catalog.

Nmap

v7.94Discovery & reconnaissance · package nmap

Host discovery, port scanning and service/version fingerprinting.

Install it

The scripts below install the real Nmap Project (Gordon Lyon) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-nmap.sh

Windows installer (PowerShell)

Install-nmap.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Nmap
```
sudo apt install -y nmap
```

RHEL, Fedora (dnf)

Install Nmap
```
sudo dnf install -y nmap
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Nmap
```
sudo pacman -S --noconfirm nmap
```

Alpine (apk)

Install Nmap
```
sudo apk add nmap
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which nmap
```
Check the version
```
nmap --version
```
The range reports 7.94.

Remove it

Take it off again
```
sudo apt remove --purge nmap
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search nmap
```
Install Nmap
```
winget install --id nmap -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Nmap
```
choco install nmap -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where nmap
```
Check the version
```
nmap --version
```
The range reports 7.94.

Remove it

Take it off again
```
winget uninstall --id nmap
```

Inside the range

Tick it on the launch screen
Under Nmap's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y nmap
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Nmap's own page →

Wireshark

v4.2.2Packet & network traffic analysis · package wireshark

Deep packet inspection of captured traffic.

Install it

The scripts below install the real Wireshark Foundation (formerly Ethereal) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-wireshark.sh

Windows installer (PowerShell)

Install-wireshark.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Wireshark
```
sudo apt install -y wireshark
```

RHEL, Fedora (dnf)

Install Wireshark
```
sudo dnf install -y wireshark
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Wireshark
```
sudo pacman -S --noconfirm wireshark
```

Alpine (apk)

Install Wireshark
```
sudo apk add wireshark
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which wireshark
```
Check the version
```
wireshark --version
```
The range reports 4.2.2.

Remove it

Take it off again
```
sudo apt remove --purge wireshark
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search wireshark
```
Install Wireshark
```
winget install --id wireshark -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Wireshark
```
choco install wireshark -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where wireshark
```
Check the version
```
wireshark --version
```
The range reports 4.2.2.

Remove it

Take it off again
```
winget uninstall --id wireshark
```

Inside the range

Tick it on the launch screen
Under Wireshark's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y wireshark
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Wireshark's own page →

Zeek

v6.0.3Packet & network traffic analysis · package zeek

Network security monitoring: protocol logs, not just packets.

Install it

The scripts below install the real Zeek Project (formerly Bro) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-zeek.sh

Windows installer (PowerShell)

Install-zeek.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Zeek
```
sudo apt install -y zeek
```

RHEL, Fedora (dnf)

Install Zeek
```
sudo dnf install -y zeek
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Zeek
```
sudo pacman -S --noconfirm zeek
```

Alpine (apk)

Install Zeek
```
sudo apk add zeek
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which zeek
```
Check the version
```
zeek --version
```
The range reports 6.0.3.

Remove it

Take it off again
```
sudo apt remove --purge zeek
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install Zeek inside it
```
wsl sudo apt install -y zeek
```

Inside the range

Tick it on the launch screen
Under Zeek's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y zeek
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Zeek's own page →

Snort

v2.9.20Intrusion detection & network monitoring · package snort

Signature-based intrusion detection and prevention.

Install it

The scripts below install the real Cisco / Snort Project package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-snort.sh

Windows installer (PowerShell)

Install-snort.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Snort
```
sudo apt install -y snort
```

RHEL, Fedora (dnf)

Install Snort
```
sudo dnf install -y snort
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Snort
```
sudo pacman -S --noconfirm snort
```

Alpine (apk)

Install Snort
```
sudo apk add snort
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which snort
```
Check the version
```
snort --version
```
The range reports 2.9.20.

Remove it

Take it off again
```
sudo apt remove --purge snort
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search snort
```
Install Snort
```
winget install --id snort -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Snort
```
choco install snort -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where snort
```
Check the version
```
snort --version
```
The range reports 2.9.20.

Remove it

Take it off again
```
winget uninstall --id snort
```

Inside the range

Tick it on the launch screen
Under Snort's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y snort
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Snort's own page →

OpenVAS / Greenbone

v22.4.1Vulnerability scanning · package gvm

Free, full-featured infrastructure vulnerability assessment.

Install it

The scripts below install the real Greenbone Networks package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-openvas.sh

Windows installer (PowerShell)

Install-openvas.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install OpenVAS / Greenbone
```
sudo apt install -y gvm
```

RHEL, Fedora (dnf)

Install OpenVAS / Greenbone
```
sudo dnf install -y gvm
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install OpenVAS / Greenbone
```
sudo pacman -S --noconfirm gvm
```

Alpine (apk)

Install OpenVAS / Greenbone
```
sudo apk add gvm
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which gvm-cli
```
Check the version
```
gvm-cli --version
```
The range reports 22.4.1.

Remove it

Take it off again
```
sudo apt remove --purge gvm
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install OpenVAS / Greenbone inside it
```
wsl sudo apt install -y gvm
```

Inside the range

Tick it on the launch screen
Under OpenVAS / Greenbone's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y gvm
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open OpenVAS / Greenbone's own page →

Probely

v2024.6Vulnerability scanning · package probely-cli

Developer-friendly SaaS DAST for web apps and APIs.

Install it

The scripts below install the real Probely (Snyk) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-probely.sh

Windows installer (PowerShell)

Install-probely.ps1

Probely has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Python (pip)

Install the interpreter tooling
```
sudo apt install -y python3-pip
```
Install Probely
```
python3 -m pip install probely-cli
```
Use a virtual environment on a shared host so the system Python stays clean.

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Probely
```
sudo apt install -y probely-cli
```

Check it worked

Confirm it landed on PATH
```
which probely
```
Check the version
```
probely --version
```
The range reports 2024.6.

Remove it

Take it off again
```
python3 -m pip uninstall probely-cli
```

On Windows

Python (pip)

Install Python

winget install --id Python.Python.3.12 -e

Install Probely
```
py -m pip install probely-cli
```

Check it worked

Confirm it resolves
```
where probely
```
Check the version
```
probely --version
```
The range reports 2024.6.

Remove it

Take it off again
```
winget uninstall --id probely-cli
```

Inside the range

Tick it on the launch screen
Under Probely's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y probely-cli
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Probely's own page →

Acunetix

v24.4Web application security testing · package acunetix

Commercial web vulnerability scanner with proof-based verification.

Install it

The scripts below install the real Invicti Security package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-acunetix.sh

Acunetix is delivered as Vendor installer, so it cannot be installed unattended. Follow the steps on the package page instead.

Windows installer (PowerShell)

Install-acunetix.ps1

Acunetix has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Vendor installer

Licensed product
Invicti Security ships its own installer behind a license. The range provides the console pre-installed so you can practice the workflow.

Check it worked

Confirm it landed on PATH
```
which acunetix
```
Check the version
```
acunetix --version
```
The range reports 24.4.

Remove it

Take it off again
```
sudo apt remove --purge acunetix
```

On Windows

Vendor installer

Licensed product
Invicti Security ships a signed Windows installer behind a license. The range provides the console pre-installed.

Check it worked

Confirm it resolves
```
where acunetix
```
Check the version
```
acunetix --version
```
The range reports 24.4.

Remove it

Take it off again

Remove-Item -Recurse -Force C:\Tools\acunetix

Inside the range

Tick it on the launch screen
Under Acunetix's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y acunetix
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Acunetix's own page →

Burp Suite

v2024.5 (Community-equivalent surface)Web application security testing · package burpsuite

Intercepting proxy and manual web application testing workbench.

Install it

The scripts below install the real PortSwigger package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-burp.sh

Burp Suite is delivered as Vendor installer, so it cannot be installed unattended. Follow the steps on the package page instead.

Windows installer (PowerShell)

Install-burp.ps1

Burp Suite has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Vendor installer

Licensed product
PortSwigger ships its own installer behind a license. The range provides the console pre-installed so you can practice the workflow.

Check it worked

Confirm it landed on PATH
```
which burpsuite
```
Check the version
```
burpsuite --version
```
The range reports 2024.5 (Community-equivalent surface).

Remove it

Take it off again
```
sudo apt remove --purge burpsuite
```

On Windows

Vendor installer

Licensed product
PortSwigger ships a signed Windows installer behind a license. The range provides the console pre-installed.

Check it worked

Confirm it resolves
```
where burpsuite
```
Check the version
```
burpsuite --version
```
The range reports 2024.5 (Community-equivalent surface).

Remove it

Take it off again

Remove-Item -Recurse -Force C:\Tools\burpsuite

Inside the range

Tick it on the launch screen
Under Burp Suite's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y burpsuite
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Burp Suite's own page →

OWASP toolchain (ZAP + Dependency-Check)

vZAP 2.15.0 / Dependency-Check 9.2.0Standards, guidance & secure-development tooling · package zaproxy

Open web security testing and dependency risk analysis, plus OWASP guidance.

Install it

The scripts below install the real OWASP Foundation package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-owasp.sh

Windows installer (PowerShell)

Install-owasp.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install OWASP toolchain (ZAP + Dependency-Check)
```
sudo apt install -y zaproxy
```

RHEL, Fedora (dnf)

Install OWASP toolchain (ZAP + Dependency-Check)
```
sudo dnf install -y zaproxy
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install OWASP toolchain (ZAP + Dependency-Check)
```
sudo pacman -S --noconfirm zaproxy
```

Alpine (apk)

Install OWASP toolchain (ZAP + Dependency-Check)
```
sudo apk add zaproxy
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which zaproxy
```
Check the version
```
zaproxy --version
```
The range reports ZAP 2.15.0 / Dependency-Check 9.2.0.

Remove it

Take it off again
```
sudo apt remove --purge zaproxy
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search zaproxy
```
Install OWASP toolchain (ZAP + Dependency-Check)
```
winget install --id zaproxy -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install OWASP toolchain (ZAP + Dependency-Check)
```
choco install zaproxy -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where zaproxy
```
Check the version
```
zaproxy --version
```
The range reports ZAP 2.15.0 / Dependency-Check 9.2.0.

Remove it

Take it off again
```
winget uninstall --id zaproxy
```

Inside the range

Tick it on the launch screen
Under OWASP toolchain (ZAP + Dependency-Check)'s category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y zaproxy
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open OWASP toolchain (ZAP + Dependency-Check)'s own page →

Wallarm

v4.10Runtime application protection (WAAP) · package wallarm-node

API security and runtime WAAP: block attacks in front of the app.

Install it

The scripts below install the real Wallarm package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-wallarm.sh

Windows installer (PowerShell)

Install-wallarm.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Wallarm
```
sudo apt install -y wallarm-node
```

RHEL, Fedora (dnf)

Install Wallarm
```
sudo dnf install -y wallarm-node
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Wallarm
```
sudo pacman -S --noconfirm wallarm-node
```

Alpine (apk)

Install Wallarm
```
sudo apk add wallarm-node
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which wallarm-cli
```
Check the version
```
wallarm-cli --version
```
The range reports 4.10.

Remove it

Take it off again
```
sudo apt remove --purge wallarm-node
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install Wallarm inside it
```
wsl sudo apt install -y wallarm-node
```

Inside the range

Tick it on the launch screen
Under Wallarm's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y wallarm-node
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Wallarm's own page →

Metasploit Framework

v6.4.9Exploitation frameworks · package metasploit-framework

Exploit, payload and post-exploitation framework.

Install it

The scripts below install the real Rapid7 package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-metasploit.sh

Windows installer (PowerShell)

Install-metasploit.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```

Install Metasploit Framework

sudo apt install -y metasploit-framework

RHEL, Fedora (dnf)

Install Metasploit Framework
```
sudo dnf install -y metasploit-framework
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Metasploit Framework

sudo pacman -S --noconfirm metasploit-framework

Alpine (apk)

Install Metasploit Framework
```
sudo apk add metasploit-framework
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which msfconsole
```
Check the version
```
msfconsole --version
```
The range reports 6.4.9.

Remove it

Take it off again

sudo apt remove --purge metasploit-framework

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search metasploit-framework
```
Install Metasploit Framework
```
winget install --id metasploit-framework -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Metasploit Framework
```
choco install metasploit-framework -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where msfconsole
```
Check the version
```
msfconsole --version
```
The range reports 6.4.9.

Remove it

Take it off again

winget uninstall --id metasploit-framework

Inside the range

Tick it on the launch screen
Under Metasploit Framework's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y metasploit-framework
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Metasploit Framework's own page →

THC-Hydra

v9.5Credential attack & password auditing · package hydra

Parallel online login brute-forcing across many protocols.

Install it

The scripts below install the real The Hacker's Choice package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-hydra.sh

Windows installer (PowerShell)

Install-hydra.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install THC-Hydra
```
sudo apt install -y hydra
```

RHEL, Fedora (dnf)

Install THC-Hydra
```
sudo dnf install -y hydra
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install THC-Hydra
```
sudo pacman -S --noconfirm hydra
```

Alpine (apk)

Install THC-Hydra
```
sudo apk add hydra
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which hydra
```
Check the version
```
hydra --version
```
The range reports 9.5.

Remove it

Take it off again
```
sudo apt remove --purge hydra
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search hydra
```
Install THC-Hydra
```
winget install --id hydra -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install THC-Hydra
```
choco install hydra -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where hydra
```
Check the version
```
hydra --version
```
The range reports 9.5.

Remove it

Take it off again
```
winget uninstall --id hydra
```

Inside the range

Tick it on the launch screen
Under THC-Hydra's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y hydra
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open THC-Hydra's own page →

Impacket

v0.12.0Post-exploitation & lateral movement · package impacket-scripts

Python classes for network protocols — the Windows/AD attack staple.

Install it

The scripts below install the real Fortra (SecureAuth) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-impacket.sh

Windows installer (PowerShell)

Install-impacket.ps1

Impacket has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Python (pip)

Install the interpreter tooling
```
sudo apt install -y python3-pip
```
Install Impacket
```
python3 -m pip install impacket-scripts
```
Use a virtual environment on a shared host so the system Python stays clean.

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Impacket
```
sudo apt install -y impacket-scripts
```

Check it worked

Confirm it landed on PATH
```
which impacket-secretsdump
```
Check the version
```
impacket-secretsdump --version
```
The range reports 0.12.0.

Remove it

Take it off again

python3 -m pip uninstall impacket-scripts

On Windows

Python (pip)

Install Python

winget install --id Python.Python.3.12 -e

Install Impacket
```
py -m pip install impacket-scripts
```

Check it worked

Confirm it resolves
```
where impacket-secretsdump
```
Check the version
```
impacket-secretsdump --version
```
The range reports 0.12.0.

Remove it

Take it off again
```
winget uninstall --id impacket-scripts
```

Inside the range

Tick it on the launch screen
Under Impacket's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y impacket-scripts
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Impacket's own page →

CrackMapExec / NetExec

v1.3.0 (netexec)Post-exploitation & lateral movement · package netexec

Sweep an Active Directory estate for access, shares and quick wins.

Install it

The scripts below install the real Porchetta Industries (community) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-cme.sh

Windows installer (PowerShell)

Install-cme.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Python (pipx)

Install the interpreter tooling
```
sudo apt install -y pipx
```
Install CrackMapExec / NetExec
```
pipx install netexec
```
pipx keeps the tool in its own environment and still puts it on PATH.

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install CrackMapExec / NetExec
```
sudo apt install -y netexec
```

Check it worked

Confirm it landed on PATH
```
which crackmapexec
```
Check the version
```
crackmapexec --version
```
The range reports 1.3.0 (netexec).

Remove it

Take it off again
```
pipx uninstall netexec
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install CrackMapExec / NetExec inside it
```
wsl sudo apt install -y netexec
```

Inside the range

Tick it on the launch screen
Under CrackMapExec / NetExec's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y netexec
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open CrackMapExec / NetExec's own page →

PowerSploit

v3.0.0Post-exploitation & lateral movement · package PowerSploit

PowerShell post-exploitation modules — the classic living-off-the-land kit.

Install it

The scripts below install the real PowerShellMafia (archived, still widely referenced) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-powersploit.sh

No Linux build. Run this one on a Windows host in the range.

Windows installer (PowerShell)

Install-powersploit.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

No Linux build. Run this one on a Windows host in the range.

On Windows

PowerShell Gallery

Allow signed modules for this session

Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned

Install PowerSploit

Install-Module -Name PowerSploit -Scope CurrentUser -Force

Load it
```
Import-Module PowerSploit
```

Check it worked

Confirm it resolves
```
where powersploit
```
Check the version
```
powersploit --version
```
The range reports 3.0.0.

Remove it

Take it off again
```
Uninstall-Module -Name PowerSploit
```

Inside the range

Tick it on the launch screen
Under PowerSploit's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
winget install --id PowerSploit -e
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open PowerSploit's own page →

Luckystrike

v2.0Social engineering & phishing simulation · package Luckystrike

Build weaponised Office documents for phishing simulations.

Install it

The scripts below install the real Curi0usJack (community, archived) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-luckystrike.sh

No Linux build. Run this one on a Windows host in the range.

Windows installer (PowerShell)

Install-luckystrike.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

No Linux build. Run this one on a Windows host in the range.

On Windows

PowerShell Gallery

Allow signed modules for this session

Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned

Install Luckystrike

Install-Module -Name Luckystrike -Scope CurrentUser -Force

Load it
```
Import-Module Luckystrike
```

Check it worked

Confirm it resolves
```
where luckystrike
```
Check the version
```
luckystrike --version
```
The range reports 2.0.

Remove it

Take it off again
```
Uninstall-Module -Name Luckystrike
```

Inside the range

Tick it on the launch screen
Under Luckystrike's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
winget install --id Luckystrike -e
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Luckystrike's own page →

Social-Engineer Toolkit (SET)

v8.0.3Social engineering & phishing simulation · package set

Build phishing campaigns, cloned portals and payload lures.

Install it

The scripts below install the real TrustedSec package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-set.sh

Windows installer (PowerShell)

Install-set.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Social-Engineer Toolkit (SET)
```
sudo apt install -y set
```

RHEL, Fedora (dnf)

Install Social-Engineer Toolkit (SET)
```
sudo dnf install -y set
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Social-Engineer Toolkit (SET)
```
sudo pacman -S --noconfirm set
```

Alpine (apk)

Install Social-Engineer Toolkit (SET)
```
sudo apk add set
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which setoolkit
```
Check the version
```
setoolkit --version
```
The range reports 8.0.3.

Remove it

Take it off again
```
sudo apt remove --purge set
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install Social-Engineer Toolkit (SET) inside it
```
wsl sudo apt install -y set
```

Inside the range

Tick it on the launch screen
Under Social-Engineer Toolkit (SET)'s category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y set
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Social-Engineer Toolkit (SET)'s own page →

BeEF

v0.5.4Exploitation frameworks · package beef-xss

Browser Exploitation Framework — hook a browser, then test what it exposes.

Install it

The scripts below install the real BeEF Project package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-beef.sh

Windows installer (PowerShell)

Install-beef.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install BeEF
```
sudo apt install -y beef-xss
```

RHEL, Fedora (dnf)

Install BeEF
```
sudo dnf install -y beef-xss
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install BeEF
```
sudo pacman -S --noconfirm beef-xss
```

Alpine (apk)

Install BeEF
```
sudo apk add beef-xss
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which beef-xss
```
Check the version
```
beef-xss --version
```
The range reports 0.5.4.

Remove it

Take it off again
```
sudo apt remove --purge beef-xss
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install BeEF inside it
```
wsl sudo apt install -y beef-xss
```

Inside the range

Tick it on the launch screen
Under BeEF's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y beef-xss
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open BeEF's own page →

SQLMap

v1.8.2Web application security testing · package sqlmap

Automated SQL injection discovery, fingerprinting and data extraction.

Install it

The scripts below install the real sqlmapproject package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-sqlmap.sh

Windows installer (PowerShell)

Install-sqlmap.ps1

SQLMap has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Python (pip)

Install the interpreter tooling
```
sudo apt install -y python3-pip
```
Install SQLMap
```
python3 -m pip install sqlmap
```
Use a virtual environment on a shared host so the system Python stays clean.

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install SQLMap
```
sudo apt install -y sqlmap
```

Check it worked

Confirm it landed on PATH
```
which sqlmap
```
Check the version
```
sqlmap --version
```
The range reports 1.8.2.

Remove it

Take it off again
```
python3 -m pip uninstall sqlmap
```

On Windows

Python (pip)

Install Python

winget install --id Python.Python.3.12 -e

Install SQLMap
```
py -m pip install sqlmap
```

Check it worked

Confirm it resolves
```
where sqlmap
```
Check the version
```
sqlmap --version
```
The range reports 1.8.2.

Remove it

Take it off again
```
winget uninstall --id sqlmap
```

Inside the range

Tick it on the launch screen
Under SQLMap's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y sqlmap
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open SQLMap's own page →

Forge Chef (CyberChef)

v10.19.4Data decoding, cryptanalysis & analysis · package cyberchef

Decode, decrypt, hash and analyze data with chained recipes.

Install it

The scripts below install the real GCHQ / CyberChef community package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-cyberchef.sh

Windows installer (PowerShell)

Install-cyberchef.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Forge Chef (CyberChef)
```
sudo apt install -y cyberchef
```

RHEL, Fedora (dnf)

Install Forge Chef (CyberChef)
```
sudo dnf install -y cyberchef
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Forge Chef (CyberChef)
```
sudo pacman -S --noconfirm cyberchef
```

Alpine (apk)

Install Forge Chef (CyberChef)
```
sudo apk add cyberchef
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which cyberchef
```
Check the version
```
cyberchef --version
```
The range reports 10.19.4.

Remove it

Take it off again
```
sudo apt remove --purge cyberchef
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search cyberchef
```
Install Forge Chef (CyberChef)
```
winget install --id cyberchef -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Forge Chef (CyberChef)
```
choco install cyberchef -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where cyberchef
```
Check the version
```
cyberchef --version
```
The range reports 10.19.4.

Remove it

Take it off again
```
winget uninstall --id cyberchef
```

Inside the range

Tick it on the launch screen
Under Forge Chef (CyberChef)'s category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y cyberchef
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Forge Chef (CyberChef)'s own page →

Steghide

v0.5.1Data decoding, cryptanalysis & analysis · package steghide

Recover data hidden inside JPEG and audio carriers.

Install it

The scripts below install the real Steghide project package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-steghide.sh

Windows installer (PowerShell)

Install-steghide.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Steghide
```
sudo apt install -y steghide
```

RHEL, Fedora (dnf)

Install Steghide
```
sudo dnf install -y steghide
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Steghide
```
sudo pacman -S --noconfirm steghide
```

Alpine (apk)

Install Steghide
```
sudo apk add steghide
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which steghide
```
Check the version
```
steghide --version
```
The range reports 0.5.1.

Remove it

Take it off again
```
sudo apt remove --purge steghide
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search steghide
```
Install Steghide
```
winget install --id steghide -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Steghide
```
choco install steghide -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where steghide
```
Check the version
```
steghide --version
```
The range reports 0.5.1.

Remove it

Take it off again
```
winget uninstall --id steghide
```

Inside the range

Tick it on the launch screen
Under Steghide's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y steghide
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Steghide's own page →

zsteg

v0.2.13Data decoding, cryptanalysis & analysis · package zsteg

Detect LSB steganography in PNG and BMP images.

Install it

The scripts below install the real zed-0xff package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-zsteg.sh

Windows installer (PowerShell)

Install-zsteg.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Ruby (gem)

Install Ruby and its headers
```
sudo apt install -y ruby ruby-dev
```
Install zsteg
```
sudo gem install zsteg
```

Check it worked

Confirm it landed on PATH
```
which zsteg
```
Check the version
```
zsteg --version
```
The range reports 0.2.13.

Remove it

Take it off again
```
sudo gem uninstall zsteg
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install zsteg inside it
```
wsl sudo apt install -y zsteg
```

Inside the range

Tick it on the launch screen
Under zsteg's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y zsteg
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open zsteg's own page →

StegSolve

v1.4Data decoding, cryptanalysis & analysis · package stegsolve

Visual bit-plane analysis of image carriers.

Install it

The scripts below install the real Caesum package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-stegsolve.sh

StegSolve is delivered as Release archive, so it cannot be installed unattended. Follow the steps on the package page instead.

Windows installer (PowerShell)

Install-stegsolve.ps1

StegSolve has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Release archive

Fetch the release and check its signature
Compare the published checksum before unpacking anything.
Unpack it under /opt
```
sudo unzip stegsolve.zip -d /opt/
```

Put the launcher on PATH

sudo ln -s /opt/stegsolve/stegsolve /usr/local/bin/stegsolve

Check it worked

Confirm it landed on PATH
```
which stegsolve
```
Check the version
```
stegsolve --version
```
The range reports 1.4.

Remove it

Take it off again
```
sudo apt remove --purge stegsolve
```

On Windows

Release archive

Unblock the download first
```
Unblock-File .\stegsolve.zip
```
Windows marks anything from the internet; unblock it or the extract fails.

Unpack it under C:\Tools

Expand-Archive .\stegsolve.zip -DestinationPath C:\Tools\stegsolve

Put it on PATH

setx PATH "$env:PATH;C:\Tools\stegsolve"

Check it worked

Confirm it resolves
```
where stegsolve
```
Check the version
```
stegsolve --version
```
The range reports 1.4.

Remove it

Take it off again

Remove-Item -Recurse -Force C:\Tools\stegsolve

Inside the range

Tick it on the launch screen
Under StegSolve's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y stegsolve
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open StegSolve's own page →

Audacity

v3.4.2Data decoding, cryptanalysis & analysis · package audacity

Waveform and spectrogram analysis of audio carriers.

Install it

The scripts below install the real Audacity Team package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-audacity.sh

Windows installer (PowerShell)

Install-audacity.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Audacity
```
sudo apt install -y audacity
```

RHEL, Fedora (dnf)

Install Audacity
```
sudo dnf install -y audacity
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Audacity
```
sudo pacman -S --noconfirm audacity
```

Alpine (apk)

Install Audacity
```
sudo apk add audacity
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which audacity
```
Check the version
```
audacity --version
```
The range reports 3.4.2.

Remove it

Take it off again
```
sudo apt remove --purge audacity
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search audacity
```
Install Audacity
```
winget install --id audacity -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Audacity
```
choco install audacity -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where audacity
```
Check the version
```
audacity --version
```
The range reports 3.4.2.

Remove it

Take it off again
```
winget uninstall --id audacity
```

Inside the range

Tick it on the launch screen
Under Audacity's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y audacity
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Audacity's own page →

ExifTool

v12.76Data decoding, cryptanalysis & analysis · package libimage-exiftool-perl

Read metadata from images, audio, PDFs and documents.

Install it

The scripts below install the real Phil Harvey package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-exiftool.sh

Windows installer (PowerShell)

Install-exiftool.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```

Install ExifTool

sudo apt install -y libimage-exiftool-perl

RHEL, Fedora (dnf)

Install ExifTool
```
sudo dnf install -y libimage-exiftool-perl
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install ExifTool

sudo pacman -S --noconfirm libimage-exiftool-perl

Alpine (apk)

Install ExifTool
```
sudo apk add libimage-exiftool-perl
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which exiftool
```
Check the version
```
exiftool --version
```
The range reports 12.76.

Remove it

Take it off again

sudo apt remove --purge libimage-exiftool-perl

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search libimage-exiftool-perl
```
Install ExifTool
```
winget install --id libimage-exiftool-perl -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install ExifTool
```
choco install libimage-exiftool-perl -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where exiftool
```
Check the version
```
exiftool --version
```
The range reports 12.76.

Remove it

Take it off again

winget uninstall --id libimage-exiftool-perl

Inside the range

Tick it on the launch screen
Under ExifTool's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y libimage-exiftool-perl
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open ExifTool's own page →

Suricata

v7.0.4Intrusion detection & network monitoring · package suricata

High-performance IDS/IPS/NSM with EVE JSON telemetry.

Install it

The scripts below install the real Open Information Security Foundation package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-suricata.sh

Windows installer (PowerShell)

Install-suricata.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Suricata
```
sudo apt install -y suricata
```

RHEL, Fedora (dnf)

Install Suricata
```
sudo dnf install -y suricata
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Suricata
```
sudo pacman -S --noconfirm suricata
```

Alpine (apk)

Install Suricata
```
sudo apk add suricata
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which suricata
```
Check the version
```
suricata --version
```
The range reports 7.0.4.

Remove it

Take it off again
```
sudo apt remove --purge suricata
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install Suricata inside it
```
wsl sudo apt install -y suricata
```

Inside the range

Tick it on the launch screen
Under Suricata's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y suricata
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Suricata's own page →

tcpdump

v4.99.4Packet & network traffic analysis · package tcpdump

Command-line packet capture and BPF filtering.

Install it

The scripts below install the real The Tcpdump Group package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-tcpdump.sh

Windows installer (PowerShell)

Install-tcpdump.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install tcpdump
```
sudo apt install -y tcpdump
```

RHEL, Fedora (dnf)

Install tcpdump
```
sudo dnf install -y tcpdump
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install tcpdump
```
sudo pacman -S --noconfirm tcpdump
```

Alpine (apk)

Install tcpdump
```
sudo apk add tcpdump
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which tcpdump
```
Check the version
```
tcpdump --version
```
The range reports 4.99.4.

Remove it

Take it off again
```
sudo apt remove --purge tcpdump
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install tcpdump inside it
```
wsl sudo apt install -y tcpdump
```

Inside the range

Tick it on the launch screen
Under tcpdump's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y tcpdump
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open tcpdump's own page →

Sysinternals Sysmon

v15.15Endpoint telemetry & host instrumentation · package sysinternals-sysmon

Deep Windows endpoint telemetry: process, network, image-load, WMI.

Install it

The scripts below install the real Microsoft Sysinternals package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-sysmon.sh

No Linux build. Run this one on a Windows host in the range.

Windows installer (PowerShell)

Install-sysmon.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

No Linux build. Run this one on a Windows host in the range.

On Windows

PowerShell Gallery

Allow signed modules for this session

Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned

Install Sysinternals Sysmon

Install-Module -Name sysinternals-sysmon -Scope CurrentUser -Force

Load it
```
Import-Module sysinternals-sysmon
```

Check it worked

Confirm it resolves
```
where sysmon
```
Check the version
```
sysmon --version
```
The range reports 15.15.

Remove it

Take it off again

Uninstall-Module -Name sysinternals-sysmon

Inside the range

Tick it on the launch screen
Under Sysinternals Sysmon's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
winget install --id sysinternals-sysmon -e
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Sysinternals Sysmon's own page →

Sysinternals Suite

v2024.06Endpoint telemetry & host instrumentation · package sysinternals-suite

Process Explorer, Autoruns, Process Monitor, PsExec and friends.

Install it

Linux installer (shell script)

install-sysinternals.sh

No Linux build. Run this one on a Windows host in the range.

Windows installer (PowerShell)

Install-sysinternals.ps1

Sysinternals Suite has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

No Linux build. Run this one on a Windows host in the range.

On Windows

Release archive

Unblock the download first
```
Unblock-File .\sysinternals-suite.zip
```
Windows marks anything from the internet; unblock it or the extract fails.

Unpack it under C:\Tools

Expand-Archive .\sysinternals-suite.zip -DestinationPath C:\Tools\sysinternals-suite

Put it on PATH

setx PATH "$env:PATH;C:\Tools\sysinternals-suite"

Check it worked

Confirm it resolves
```
where procexp
```
Check the version
```
procexp --version
```
The range reports 2024.06.

Remove it

Take it off again

Remove-Item -Recurse -Force C:\Tools\sysinternals-suite

Inside the range

Tick it on the launch screen
Under Sysinternals Suite's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
winget install --id sysinternals-suite -e
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Sysinternals Suite's own page →

Osquery

v5.12.1Endpoint telemetry & host instrumentation · package osquery

Query an endpoint like it's a database — SQL over host state.

Install it

The scripts below install the real Linux Foundation (originally Facebook) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-osquery.sh

Windows installer (PowerShell)

Install-osquery.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Osquery
```
sudo apt install -y osquery
```

RHEL, Fedora (dnf)

Install Osquery
```
sudo dnf install -y osquery
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Osquery
```
sudo pacman -S --noconfirm osquery
```

Alpine (apk)

Install Osquery
```
sudo apk add osquery
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which osqueryi
```
Check the version
```
osqueryi --version
```
The range reports 5.12.1.

Remove it

Take it off again
```
sudo apt remove --purge osquery
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search osquery
```
Install Osquery
```
winget install --id osquery -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Osquery
```
choco install osquery -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where osqueryi
```
Check the version
```
osqueryi --version
```
The range reports 5.12.1.

Remove it

Take it off again
```
winget uninstall --id osquery
```

Inside the range

Tick it on the launch screen
Under Osquery's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y osquery
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Osquery's own page →

Volatility 3

v2.7.0Digital forensics & reverse engineering · package volatility3

Memory forensics: reconstruct processes, DLLs, network state from a dump.

Install it

The scripts below install the real Volatility Foundation package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-volatility.sh

Windows installer (PowerShell)

Install-volatility.ps1

Volatility 3 has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Python (pip)

Install the interpreter tooling
```
sudo apt install -y python3-pip
```
Install Volatility 3
```
python3 -m pip install volatility3
```
Use a virtual environment on a shared host so the system Python stays clean.

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Volatility 3
```
sudo apt install -y volatility3
```

Check it worked

Confirm it landed on PATH
```
which vol
```
Check the version
```
vol --version
```
The range reports 2.7.0.

Remove it

Take it off again
```
python3 -m pip uninstall volatility3
```

On Windows

Python (pip)

Install Python

winget install --id Python.Python.3.12 -e

Install Volatility 3
```
py -m pip install volatility3
```

Check it worked

Confirm it resolves
```
where vol
```
Check the version
```
vol --version
```
The range reports 2.7.0.

Remove it

Take it off again
```
winget uninstall --id volatility3
```

Inside the range

Tick it on the launch screen
Under Volatility 3's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y volatility3
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Volatility 3's own page →

Ghidra

v11.1.2Digital forensics & reverse engineering · package ghidra

Software reverse-engineering suite: disassembler and decompiler.

Install it

The scripts below install the real National Security Agency package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-ghidra.sh

Ghidra is delivered as Release archive, so it cannot be installed unattended. Follow the steps on the package page instead.

Windows installer (PowerShell)

Install-ghidra.ps1

Ghidra has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Release archive

Fetch the release and check its signature
Compare the published checksum before unpacking anything.
Unpack it under /opt
```
sudo unzip ghidra.zip -d /opt/
```

Put the launcher on PATH

sudo ln -s /opt/ghidra/ghidra /usr/local/bin/ghidra

Check it worked

Confirm it landed on PATH
```
which ghidra
```
Check the version
```
ghidra --version
```
The range reports 11.1.2.

Remove it

Take it off again
```
sudo apt remove --purge ghidra
```

On Windows

Release archive

Unblock the download first
```
Unblock-File .\ghidra.zip
```
Windows marks anything from the internet; unblock it or the extract fails.

Unpack it under C:\Tools

Expand-Archive .\ghidra.zip -DestinationPath C:\Tools\ghidra

Put it on PATH
```
setx PATH "$env:PATH;C:\Tools\ghidra"
```

Check it worked

Confirm it resolves
```
where ghidra
```
Check the version
```
ghidra --version
```
The range reports 11.1.2.

Remove it

Take it off again

Remove-Item -Recurse -Force C:\Tools\ghidra

Inside the range

Tick it on the launch screen
Under Ghidra's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y ghidra
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Ghidra's own page →

YARA

v4.5.1Digital forensics & reverse engineering · package yara

Pattern-matching engine for classifying and identifying malware.

Install it

The scripts below install the real VirusTotal package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-yara.sh

Windows installer (PowerShell)

Install-yara.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install YARA
```
sudo apt install -y yara
```

RHEL, Fedora (dnf)

Install YARA
```
sudo dnf install -y yara
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install YARA
```
sudo pacman -S --noconfirm yara
```

Alpine (apk)

Install YARA
```
sudo apk add yara
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which yara
```
Check the version
```
yara --version
```
The range reports 4.5.1.

Remove it

Take it off again
```
sudo apt remove --purge yara
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search yara
```
Install YARA
```
winget install --id yara -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install YARA
```
choco install yara -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where yara
```
Check the version
```
yara --version
```
The range reports 4.5.1.

Remove it

Take it off again
```
winget uninstall --id yara
```

Inside the range

Tick it on the launch screen
Under YARA's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y yara
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open YARA's own page →

TheHive

v5.2.7Threat intelligence & case management · package thehive

Collaborative incident-response case management.

Install it

The scripts below install the real StrangeBee package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-thehive.sh

Windows installer (PowerShell)

Install-thehive.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install TheHive
```
sudo apt install -y thehive
```

RHEL, Fedora (dnf)

Install TheHive
```
sudo dnf install -y thehive
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install TheHive
```
sudo pacman -S --noconfirm thehive
```

Alpine (apk)

Install TheHive
```
sudo apk add thehive
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which thehive
```
Check the version
```
thehive --version
```
The range reports 5.2.7.

Remove it

Take it off again
```
sudo apt remove --purge thehive
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install TheHive inside it
```
wsl sudo apt install -y thehive
```

Inside the range

Tick it on the launch screen
Under TheHive's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y thehive
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open TheHive's own page →

MISP

v2.4.194Threat intelligence & case management · package misp

Threat-intel sharing platform: events, attributes, IOCs, sightings.

Install it

The scripts below install the real MISP Project / CIRCL package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-misp.sh

Windows installer (PowerShell)

Install-misp.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Upstream install script

Read the script before you run it
```
curl -fsSL https://misp.range.local/install.sh -o install.sh
```
Piping an unread script straight into a shell is how estates get owned.
Run the installer
```
sudo bash install.sh
```

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install MISP
```
sudo apt install -y misp
```

Check it worked

Confirm it landed on PATH
```
which misp-cli
```
Check the version
```
misp-cli --version
```
The range reports 2.4.194.

Remove it

Take it off again
```
sudo apt remove --purge misp
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install MISP inside it
```
wsl sudo apt install -y misp
```

Inside the range

Tick it on the launch screen
Under MISP's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y misp
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open MISP's own page →

Atomic Red Team

v24.06Post-exploitation & lateral movement · package invoke-atomicredteam

MITRE ATT&CK-mapped atomic test harness (Invoke-AtomicTest).

Install it

The scripts below install the real Red Canary package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-atomic.sh

Windows installer (PowerShell)

Install-atomic.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```

Install Atomic Red Team

sudo apt install -y invoke-atomicredteam

RHEL, Fedora (dnf)

Install Atomic Red Team
```
sudo dnf install -y invoke-atomicredteam
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Atomic Red Team

sudo pacman -S --noconfirm invoke-atomicredteam

Alpine (apk)

Install Atomic Red Team
```
sudo apk add invoke-atomicredteam
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which invoke-atomictest
```
Check the version
```
invoke-atomictest --version
```
The range reports 24.06.

Remove it

Take it off again

sudo apt remove --purge invoke-atomicredteam

On Windows

PowerShell Gallery

Allow signed modules for this session

Set-ExecutionPolicy -Scope Process -ExecutionPolicy RemoteSigned

Install Atomic Red Team

Install-Module -Name invoke-atomicredteam -Scope CurrentUser -Force

Load it
```
Import-Module invoke-atomicredteam
```

Check it worked

Confirm it resolves
```
where invoke-atomictest
```
Check the version
```
invoke-atomictest --version
```
The range reports 24.06.

Remove it

Take it off again

Uninstall-Module -Name invoke-atomicredteam

Inside the range

Tick it on the launch screen
Under Atomic Red Team's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y invoke-atomicredteam
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Atomic Red Team's own page →

John the Ripper

v1.9.0-jumbo-1Credential attack & password auditing · package john

Offline password cracker across dozens of hash formats.

Install it

The scripts below install the real Openwall package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-johntheripper.sh

Windows installer (PowerShell)

Install-johntheripper.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install John the Ripper
```
sudo apt install -y john
```

RHEL, Fedora (dnf)

Install John the Ripper
```
sudo dnf install -y john
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install John the Ripper
```
sudo pacman -S --noconfirm john
```

Alpine (apk)

Install John the Ripper
```
sudo apk add john
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which john
```
Check the version
```
john --version
```
The range reports 1.9.0-jumbo-1.

Remove it

Take it off again
```
sudo apt remove --purge john
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search john
```
Install John the Ripper
```
winget install --id john -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install John the Ripper
```
choco install john -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where john
```
Check the version
```
john --version
```
The range reports 1.9.0-jumbo-1.

Remove it

Take it off again
```
winget uninstall --id john
```

Inside the range

Tick it on the launch screen
Under John the Ripper's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y john
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open John the Ripper's own page →

Hashcat

v6.2.6Credential attack & password auditing · package hashcat

GPU-class password recovery across hundreds of hash modes.

Install it

The scripts below install the real hashcat.net package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-hashcat.sh

Windows installer (PowerShell)

Install-hashcat.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Hashcat
```
sudo apt install -y hashcat
```

RHEL, Fedora (dnf)

Install Hashcat
```
sudo dnf install -y hashcat
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Hashcat
```
sudo pacman -S --noconfirm hashcat
```

Alpine (apk)

Install Hashcat
```
sudo apk add hashcat
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which hashcat
```
Check the version
```
hashcat --version
```
The range reports 6.2.6.

Remove it

Take it off again
```
sudo apt remove --purge hashcat
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search hashcat
```
Install Hashcat
```
winget install --id hashcat -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Hashcat
```
choco install hashcat -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where hashcat
```
Check the version
```
hashcat --version
```
The range reports 6.2.6.

Remove it

Take it off again
```
winget uninstall --id hashcat
```

Inside the range

Tick it on the launch screen
Under Hashcat's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y hashcat
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Hashcat's own page →

Aircrack-ng

v1.7Credential attack & password auditing · package aircrack-ng

Wi-Fi auditing suite: capture, replay and WPA-PSK cracking.

Install it

The scripts below install the real Aircrack-ng Project package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-aircrack.sh

Windows installer (PowerShell)

Install-aircrack.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Aircrack-ng
```
sudo apt install -y aircrack-ng
```

RHEL, Fedora (dnf)

Install Aircrack-ng
```
sudo dnf install -y aircrack-ng
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Aircrack-ng
```
sudo pacman -S --noconfirm aircrack-ng
```

Alpine (apk)

Install Aircrack-ng
```
sudo apk add aircrack-ng
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which aircrack-ng
```
Check the version
```
aircrack-ng --version
```
The range reports 1.7.

Remove it

Take it off again
```
sudo apt remove --purge aircrack-ng
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install Aircrack-ng inside it
```
wsl sudo apt install -y aircrack-ng
```

Inside the range

Tick it on the launch screen
Under Aircrack-ng's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y aircrack-ng
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Aircrack-ng's own page →

Responder

v3.1.4Credential attack & password auditing · package responder

LLMNR/NBT-NS/mDNS poisoner and rogue authentication server.

Install it

The scripts below install the real Laurent Gaffié package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-responder.sh

Windows installer (PowerShell)

Install-responder.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Responder
```
sudo apt install -y responder
```

RHEL, Fedora (dnf)

Install Responder
```
sudo dnf install -y responder
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Responder
```
sudo pacman -S --noconfirm responder
```

Alpine (apk)

Install Responder
```
sudo apk add responder
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which responder
```
Check the version
```
responder --version
```
The range reports 3.1.4.

Remove it

Take it off again
```
sudo apt remove --purge responder
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install Responder inside it
```
wsl sudo apt install -y responder
```

Inside the range

Tick it on the launch screen
Under Responder's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y responder
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Responder's own page →

BloodHound

v5.13.0Post-exploitation & lateral movement · package bloodhound

Active Directory attack-path analysis with a graph database.

Install it

The scripts below install the real SpecterOps package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-bloodhound.sh

Windows installer (PowerShell)

Install-bloodhound.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install BloodHound
```
sudo apt install -y bloodhound
```

RHEL, Fedora (dnf)

Install BloodHound
```
sudo dnf install -y bloodhound
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install BloodHound
```
sudo pacman -S --noconfirm bloodhound
```

Alpine (apk)

Install BloodHound
```
sudo apk add bloodhound
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which bloodhound
```
Check the version
```
bloodhound --version
```
The range reports 5.13.0.

Remove it

Take it off again
```
sudo apt remove --purge bloodhound
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search bloodhound
```
Install BloodHound
```
winget install --id bloodhound -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install BloodHound
```
choco install bloodhound -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where bloodhound
```
Check the version
```
bloodhound --version
```
The range reports 5.13.0.

Remove it

Take it off again
```
winget uninstall --id bloodhound
```

Inside the range

Tick it on the launch screen
Under BloodHound's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y bloodhound
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open BloodHound's own page →

Mimikatz

v2.2.0 (20231121)Credential attack & password auditing · package mimikatz

Extract Windows credentials and Kerberos tickets from memory.

Install it

The scripts below install the real Benjamin Delpy (gentilkiwi) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-mimikatz.sh

No Linux build. Run this one on a Windows host in the range.

Windows installer (PowerShell)

Install-mimikatz.ps1

Mimikatz has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

No Linux build. Run this one on a Windows host in the range.

On Windows

Release archive

Unblock the download first
```
Unblock-File .\mimikatz.zip
```
Windows marks anything from the internet; unblock it or the extract fails.

Unpack it under C:\Tools

Expand-Archive .\mimikatz.zip -DestinationPath C:\Tools\mimikatz

Put it on PATH
```
setx PATH "$env:PATH;C:\Tools\mimikatz"
```

Check it worked

Confirm it resolves
```
where mimikatz
```
Check the version
```
mimikatz --version
```
The range reports 2.2.0 (20231121).

Remove it

Take it off again

Remove-Item -Recurse -Force C:\Tools\mimikatz

Inside the range

Tick it on the launch screen
Under Mimikatz's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
winget install --id mimikatz -e
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Mimikatz's own page →

Nikto

v2.5.0Web application security testing · package nikto

Web server misconfiguration and known-issue scanner.

Install it

The scripts below install the real CIRT.net package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-nikto.sh

Windows installer (PowerShell)

Install-nikto.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Nikto
```
sudo apt install -y nikto
```

RHEL, Fedora (dnf)

Install Nikto
```
sudo dnf install -y nikto
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Nikto
```
sudo pacman -S --noconfirm nikto
```

Alpine (apk)

Install Nikto
```
sudo apk add nikto
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which nikto
```
Check the version
```
nikto --version
```
The range reports 2.5.0.

Remove it

Take it off again
```
sudo apt remove --purge nikto
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search nikto
```
Install Nikto
```
winget install --id nikto -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Nikto
```
choco install nikto -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where nikto
```
Check the version
```
nikto --version
```
The range reports 2.5.0.

Remove it

Take it off again
```
winget uninstall --id nikto
```

Inside the range

Tick it on the launch screen
Under Nikto's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y nikto
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Nikto's own page →

Gobuster

v3.6Web application security testing · package gobuster

Content, DNS and virtual-host brute-force discovery.

Install it

The scripts below install the real OJ Reeves package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-gobuster.sh

Windows installer (PowerShell)

Install-gobuster.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Gobuster
```
sudo apt install -y gobuster
```

RHEL, Fedora (dnf)

Install Gobuster
```
sudo dnf install -y gobuster
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Gobuster
```
sudo pacman -S --noconfirm gobuster
```

Alpine (apk)

Install Gobuster
```
sudo apk add gobuster
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which gobuster
```
Check the version
```
gobuster --version
```
The range reports 3.6.

Remove it

Take it off again
```
sudo apt remove --purge gobuster
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search gobuster
```
Install Gobuster
```
winget install --id gobuster -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Gobuster
```
choco install gobuster -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where gobuster
```
Check the version
```
gobuster --version
```
The range reports 3.6.

Remove it

Take it off again
```
winget uninstall --id gobuster
```

Inside the range

Tick it on the launch screen
Under Gobuster's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y gobuster
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Gobuster's own page →

ffuf

v2.1.0Web application security testing · package ffuf

Fast web fuzzer for paths, parameters and headers.

Install it

The scripts below install the real Joona Hoikkala package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-ffuf.sh

Windows installer (PowerShell)

Install-ffuf.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install ffuf
```
sudo apt install -y ffuf
```

RHEL, Fedora (dnf)

Install ffuf
```
sudo dnf install -y ffuf
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install ffuf
```
sudo pacman -S --noconfirm ffuf
```

Alpine (apk)

Install ffuf
```
sudo apk add ffuf
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which ffuf
```
Check the version
```
ffuf --version
```
The range reports 2.1.0.

Remove it

Take it off again
```
sudo apt remove --purge ffuf
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search ffuf
```
Install ffuf
```
winget install --id ffuf -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install ffuf
```
choco install ffuf -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where ffuf
```
Check the version
```
ffuf --version
```
The range reports 2.1.0.

Remove it

Take it off again
```
winget uninstall --id ffuf
```

Inside the range

Tick it on the launch screen
Under ffuf's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y ffuf
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open ffuf's own page →

Cloud CLI (aws-compatible)

v2.15.30Discovery & reconnaissance · package awscli

Enumerate identities, keys, buckets and control-plane events.

Install it

The scripts below install the real Range control plane package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-awscli.sh

Windows installer (PowerShell)

Install-awscli.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Cloud CLI (aws-compatible)
```
sudo apt install -y awscli
```

RHEL, Fedora (dnf)

Install Cloud CLI (aws-compatible)
```
sudo dnf install -y awscli
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Cloud CLI (aws-compatible)
```
sudo pacman -S --noconfirm awscli
```

Alpine (apk)

Install Cloud CLI (aws-compatible)
```
sudo apk add awscli
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which aws
```
Check the version
```
aws --version
```
The range reports 2.15.30.

Remove it

Take it off again
```
sudo apt remove --purge awscli
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search awscli
```
Install Cloud CLI (aws-compatible)
```
winget install --id awscli -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Cloud CLI (aws-compatible)
```
choco install awscli -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where aws
```
Check the version
```
aws --version
```
The range reports 2.15.30.

Remove it

Take it off again
```
winget uninstall --id awscli
```

Inside the range

Tick it on the launch screen
Under Cloud CLI (aws-compatible)'s category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y awscli
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Cloud CLI (aws-compatible)'s own page →

Trivy

v0.53.0Vulnerability scanning · package trivy

Container, filesystem and IaC vulnerability scanner.

Install it

The scripts below install the real Aqua Security package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-trivy.sh

Windows installer (PowerShell)

Install-trivy.ps1

No native Windows build. Use a Linux host in the range, or run it under WSL.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Trivy
```
sudo apt install -y trivy
```

RHEL, Fedora (dnf)

Install Trivy
```
sudo dnf install -y trivy
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Trivy
```
sudo pacman -S --noconfirm trivy
```

Alpine (apk)

Install Trivy
```
sudo apk add trivy
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which trivy
```
Check the version
```
trivy --version
```
The range reports 0.53.0.

Remove it

Take it off again
```
sudo apt remove --purge trivy
```

On Windows

No native Windows build. Use a Linux host in the range, or run it under WSL.

Windows Subsystem for Linux

Install a Linux userland on the Windows host
```
wsl --install -d Ubuntu
```
The upstream project has no native Windows build; WSL is the usual way round it.
Install Trivy inside it
```
wsl sudo apt install -y trivy
```

Inside the range

Tick it on the launch screen
Under Trivy's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y trivy
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Trivy's own page →

Semgrep

v1.79.0Standards, guidance & secure-development tooling · package semgrep

Lightweight static analysis with pattern-matching rules.

Install it

The scripts below install the real Semgrep Inc. package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-semgrep.sh

Windows installer (PowerShell)

Install-semgrep.ps1

Semgrep has no unattended Windows install. Follow the steps on the package page.

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Python (pip)

Install the interpreter tooling
```
sudo apt install -y python3-pip
```
Install Semgrep
```
python3 -m pip install semgrep
```
Use a virtual environment on a shared host so the system Python stays clean.

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Semgrep
```
sudo apt install -y semgrep
```

Check it worked

Confirm it landed on PATH
```
which semgrep
```
Check the version
```
semgrep --version
```
The range reports 1.79.0.

Remove it

Take it off again
```
python3 -m pip uninstall semgrep
```

On Windows

Python (pip)

Install Python

winget install --id Python.Python.3.12 -e

Install Semgrep
```
py -m pip install semgrep
```

Check it worked

Confirm it resolves
```
where semgrep
```
Check the version
```
semgrep --version
```
The range reports 1.79.0.

Remove it

Take it off again
```
winget uninstall --id semgrep
```

Inside the range

Tick it on the launch screen
Under Semgrep's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y semgrep
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Semgrep's own page →

CBOM Scanner

v1.4.0Standards, guidance & secure-development tooling · package cbom-scan

Cryptographic discovery and post-quantum readiness with a CycloneDX 1.6 CBOM.

Install it

The scripts below install the real CycloneDX CBOM community (CipherIQ / OQS Scanner alike) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-cbom-scan.sh

Windows installer (PowerShell)

Install-cbom-scan.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install CBOM Scanner
```
sudo apt install -y cbom-scan
```

RHEL, Fedora (dnf)

Install CBOM Scanner
```
sudo dnf install -y cbom-scan
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install CBOM Scanner
```
sudo pacman -S --noconfirm cbom-scan
```

Alpine (apk)

Install CBOM Scanner
```
sudo apk add cbom-scan
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which cbom-scan
```
Check the version
```
cbom-scan --version
```
The range reports 1.4.0.

Remove it

Take it off again
```
sudo apt remove --purge cbom-scan
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search cbom-scan
```
Install CBOM Scanner
```
winget install --id cbom-scan -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install CBOM Scanner
```
choco install cbom-scan -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where cbom-scan
```
Check the version
```
cbom-scan --version
```
The range reports 1.4.0.

Remove it

Take it off again
```
winget uninstall --id cbom-scan
```

Inside the range

Tick it on the launch screen
Under CBOM Scanner's category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y cbom-scan
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open CBOM Scanner's own page →

Open Quantum Safe (liboqs + oqs-provider)

v0.14.0Standards, guidance & secure-development tooling · package liboqs-tools

Post-quantum KEMs and signatures beyond the NIST set, for comparison and testing.

Install it

The scripts below install the real Open Quantum Safe project (Linux Foundation PQCA) package on your own machine — read them first, and run them somewhere you are allowed to change. Inside the range, one press puts the simulated package on your next machine.

Linux installer (shell script)

install-liboqs.sh

Windows installer (PowerShell)

Install-liboqs.ps1

On a range machine

Add it to your kit and every machine you launch comes with it.

On Linux

Debian, Ubuntu, Kali (apt)

Refresh the package lists
```
sudo apt update
```
Install Open Quantum Safe (liboqs + oqs-provider)
```
sudo apt install -y liboqs-tools
```

RHEL, Fedora (dnf)

Install Open Quantum Safe (liboqs + oqs-provider)
```
sudo dnf install -y liboqs-tools
```
Package names drift between distributions; search first if this one misses.

Arch (pacman)

Install Open Quantum Safe (liboqs + oqs-provider)
```
sudo pacman -S --noconfirm liboqs-tools
```

Alpine (apk)

Install Open Quantum Safe (liboqs + oqs-provider)
```
sudo apk add liboqs-tools
```
Package names drift between distributions; search first if this one misses.

Check it worked

Confirm it landed on PATH
```
which oqs-bench
```
Check the version
```
oqs-bench --version
```
The range reports 0.14.0.

Remove it

Take it off again
```
sudo apt remove --purge liboqs-tools
```

On Windows

Windows Package Manager (winget)

Search the catalog
```
winget search liboqs-tools
```
Install Open Quantum Safe (liboqs + oqs-provider)
```
winget install --id liboqs-tools -e
```
Package names drift between distributions; search first if this one misses.

Chocolatey (choco)

Install Open Quantum Safe (liboqs + oqs-provider)
```
choco install liboqs-tools -y
```
Run the shell as administrator.

Check it worked

Confirm it resolves
```
where oqs-bench
```
Check the version
```
oqs-bench --version
```
The range reports 0.14.0.

Remove it

Take it off again
```
winget uninstall --id liboqs-tools
```

Inside the range

Tick it on the launch screen
Under Open Quantum Safe (liboqs + oqs-provider)'s category on the advanced tool shelf. A lab that depends on it locks the toggle on and says why.
Or install it from a range terminal
```
sudo apt install -y liboqs-tools
```
The simulated package manager seeds the same binaries, config and receipt the shelf toggle does.
Everything here is simulated
No software is downloaded and nothing executes — the range answers from authored fixtures.

Open Open Quantum Safe (liboqs + oqs-provider)'s own page →