Remote Hashcat Cracking Setup

UwU Toolkit can offload hash cracking to a remote machine with a GPU. This guide walks you through setting up SSH access from your Exegol container to your host machine.

Prerequisites

• A host machine with:
  • hashcat installed
  • NVIDIA GPU with CUDA or OpenCL support
  • SSH server running (sudo systemctl enable --now sshd)
• Exegol container with UwU Toolkit

Quick Setup

Step 1: Run hashcrack_setup in Exegol

uwu> hashcrack_setup

The setup wizard will display your SSH public key with a ready-to-paste command:

  Hashcat Remote Cracking Setup
  ==================================================
  Configure SSH connection to a machine with hashcat/GPU

  ➜ Run this on your HOST to authorize this key:
  ────────────────────────────────────────────────────────────
  echo 'ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIxxxx...' >> ~/.ssh/authorized_keys
  ────────────────────────────────────────────────────────────

Step 2: Add the key on your host

Copy the echo '...' >> ~/.ssh/authorized_keys command and run it on your host machine.

Step 3: Complete the setup in Exegol

Continue with the prompts:

Step 4: Verify connection

uwu> hashcrack_setup --test

You should see:

  [+] Connection successful!
  [+] Hashcat: /usr/bin/hashcat
  [+] Version: v7.1.2

Commands Reference

Troubleshooting

“Permission denied (publickey)”

Your SSH key isn’t authorized on the host. Run the echo command shown during setup on your host machine.

“Host key verification failed”

First-time connection. The setup now auto-accepts new host keys, but if issues persist:

ssh-keyscan -H 172.17.0.1 >> ~/.ssh/known_hosts

“Connection timed out”

• Verify SSH is running on host: sudo systemctl status sshd
• Check the IP is correct (use 172.17.0.1 for Docker gateway)
• Ensure no firewall blocking port 22

hashcat not found

Install hashcat on your host:

sudo apt install hashcat

For CUDA support:

sudo apt install nvidia-cuda-toolkit

Network Configuration

From Exegol Container

The Docker gateway IP 172.17.0.1 typically reaches your host from inside containers. This IP is stable and doesn’t change.

Alternative: Use hostname

If mDNS/Avahi is configured, you can use hostname.local:

SSH Host: myhostname.local

Recommended Wordlists & Rules

Wordlists

Rules

Install OneRuleToRuleThemAll:

sudo curl -L -o /usr/share/hashcat/rules/OneRuleToRuleThemAll.rule \
  https://raw.githubusercontent.com/stealthsploit/Optimised-hashcat-Rule/master/OneRuleToRuleThemAll.rule

How It Works

When modules like targeted_kerberoast or ntlm_coerce capture hashes with AUTO_CRACK=yes:

1. Hashes are saved locally in Exegol
2. UwU Toolkit SSHs to your configured host
3. hashcat runs on the host GPU
4. Results are returned to Exegol

This gives you full GPU acceleration without needing GPU passthrough to containers.

Supported Hash Modes

The hashcrack module auto-detects hash types, but you can also set them manually:

Module Integration

uwu > use auxiliary/cracking/hashcrack
uwu hashcrack > set HASHFILE /workspace/hashes.txt
uwu hashcrack > set SSH_HOST 172.17.0.1
uwu hashcrack > run

[*] Loaded hashes from: /workspace/hashes.txt
[*] Transferring hashes to 172.17.0.1...
[*] Running hashcat on 172.17.0.1...
[+] Cracked: user:Password123