VoidWalker folds two former standalone projects into itself and drives them through one themed CLI. The engines are vendored inside the package — nothing to clone separately — and every install path is architecture-aware (amd64 · arm64 · armv7).
+ +The arsenal builder: 400+ arch-aware offensive tools, a C# source-build pipeline, offline CVE / NSE / Exploit-DB search, and Obsidian engagement vaults.
voidwalker # interactive menuThe battle-tested “make a fresh Kali usable” engine — missing tooling, smb.conf, nmap scripts, Impacket, mirrors, root login and more.
voidwalker kali --newvmAn encrypted pe store for flags / creds / hosts / notes, plus a full Rosé-Pine zsh + tmux + BSPWM rice and in-terminal cheatsheets.
voidwalker env # deploy it[1] Install Full Arsenal (400+ tools)
+[2] Select Categories
+[3] View All Tools
+[4] System Packages (apt/brew)
+[5] Windows Binaries Only
+[6] Build C# Tools from Source
+[7] Setup Pentest Obsidian Vault
+[8] Fix / Harden Kali (pimpmykali)
+[9] Deploy Pentest Environment (pe)
+[10] Setup BloodHound-CE
+[11] View Sources & Guides
+[12] ExitArchitecture-aware: on ARM, tools with no native binary route to a go/cargo source build instead of grabbing an x86 build that can't run. voidwalker --dry-run prints the exact plan for your machine.
Menu [1] installs the lot; [2] lets you cherry-pick categories. On ARM, anything without a native binary routes to a go / cargo source build instead of a dead x86 download.
| Category | What it covers | Key tools |
|---|---|---|
| Windows Binaries | Compiled C# AD recon, cred extraction, lateral movement | Rubeus · Seatbelt · SharpHound · Certify |
| C# Build Targets | Source-to-binary compilation for OPSEC | ADCSPwn · SharpSCCM · SauronEye |
| Maldev & Evasion | Loaders, sleep obfuscation, shellcode runners | Freeze.rs · NimPlant · Ekko |
| C2 Frameworks | Command-and-control for post-exploitation | Havoc · Mythic · Sliver · Empire |
| PowerShell | Memory-resident scripts + AMSI bypasses | PowerSploit · PowerView · Nishang |
| Cross-Platform | Tunnels, proxies, relays across OS boundaries | Chisel · Ligolo-ng · Kerbrute · Fscan |
Preview first: voidwalker --dry-run prints the exact per-architecture plan and downloads nothing; voidwalker selftest validates the catalog offline. Menu [7] scaffolds an Obsidian engagement vault under ~/voidwalker/Vault.
Install + start BloodHound-CE.
voidwalker bloodhoundWire proxychains4 to a SOCKS pivot.
voidwalker proxy 127.0.0.1:1080Record a shell / capture screenshots.
voidwalker rec shell HTB-CapShodan terminal query (SHODAN_API_KEY).
voidwalker shodan apacheInstall Parallels Tools in a Kali guest.
voidwalker ptShell sugar from the env: newbox Cap 10.10.10.245 registers a target and drops you into ~/htb/Cap; scan runs a recorded nmap; Ctrl-X f pastes a flag.
newbox Cap 10.10.10.245 # add target + ~/htb/Cap/{nmap,loot,…}
+scan # recorded nmap -sCV into ./nmap
+useip # export $IP / $RHOST from active target
+ts # pe status · tl=target ls · fl=flag lsOne-letter aliases & fzf widgets wired into the prompt:
+t · f · c · h · n | pe target / flag / cred / host / note |
| Ctrl+X f | fzf-pick a flag, paste its value at the cursor |
| Ctrl+X c | fzf-pick a cred, paste the secret |
| Ctrl+X t | fzf-switch the active target |
tip · useip | active IP → clipboard / into $IP |
One deploy lays down the window-manager rice and the shell together. voidwalker env runs the installer; the full run includes the BSPWM rice, the core run skips it. It's idempotent — safe to re-run.
voidwalker env # menu → [1] full install
+# …non-interactive equivalents:
+./install.sh # full: pe+zsh+tmux+theme+rice
+./install.sh --no-wm --no-theme # core only (no rice)
+./install.sh --dry-run # print actions, change nothing
+# more flags: --no-deps --no-fonts --no-plugins --uninstallWhat the full install lays down:
+~/.config, with a generated Rosé-Pine wallpaper.zsh-autosuggestions, zsh-syntax-highlighting, zsh-you-should-use, fzf-tab (+ git / sudo / fzf / docker / tmux built-ins).~/.tmux.conf.Not Starship. People ask — the prompt is a custom, dependency-free zsh prompt (ZSH_THEME="", defined in prompt.zsh), not Starship or Powerlevel10k. It only borrows the MesloLGS NF font. All the zsh plugins listed above are installed automatically.
Log out, pick the bspwm session at the greeter, log back in — or for startx users: echo 'exec bspwm' >> ~/.xinitrc && startx. The mod key is Super (the ⊞ key).
| Keys | Action | Keys | Action |
|---|---|---|---|
| Super+Return | terminal (alacritty) | Super+w | close window |
| Super+Space | app launcher (rofi) | Super+Shift+w | kill window |
| Super+Shift+Return | browser | Super+t / s / f | tiled / floating / fullscreen |
| Super+e | file manager | Super+h/j/k/l | focus window (vim dirs) |
| Super+v | clipboard history | Super+Shift+h/j/k/l | move window |
| Super+1–9 | switch desktop | Super+Shift+1–9 | send window to desktop |
| Print / Super+Print | screenshot full / region | Super+Shift+e | power menu |
| Super+Escape | reload sxhkd | Super+Shift+r | restart bspwm |
Full keymap lives in ~/.config/sxhkd/sxhkdrc — resize with Super+Alt+h/j/k/l, preselect splits with Super+Ctrl+h/j/k/l, and the media / volume / brightness keys are wired too.
The pimpmykali engine, folded in as voidwalker kali. It self-elevates with sudo and is Kali/Debian-only. Start with --newvm on a brand-new box, or open the submenu to cherry-pick.
voidwalker kali --newvm # recommended first run
+voidwalker kali --all # fix all (menu options 1-8)
+voidwalker kali --missing # the usual missing tooling
+voidwalker kali # curated submenuIndividual fixes you can pass straight through:
+Any bare pimpmykali switch is forwarded verbatim — e.g. voidwalker kali --nmap --smbconf. Passing no switch opens the full upstream menu.
Running the arsenal in a Parallels Kali VM on Apple Silicon? Parallels Tools buys you the Mac ↔ VM shared clipboard the BSPWM rice leans on, plus drag-and-drop, dynamic resolution and shared folders. Its stock installer routinely dies on Kali — so the bundled pt-install helper does it for you. It's opt-in: voidwalker env drops pt-install onto your PATH but never runs it unprompted.
# in the Parallels menu bar, with the VM focused:
+# Actions → Install Parallels Tools
+# this mounts the Tools CD inside the guestpt-install # self-elevates — do NOT prefix sudo
+# …or straight from the pentest-env checkout:
+./install.sh --parallels-toolssudo reboot # loads the prl_fs / prl_eth modules
+# clipboard + shared folders work after thisWhat pt-install fixes for you: it unmounts the auto-mounted Tools CD and remounts it with exec (Kali mounts it noexec, so the stock ./install can't execute), pulls the linux-headers matching your running kernel, and satisfies Parallels' hardcoded libfuse2 dependency with a libfuse2t64 shim on time64 Kali.
If it aborts on kernel headers: your running kernel is newer than the packaged headers. Run sudo apt update && sudo apt full-upgrade -y && sudo reboot, then re-run pt-install. Handy flags: pt-install --mount-only just remounts the CD so you can run ./install yourself; --no-deps skips the apt step.