Summary
First of all, thanks a lot for your work on Flipper Blackhat OS and the whole Flipper Blackhat ecosystem – it’s an awesome WiFi security testing platform.
I would like to request that wifite2 (the kimocoder fork) be included as a preinstalled tool (or as an officially supported package/option) in Flipper Blackhat OS:
https://github.com/kimocoder/wifite2
Motivation / use case
Flipper Blackhat OS is already focused on WiFi pentesting and network analysis, and it ships with a number of WiFi and exploitation tools. wifite2 fits perfectly into this toolbox because it:
- Wraps common WiFi tools (aircrack-ng suite, etc.) behind a single CLI
- Automates:
- Target scanning
- Handshake/PMKID/SAE capture
- WPS attacks
- Evil Twin / captive portal style attacks
- Various WPA/WPA3 workflows
- Supports more advanced setups such as:
- Dual interface mode (
--dual-interface)
- Evil Twin with dual adapters
- WPA/WPA3 attacks with continuous capture
For many users, this dramatically lowers the barrier to running complex WiFi audits on the Blackhat board.
Proposed integration
Baseline idea
- Ship
wifite2 (kimocoder fork) in the default Flipper Blackhat OS image, installed as a CLI tool available in $PATH (wifite or wifite2 command).
- Ensure required dependencies are present in the image, for example:
- Python 3 (version compatible with wifite2)
aircrack-ng suite and related wireless tools
iw / ip (for interface handling)
- Optional but nice-to-have:
tshark, reaver, bully, etc.
Optional enhancements
- Add a short section to
BLACKHAT_REFERENCE.md describing:
- That
wifite2 is included
- A couple of example commands (e.g.
sudo wifite --dual-interface, sudo wifite --eviltwin)
- (Nice to have) Provide a simple wrapper script or menu entry that launches
wifite2 with sensible defaults for the Flipper Blackhat hardware.
Potential considerations
- Image size:
wifite2 itself is fairly small; most of the size impact would come from dependencies which may already be present for other tools.
- Licensing:
wifite2 is GPL-2.0 licensed. As a userland tool packaged in the OS image, this should be fine as long as the usual GPL requirements are respected (source availability, etc.), but you’ll likely want to double-check that this aligns with how you handle other GPL tools.
- Integration method: Since Flipper Blackhat OS does not provide a traditional package manager like
apt, adding wifite2 is best done directly in the build system (e.g. as a Buildroot package or via a rootfs overlay) rather than expecting users to install it manually on-device.
Environment
- Flipper Blackhat OS: BlackhatOS v1.3 (latest release at the time of writing)
- Hardware:
- Flipper Blackhat board (A33)
- Flipper Zero
Alternatives / workarounds
Right now, there is no straightforward way for an average user to install wifite2 plus all required dependencies directly on the device, because:
- The stock image does not ship with a full package manager like
apt.
- Manually cloning
wifite2 and installing Python dependencies still requires that all external tools (aircrack-ng, hcxtools, reaver, etc.) are already present and correctly configured.
The only realistic workaround is to build a custom Blackhat OS image from source and include wifite2 (and its dependencies) yourself, for example:
- Adding
wifite2 as a Buildroot package
- Or using a rootfs overlay to bundle it and its dependencies into the image
This is feasible for advanced users but not practical or user-friendly for most people, which is exactly why having it integrated into the official image would be so valuable.
Closing
If you’re open to the idea but prefer a specific integration approach (e.g. Buildroot package, optional config flag, or a separate “WiFi extras” image), I’d be happy to adapt to that direction and test it.
Thanks for considering this request!
Summary
First of all, thanks a lot for your work on Flipper Blackhat OS and the whole Flipper Blackhat ecosystem – it’s an awesome WiFi security testing platform.
I would like to request that
wifite2(the kimocoder fork) be included as a preinstalled tool (or as an officially supported package/option) in Flipper Blackhat OS:Motivation / use case
Flipper Blackhat OS is already focused on WiFi pentesting and network analysis, and it ships with a number of WiFi and exploitation tools.
wifite2fits perfectly into this toolbox because it:--dual-interface)For many users, this dramatically lowers the barrier to running complex WiFi audits on the Blackhat board.
Proposed integration
Baseline idea
wifite2(kimocoder fork) in the default Flipper Blackhat OS image, installed as a CLI tool available in$PATH(wifiteorwifite2command).aircrack-ngsuite and related wireless toolsiw/ip(for interface handling)tshark,reaver,bully, etc.Optional enhancements
BLACKHAT_REFERENCE.mddescribing:wifite2is includedsudo wifite --dual-interface,sudo wifite --eviltwin)wifite2with sensible defaults for the Flipper Blackhat hardware.Potential considerations
wifite2itself is fairly small; most of the size impact would come from dependencies which may already be present for other tools.wifite2is GPL-2.0 licensed. As a userland tool packaged in the OS image, this should be fine as long as the usual GPL requirements are respected (source availability, etc.), but you’ll likely want to double-check that this aligns with how you handle other GPL tools.apt, addingwifite2is best done directly in the build system (e.g. as a Buildroot package or via a rootfs overlay) rather than expecting users to install it manually on-device.Environment
Alternatives / workarounds
Right now, there is no straightforward way for an average user to install
wifite2plus all required dependencies directly on the device, because:apt.wifite2and installing Python dependencies still requires that all external tools (aircrack-ng,hcxtools,reaver, etc.) are already present and correctly configured.The only realistic workaround is to build a custom Blackhat OS image from source and include
wifite2(and its dependencies) yourself, for example:wifite2as a Buildroot packageThis is feasible for advanced users but not practical or user-friendly for most people, which is exactly why having it integrated into the official image would be so valuable.
Closing
If you’re open to the idea but prefer a specific integration approach (e.g. Buildroot package, optional config flag, or a separate “WiFi extras” image), I’d be happy to adapt to that direction and test it.
Thanks for considering this request!