flipper-zero Jul 3, 2026 ◑ 18 views ◯ 2 min read

Marauder Firmware Setup & Full Menu Walkthrough

flipper zerowifi devboardmarauderesp32

What the WiFi Dev Board Adds

Flipper's own radios don't include WiFi — the WiFi Dev Board is an ESP32-S2 module that clips onto Flipper's back GPIO header, running its own firmware (Marauder is the most popular option) that Flipper's screen/buttons act as a UI for, over UART.

Flashing Marauder

Connect the WiFi Dev Board to your computer via its own USB-C port (not through Flipper) for flashing.
Use the Marauder web flasher (works in Chrome/Edge via WebSerial) or esptool.py from the command line — the web flasher is the lower-friction option for most people.
Select the correct board variant matching your Dev Board hardware revision — check the Marauder GitHub releases page for current board support before flashing, since ESP32-S2 vs S3 dev board variants exist and need matching firmware builds.

Connecting to Flipper

Once flashed, clip the Dev Board onto Flipper's back header, then in Flipper: Apps > GPIO > ESP32 WiFi Marauder (or install the Marauder companion app from the Flipper app catalog if it's not preloaded on your firmware). This gives you a menu-driven interface on Flipper's screen controlling the Dev Board's WiFi radio.

Menu Walkthrough

Scan APs: lists visible WiFi access points in range with SSID, channel, signal strength — the starting point for most other functions, since several later options target a specific AP you select from this scan.
Scan Stations: lists client devices connected to a selected AP.
Sniff (various modes — beacon, probe, deauth, pwn): passive packet capture of different 802.11 frame types, useful for network analysis and troubleshooting on networks you own/administer.
Deauth: sends deauthentication frames — this has legitimate uses for testing your own network's client reconnection behavior and WPA3/PMF (protected management frames) effectiveness, and is illegal to use against networks you don't own/have permission to test in essentially every jurisdiction.
Evil Portal: stands up a fake captive portal AP — covered in its own dedicated guide, legitimate use is security awareness training on networks/environments you're authorized to test.
PCAP Save: writes captured packets to the Dev Board's SD card (if present) or Flipper's storage in standard PCAP format for later analysis in Wireshark — see the dedicated PCAP workflow guide.

Legal Reality Check

Nearly everything on this list beyond passive scanning of your own network is regulated — deauth attacks, unauthorized packet capture of others' traffic, and rogue AP/evil portal deployment against networks you don't own or lack explicit written authorization to test are illegal in most jurisdictions (in the US, this falls under the Computer Fraud and Abuse Act and FCC regulations on RF interference). Use this hardware on your own network and equipment, or in an authorized penetration testing engagement with signed scope documentation — not "just to see what happens" on a neighbor's or business's network.