AllHackingTools: a Termux installer that bundles penetration testing tools behind one menu

What AllHackingTools actually solves for Termux users

Termux gives Android a Linux userland, but it does not ship a security toolset. Getting one means cloning dozens of repositories, installing their Python or Go dependencies, and remembering which directory each tool lives in. AllHackingTools is a Shell project that automates that download and install process and then presents the result as a menu. The README describes it as "a system designed to automate the download process and install various tools for penetration testing." The audience is narrow: people running Termux on Android, typically on a phone, who want a catalogue of tools without assembling it themselves. The README states the download takes 5 to 20 minutes and that the only tested system is Termux. There is no desktop installer, no container image and no package on a distribution repository. If you work on a laptop, this project is not aimed at you.

How the installer and the msdconsole menu fit together

The repository is a Shell project with a Python menu. Install.sh is the entry point that the README tells you to run with bash; MainMenu.py is the menu that the msdconsole command starts. The top-level layout shows the supporting pieces: Tool/ holds the tool definitions, .settings/ and .desing/ hold configuration and terminal styling, .logs/ and .temp/ hold runtime output, Themes/ and .fonts/ feed the terminal customisation, and Uninstall/ holds the removal path. The README also lists Castom/, Files/ and Termux-os/ as top-level directories, though it does not explain what each one contains. The menu groups tools into categories such as Information Gathering, Exploitation Tools, Sniffing and Spoofing, Web Attack Tools, SQL Injection Tools, SocialMedia Bruteforce, DDOS Attack Tools, Phishing Attack Tools, Hash Cracking Tools, XSS Attack Tools and Wireless attack Tools. The README says the user can run tools directly from AllHackingTools even when they are already installed, and that exiting a tool restarts AllHackingTools automatically. That restart behaviour is a design choice worth noting: it keeps the menu in the foreground, but it also means the menu process is the parent of whatever you launch, so a tool that expects a clean shell may behave differently than it would if you started it yourself.

Installing AllHackingTools on Termux and starting it

The README gives the install sequence explicitly. You update the package index, grant storage permission, install git, clone the repository, enter the directory and run the installer. Each command below is copied from the README.

apt update
apt upgrade
termux-setup-storage
apt install git
git clone https://github.com/mishakorzik/AllHackingTools
cd AllHackingTools
bash Install.sh

The README says the download takes 5 to 20 minutes and that when a large rainbow button appears reading "Done, everything is ready!" the installation has finished. If the install errors out, the README gives one recovery step: cd AllHackingTools && bash fix.sh. After installation, the command that starts the menu is msdconsole, which the README documents as follows.

msdconsole

The README also lists msdc as an alias and msdServer as a command to check the AllHackingTools server. It documents an optional ngrok step for exposing a local port, with ngrok authtoken and ngrok http 80. Nothing in the README explains which tool requires that tunnel, so treat it as optional until you find the tool that needs it.

Where the AllHackingTools approach breaks down

The installer is a convenience layer over other people's repositories, and the README does not describe how those repositories are pinned. There is no version list, no lockfile and no checksum in the README or the repository layout. That means two installs on two devices, or the same device a month apart, can pull different upstream code. For a phone-based toolkit used for practice, that is tolerable. For anything you need to reproduce, it is not. The second limitation is the removal path. The repository contains an Uninstall/ directory, but the README does not document rollback, so it does not say what Uninstall/ removes or whether it restores the Termux environment. The third is scope: the README states the project is tested only on Termux, so Linux desktop users who want the same menu have no documented path. Finally, the catalogue includes categories such as DDOS Attack Tools and Phishing Attack Tools. Running those against systems you do not own is illegal in most jurisdictions, and the README's disclaimer ("I am not responsible for your actions") does not change that. The presence of a category is not a licence to use it.

AllHackingTools compared with Kali NetHunter and manual Termux setup

The closest alternative in the Android security space is Kali NetHunter, which installs a Kali Linux chroot or a custom kernel on a supported device. The difference in approach is architectural: NetHunter gives you a full Kali userland with its own package manager and a curated tool set, while AllHackingTools keeps you inside Termux and clones individual tool repositories into it. NetHunter requires a device from a supported list and, for some features, a custom kernel and root; AllHackingTools requires only Termux and git, which is why it works on phones that NetHunter does not support. The trade-off is that NetHunter's tools come from Kali packages with a distribution's release process behind them, while AllHackingTools pulls from upstream repositories that the README does not enumerate by version. The other alternative is doing it by hand: clone each tool, install its dependencies, keep your own notes. That is slower and more error-prone, but you end up with a setup you fully understand and can reproduce.

Maintenance, licence and the cost of keeping it running

The repository is not archived, and the last push was on 2026-09-17, so the project is being touched. That says nothing about whether the bundled tools are current, because they live in other repositories. The README describes an update path ("the ability to quickly update AllHackingTools") but does not give the command, so the upgrade cost is not documented. The project itself is GPL-3.0. That licence covers the Shell and Python code in this repository; it does not automatically cover the tools the installer downloads, each of which carries its own licence. Before you rely on any bundled tool in a commercial or client context, check that tool's own licence, not this repository's. The README's own disclaimer is a liability statement, not a legal shield, and the project does not offer legal advice or a warranty.

Editorial conclusion

AllHackingTools suits Android users who want a Termux environment populated with a broad catalogue of security tools without cloning each project by hand, and who accept that the README does not document rollback or per-tool licences. It is the wrong choice for anyone who needs reproducibility, CI integration or per-tool provenance, because the installer downloads tools from many upstream repositories and the README lists no pinned versions. Before adopting it, read .github/TOOLS.md to confirm the catalogue, check the licence of each tool you plan to use, and verify that bash Install.sh completes and that msdconsole starts the menu on your device; if the installer fails, the README points to cd AllHackingTools && bash fix.sh.

Frequently asked questions

Official sources

1. Issues
2. License: GPL-3.0
3. mishakorzik/AllHackingTools on GitHub
4. README