Repository navigation
Flipper Zero Ultimate Field Guide
PNWC Cyberdeck field operations: Flipper, WiFi Pineapple, Bruce & Marauder workflow explains companion firmware, scoped surveys, evidence transfer and qualification, not hardware-hacking bench techniques.
FlipperHTTP supplies target-specific network-bridge firmware and a library used by separate Flipper applications. It is not Flipper OS and does not add Wi-Fi hardware to the Flipper itself. Use the exact board-directory installation/wiring instructions, match the companion app, and keep network credentials out of shared backups. It is a different role from Marauder or GhostESP survey/capture firmware.
Update the Flipper and its radio accessory as separate devices. The Flipper itself has no Wi-Fi scanning radio; a firmware change on the Flipper does not add one. Preserve logs and match companion applications to the accessory firmware.
| Resource | Role & Compatibility Boundary |
|---|---|
| Official Flipper Firmware | Baseline vendor firmware and documented update/recovery workflow. |
| Momentum Updater | Community Flipper firmware; does not flash the external ESP radio. |
| Unleashed Installer | Community Flipper firmware; separate from its ESP web-flasher catalog. |
| GhostESP Revival | Alternative ESP accessory/standalone firmware; verify board and companion-interface support. |
| Marauder Survey Guide | Existing ESP accessory targets, GPS and evidence workflow. |
| Scout Lite / SigRoam | Vendor-specific scanner/controller pairing; never write a FAP as an ESP image. |
| CC1101, nRF24, AWOK, BW16 & Poltergeist Field Labs | Board selection, GPIO/power safety, app/firmware distinctions and eight authorized labs. |
Field guide for the Flipper Zero multi-tool device covering all built-in radios and interfaces for authorized physical penetration testing, IT administration, and security assessment workflows.
Organized by hardware module: Sub-GHz radio, NFC (13.56 MHz), 125kHz RFID, Infrared, iButton, BadUSB, GPIO, Bluetooth, and WiFi via the ESP32 Dev Board. Covers firmware options (Official, Unleashed, Momentum, RogueMaster), initial setup, the full app catalog, pentesting and IT-admin workflows, and field kit integration with tools like HackRF, Bus Pirate, and ProxMark3.
Enable IT professionals and penetration testers to use the Flipper Zero effectively across the full range of physical security assessment tasks - from access control badge cloning to wireless handshake capture to BadUSB payload delivery.
- Physical access control assessments (125kHz RFID/NFC badge reading and cloning)
- Wireless assessments (Sub-GHz fixed-code replay, WiFi handshake capture via Marauder)
- USB HID attacks (BadUSB payloads) during authorized red-team engagements
- IT admin console access to routers and switches via GPIO UART
- Client security awareness demonstrations (BLE spam, IR disruption, unlocked workstation demos)
โ ๏ธ Legal Disclaimer: All techniques in this guide are for use only on systems and devices you own or have explicit written authorization to test. Unauthorized interception, cloning, or access of wireless signals, access control systems, or computer systems violates the Computer Fraud and Abuse Act (CFAA), the Electronic Communications Privacy Act (ECPA), and applicable state laws. PNWC accepts no liability for misuse of the information contained herein.
- Hardware Overview
- Firmware
- Initial Setup
- Sub-GHz Radio
- NFC (13.56 MHz)
- 125kHz RFID
- Infrared
- iButton
- BadUSB
- U2F / FIDO2
- GPIO & Hardware Interfaces
- Bluetooth
- WiFi - ESP32 Dev Board
- Apps - Full Catalog
- Pentesting Workflows
- IT Admin Workflows
- Field Kit Integration
- SD Card Organization
- Resources & References
Wi-Fi wardriving requires an external scanner: A Flipper Zero does not include a native Wi-Fi survey radio. For the PINGEQUA Scout Lite ESP32-C5 board, compatible SigRoam Flipper app/board firmware and microSD/GNSS workflow, see SigRoam Wardriving. For alternate board firmware see ESP32 Marauder and the Wardriving overview.
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
โ [โBack] [Flipper Logo] โ
โ โ
โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ
โ โ 1.4" LCD Display โ โ
โ โ 128 x 64 pixels โ โ
โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ โ
โ โ
โ [โฒ] โ
โ [โ] [OK] [โบ] [โ] LED โ
โ [โผ] โ
โ โ
โ [Back] [Power/Lock] โ
โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ
| Component | Spec |
|---|---|
| MCU | STM32WB55 (ARM Cortex-M4 @ 64MHz + M0+ BLE co-processor) |
| Display | 1.4" monochrome LCD, 128ร64 |
| Sub-GHz Radio | CC1101 (300โ928 MHz) |
| NFC | ST25R3916 (13.56 MHz, ISO 14443A/B, ISO 15693) |
| 125kHz RFID | EM4100, HID Prox, Indala, Hitag, etc. |
| Infrared | TX/RX up to 56kHz carrier |
| iButton | 1-Wire protocol (Dallas/Maxim) |
| Bluetooth | BLE 5.0 via STM32WB55 |
| USB | USB 2.0 Full-Speed (HID, CDC, DFU) |
| GPIO | 18 pins (3.3V logic, 5V tolerant inputs) |
| Storage | MicroSD (up to 256GB) |
| Battery | 2000mAh Li-Ion |
| Charging | USB-C, ~2hr full charge |
3V3 1 โ โ 2 GND
PA7 3 โ โ 4 PB2
PA6 5 โ โ 6 PC3
PA4 7 โ โ 8 PC1
PB3 9 โ โ 10 PC0
PB2 11 โ โ 12 GND
PC6 13 โ โ 14 PC5 (TX)
PC4 15 โ โ 16 PC3 (RX)
GND 17 โ โ 18 5V (USB)
Key pins for common use:
- Pin 13/14 - UART TX/RX (serial console work)
- Pin 15/16 - SPI MOSI/MISO
- Pin 18 - 5V (from USB only, not battery)
- Pin 1 - 3.3V regulated output (~20mA max)
| Firmware | Stability | App Count | Sub-GHz Unlock | Custom UI | Best For |
|---|---|---|---|---|---|
| Official (OFW) | โ โ โ โ โ | Low | โ | โ | Warranty / compliance |
| Unleashed | โ โ โ โ โ | High | โ | Partial | Daily IT + pentesting |
| Momentum | โ โ โ โ โ | Highest | โ | โ | Feature-rich builds |
| RogueMaster | โ โ โ โโ | Highest | โ | โ | Max features, less stable |
- Source: flipper.net / qFlipper auto-update
- Stock feature set, regionally restricted Sub-GHz
- Required for warranty claims
- App Catalog access via lab.flipper.net
- Source: github.com/DarkFlippers/unleashed-firmware/releases
- Removes Sub-GHz regional frequency restrictions
- Adds extra protocols: CAME, Nice, Ansonic, etc.
- Extra apps bundle in
*e.tgzrelease variant - Compatible with official Flipper App Catalog
- Source: github.com/Next-Flip/Momentum-Firmware/releases
- Fork of Xtreme firmware, actively maintained
- Largest bundled app collection
- Custom themes, UI tweaks, extended settings
- Extra apps in
*e.tgzor resources package - Supports custom asset packs
- Source: github.com/RogueMaster/flipperzero-firmware-wPlugins
- Maximum features and app count
- Less stable, rolling releases
- Good for experimentation, not field reliance
- Connect Flipper via USB-C
- Open qFlipper โ click "Install from file"
- Select the downloaded
.tgzupdate package - Wait for flash + reboot (~2 minutes)
Via SD Card (OTA, no PC needed):
- Copy update folder to SD card root
- On Flipper: Settings โ Power โ Update Firmware
- Select the update package
Via CLI/ufbt:
pip3 install ufbt
ufbt update --channel=dev # or release/rcDownload the resources package from your firmware's releases page:
momentum-f7-resources-<version>.tgz
Extract and copy the apps/ folder to your SD card via qFlipper File Manager.
- Charge to 100% before first use
- Insert MicroSD card (FAT32 formatted)
- Flash preferred firmware (Momentum recommended)
- Set region: Settings โ System โ Region
- Set time/date: Settings โ System โ Date & Time
- Enable BLE if needed: Settings โ Bluetooth
- Pair with mobile app (Flipper Mobile App - iOS/Android)
Format as FAT32 (exFAT works but FAT32 is more reliable). The firmware will create the directory structure on first boot:
SD:/
โโโ apps/ # .fap app files by category
โโโ badusb/ # DuckyScript payloads
โโโ infrared/ # IR remote files (.ir)
โโโ lfrfid/ # 125kHz RFID saves
โโโ nfc/ # NFC card saves (.nfc)
โโโ subghz/ # Sub-GHz captures (.sub)
โ โโโ assets/ # Protocol databases
โโโ ibutton/ # iButton key saves
โโโ dolphin/ # XP/level data
โโโ logs/ # System logs
โโโ update/ # Firmware update packages
Essential for managing SD card contents. Access via:
- qFlipper โ SD Card tab โ file tree on left
- Drag and drop files to/from your PC
- Right-click for delete, rename, new folder
Available on iOS and Android. Enables:
- Remote control via BLE
- File transfer without USB
- App catalog browsing
- firmware update over BLE
The built-in CC1101 covers approximately 300โ348 MHz, 387โ464 MHz and 779โ928 MHz hardware bands (not an unrestricted continuous 300โ928 MHz span), with supported operation further limited by firmware, antenna and regional regulations. See official Sub-GHz specifications.
Common frequencies:
| Frequency | Common Use |
|---|---|
| 315 MHz | US/Canada garage doors, automotive remotes |
| 433.92 MHz | European garage doors, weather stations, sensors |
| 868 MHz | European IoT, Z-Wave (EU), LoRa |
| 915 MHz | US ISM band, Z-Wave (US), LoRa |
| 433/868/915 | Alarm sensors, temperature sensors |
Main Menu โ Sub-GHz โ Read
Passive capture mode. The Flipper listens on a configured frequency and decodes signals it recognizes. When a known signal is received, it appears on screen and can be saved.
Steps:
- Sub-GHz โ Read
- Point remote/transmitter at Flipper
- Press the button on the target device
- If decoded: press OK to save, give it a name
Supported protocols (built-in + Unleashed/Momentum extras):
- Princeton, CAME, Nice Flor, Chamberlain, Linear, Securplus
- Ansonic, Holtek, Doitrand, SMC5326, GangQi
- KeeLoq (fixed code capture - not rolling)
- Star Line automotive (fixed segments)
Sub-GHz โ Read RAW
Captures the raw signal waveform without attempting to decode it. Use when:
- Protocol is not recognized
- You want to replay without needing decode
- Analyzing unknown signals
Raw files are larger but more universal. They replay the exact timing of the original signal.
Settings in RAW mode:
- Frequency: manually set or use Frequency Analyzer first
- RSSI: signal strength indicator - get close to transmitter
Sub-GHz โ Saved โ [select file] โ Send
Replays a saved signal. For fixed-code protocols this is a direct replay attack. Holding the send button repeats transmission.
Pentest note: Fixed-code systems (many older garage doors, gates, parking barriers) are vulnerable to replay. Rolling code systems (KeeLoq with sync, HCS series) are not replayed this way.
Sub-GHz โ Frequency Analyzer
Real-time spectrum display. Shows what frequencies are actively transmitting in your environment. Use before capturing to identify:
- What frequency a device operates on
- Whether a signal is present at all
- Interference sources on client sites
Apps โ Sub-GHz โ Sub-GHz Bruteforcer
Iterates through all possible fixed codes for a given protocol and bit length. Effective against:
- Gate controllers using fixed codes
- Parking barriers
- Simple intercoms
- Older garage door systems
Usage:
- Select protocol (Princeton is most common)
- Select bit length (typically 24 or 25 bit)
- Start - Flipper transmits codes sequentially
Time estimates:
- 24-bit Princeton: ~45 minutes for full sweep
- 12-bit: seconds
Pentest note: Demonstrate to clients that fixed-code systems can be opened by any attacker with $30 of hardware in under an hour.
Unleashed and Momentum support frequencies beyond the defaults. Edit:
SD:/subghz/assets/setting_user
Example entries:
Frequency: 303920000
Frequency: 304250000
Frequency: 390000000
| Protocol | Type | Notes |
|---|---|---|
| Princeton | Fixed | Most common 24-bit fixed code |
| CAME | Fixed | Common in EU gate systems |
| Nice Flor S | Rolling | Cannot replay, capture only |
| KeeLoq | Rolling | Automotive, some gates |
| Chamberlain | Rolling | Security+, not replayable |
| Linear | Fixed | Older US systems |
| Holtek HT12X | Fixed | Common RF modules |
| SMC5326 | Fixed | Chinese gate controllers |
| Ansonic | Fixed | Various remotes |
| StarLine | Fixed segments | Russian automotive |
The Flipper's NFC reader (ST25R3916) supports ISO 14443A/B and ISO 15693, covering the vast majority of contactless smart cards used in access control, payment, and transit systems.
Supported card types:
| Card Type | Common Use | Read | Clone | Emulate |
|---|---|---|---|---|
| Mifare Classic 1K/4K | Access control (very common) | โ | โ * | โ |
| Mifare Ultralight | Transit, events | โ | โ | โ |
| Mifare DESFire | High-security access | UID only | โ | UID only |
| NTAG 203/213/215/216 | NFC tags, Amiibo | โ | โ | โ |
| EMV (bank cards) | Payment | UID + metadata | โ | โ |
| ISO 15693 (iClass) | Corporate access | โ ** | โ ** | โ ** |
*Requires key recovery (MFKey/Mifare Nested app) **Requires Picopass app
Main Menu โ NFC โ Read
Hold card to Flipper's back (NFC antenna area). The Flipper will identify card type and read available data. Save with a descriptive name.
For Mifare Classic, initial read captures the UID and sector structure but locked sectors require key recovery first.
NFC โ Saved โ [card] โ Emulate
Flipper presents itself as the saved card to readers. Works well for:
- Mifare Ultralight (full emulation)
- NTAG series (full emulation)
- Mifare Classic (partial - some readers detect timing differences)
Mifare Classic uses 48-bit sector keys (Key A and Key B). Default keys (0xFFFFFFFF, 0xA0A1A2A3A4A5, etc.) are tried automatically. For non-default keys:
Method 1: MFKey App (requires a real reader)
- Install MFKey from Flipper Lab
- NFC โ Detect Reader - hold Flipper near the target reader (badge reader on a door)
- The reader will challenge the Flipper, which captures the crypto nonces
- Apps โ NFC โ MFKey โ Run
- MFKey performs offline CRYPTO1 cryptanalysis to recover the sector keys
- Return to NFC โ Saved โ [card] โ Read with recovered keys
Method 2: Mifare Nested (app) Performs nested authentication attack to recover keys from a card that has at least one known sector key.
Method 3: MIFARE Classic Editor Manually enter/edit sector keys and data blocks after recovery.
NFC โ Saved โ [card] โ Write
Writes saved card data to a blank writable card. Requires:
- Mifare Classic: "Magic" Gen1 or Gen2 card (available cheaply online)
- NTAG: Any blank NTAG of correct type
- Ultralight: Blank Ultralight card
Gen1 vs Gen2 magic cards:
- Gen1: UID rewritable via backdoor command, detected by some readers
- Gen2: UID rewritable via standard commands, harder to detect
- Use Gen2 for professional pentest deliverables
HID iClass is a 13.56 MHz standard common in corporate environments. Not supported by the built-in NFC app - requires the Picopass app.
Install: Flipper Lab โ search "Picopass"
Capabilities:
- Read iClass Legacy and iClass SE credentials
- Read Standard and High-security segments
- Save and emulate credentials
- iClass Elite key bruteforce (if Elite key is unknown)
Physical Access Assessment Workflow:
- Covertly read target badge (NFC โ Read, brief contact sufficient)
- Identify card type
- If Mifare Classic: hold near reader to capture nonces (MFKey)
- Recover keys, re-read full card data
- Write to Gen2 magic card as physical evidence
- Test cloned card at target reader
- Document: card type, security weakness, affected doors
Deliverable talking points for clients:
- Mifare Classic 1K is cryptographically broken (CRYPTO1 cipher, 2008)
- Full key recovery takes ~30 seconds with commodity hardware
- Upgrade path: Mifare DESFire EV2/EV3 or SEOS
125kHz RFID (Low Frequency) is the oldest and least secure access control technology still widely deployed. The Flipper reads and emulates all common LF card formats.
Supported protocols:
| Protocol | Notes |
|---|---|
| EM4100 / EM4102 | Most common worldwide, read-only |
| HID Prox | Very common in US corporate |
| Indala | Motorola/HID, older deployments |
| AWID | Older US systems |
| Paradox | Security panels |
| Keri | Access control |
| Hitag 1/2/S | More secure, key-protected |
| FDX-B | Animal microchips |
| ioProx | Kantech systems |
Main Menu โ 125kHz RFID โ Read
Hold card against Flipper's back. Most LF cards read instantly. Save with descriptive name.
These cards transmit their ID with zero authentication - any reader in range can capture the credential. This is the lowest tier of access control security.
125kHz RFID โ Saved โ [card] โ Emulate
Flipper transmits the stored credential, presenting as the original card. Works against virtually all LF readers since LF systems have no mutual authentication.
125kHz RFID โ Saved โ [card] โ Write
Writes to T5577 writable cards (extremely cheap, widely available). These blank cards can be programmed to any EM4100/HID Prox/Indala credential.
125kHz RFID โ Add Manually
Useful when you know the card number (printed on the card, on a document, etc.) but don't have physical access to the card itself.
Apps โ RFID โ RFID Fuzzer
Iterates through credential ranges for a given protocol. Useful for:
- Testing whether a reader accepts sequential or predictable card numbers
- Discovering what credential ranges are active in a system
125kHz is essentially security theater:
- Cards are read-only and broadcast credentials with no authentication
- Can be read covertly from several centimeters with off-the-shelf hardware
- Cloning takes under 5 seconds with the Flipper
- Virtually all SMB facilities running HID Prox or EM4100 are vulnerable
Common client scenario: Visitor badges at front desk use the same format as employee badges - capture visitor badge UID, clone it, present at secured doors.
The Flipper includes an IR transmitter (950nm LED) and receiver, supporting carrier frequencies up to 56kHz. Covers virtually all consumer IR remote protocols.
Supported protocols: NEC, Samsung, RC5, RC6, SIRC, KASEIKYO, RCA, and raw capture for anything else.
Main Menu โ Infrared โ Learn New Remote
Captures IR signals from existing remotes. For each button:
- Select "Add Button"
- Name the button
- Point original remote at Flipper, press button
- Repeat for each button needed
Saves as .ir file on SD card.
Infrared โ Universal Remotes
Built-in database of common remote codes for:
- TVs (Samsung, LG, Sony, etc.)
- Air conditioners
- Projectors
- Audio equipment
Pentest / physical assessment use: Can disable AV equipment, TVs, or projectors in lobbies/conference rooms as part of a physical intrusion demo.
The UberGuidoZ repo (github.com/UberGuidoZ/Flipper/tree/main/Infrared) contains hundreds of device-specific IR files. Download relevant ones and place in SD:/infrared/.
Apps โ Infrared โ Brute Force IR
Iterates through all known codes for a given device type/brand. Useful for unlocking hotel TVs, testing IR receiver security.
iButton (1-Wire / Dallas keys) are contact-based keys used in some intercom systems, apartment buildings (common in Eastern Europe and Russia), and some industrial access control systems. Less common in the US but still encountered.
Supported types:
- DS1990A (RW1990) - most common
- DS1992, DS1996 - memory types
- Cyfral, Metakom - Russian apartment systems
Main Menu โ iButton โ Read
Contact the iButton key to the Flipper's iButton connector (bottom of device, next to USB). Reads and saves the key ID.
iButton โ Saved โ [key] โ Emulate
Flipper presents the key credential via the iButton connector. Hold Flipper to the reader contact point.
iButton โ Saved โ [key] โ Write
Writes to blank RW1990 writable keys. Cheap and widely available.
When connected via USB, the Flipper can present itself as a USB HID keyboard and type arbitrary keystrokes at machine speed. Uses DuckyScript 1.0 syntax (compatible with Hak5 Rubber Ducky payloads).
REM Comment line
DELAY [ms] Wait in milliseconds
STRING Type text
ENTER Press Enter
GUI Windows key
CTRL Control key
ALT Alt key
SHIFT Shift key
TAB Tab key
SPACE Space
BACKSPACE Backspace
DELETE Delete
UP/DOWN/LEFT/RIGHT Arrow keys
F1-F12 Function keys
CAPSLOCK Caps Lock toggle
HOME / END Navigation
PAGEUP/PAGEDOWN Page navigation
Key combos:
GUI r Windows + R (Run dialog)
CTRL-ALT t Open terminal (Linux)
CTRL c Copy
CTRL v Paste
CTRL-SHIFT ESC Task Manager
- Place
.txtpayload files inSD:/badusb/ - Main Menu โ BadUSB
- Select payload file
- Connect to target USB port
- Press OK to run
- Always start with
DELAY 1000to give the OS time to recognize the device - Add generous
DELAYvalues after commands that open windows (600-1200ms) - Use
DELAY 3000or more after commands that trigger UAC prompts - Test on your own machine before field deployment
- Keep payloads idempotent where possible (safe to run twice)
Match the payload's keyboard layout to the target system. Set in: Settings โ System โ USB Keyboard Layout
Important for special characters - @, \, / vary by locale. US layout is default.
See the PNWC BadUSB library (separate document) for a complete set of ready-to-deploy payloads covering:
- Windows full system recon
- Network enumeration
- Security posture audit
- WiFi credential dump
- Active Directory enumeration
- Reverse shells (PS + Bash)
- Privilege escalation checks
- Persistence demonstration
- Data exfil simulation
- Physical security awareness test
- Client intake form auto-fill
- Rapid IT remediation
The Flipper can act as a FIDO U2F hardware security key for two-factor authentication. Useful as a backup 2FA device or for demonstrating hardware token concepts to clients.
Setup:
- Settings โ U2F โ Enable
- Connect Flipper via USB
- Register as a security key on any FIDO U2F-compatible service (Google, GitHub, Cloudflare, etc.)
- During authentication: press the OK button when prompted
Limitations:
- Stores one U2F credential
- Not FIDO2/WebAuthn level - works for U2F only
- No PIN protection (anyone with physical Flipper can authenticate)
Practical use for IT/security:
- Demonstrate hardware token value to clients
- Test whether services properly enforce MFA
- Emergency backup factor for personal accounts
18 GPIO pins provide access to UART, SPI, I2C, 1-Wire, and general digital I/O. The Flipper can serve as a portable hardware interface tool, logic analyzer, and signal generator.
Apps โ GPIO โ UART Terminal
Presents a serial terminal over the Flipper's GPIO pins. Essential for accessing:
- Router/switch console ports (Cisco, UniFi, MikroTik, pfSense)
- Embedded Linux devices (Raspberry Pi, development boards)
- IoT device debug ports
GPIO โ RJ45 Console Cable (make your own):
Flipper Pin 14 (TX) โ RJ45 Pin 3 (RX on Cisco)
Flipper Pin 16 (RX) โ RJ45 Pin 6 (TX on Cisco)
Flipper Pin 17 (GND) โ RJ45 Pin 8 (GND)
Serial settings: 9600/115200 baud, 8N1 (varies by device)
Cisco default console: 9600 baud, 8N1, no flow control UniFi default console: 115200 baud, 8N1
Apps โ GPIO โ Logic Analyzer
Captures digital signal states on GPIO pins. 4-channel capture, useful for:
- Analyzing SPI/I2C/UART traffic on unknown devices
- Timing analysis of digital signals
- Identifying communication protocols on circuit boards
Scan and communicate with I2C devices on the bus:
- Scan for device addresses
- Read/write registers
- Useful for hardware hacking sessions alongside Bus Pirate 5
Similar to I2C but for SPI devices. Can read SPI flash chips (with appropriate wiring), though the Bus Pirate 5 is more capable for deep hardware work.
Apps โ GPIO โ Tone Generator
Generates square waves on GPIO pins. Useful for:
- Testing audio circuits
- Generating clock signals
- Basic hardware testing
Apps โ GPIO โ Wire Tester
Continuity tester using GPIO pins. Quick cable verification tool - handy for network cable checking on client sites.
The Flipper can be used as a GPIO expander for Raspberry Pi projects. With flipperzero-protobuf and the Flipper's USB serial interface, you can script Flipper actions from Python.
Several add-on boards connect to the GPIO header:
| Module | Purpose |
|---|---|
| WiFi Dev Board (ESP32-S2) | WiFi pentesting via Marauder |
| Video Game Module | Flipper gaming (not pentesting use) |
| nRF24 Module | 2.4 GHz proprietary packet-radio observation; not a Wi-Fi or BLE radio |
| GNSS/GPS Module | Location metadata only with supported UART/firmware, reliable fix and real log integration |
| Servo/Motor Driver | Robotics integration |
| External CC1101 | Alternative Sub-GHz front-end/antenna for supported bands |
| AWOK Dual C5 | Independent C5 radios and optional Flipper companion interface |
| BW16 / RTL8720DN | Realtek 2.4/5 GHz; 5Ghost/FlipperHTTP firmware families |
| Rabbit-Labs Poltergeist | ESP32-C5 2.4/5 GHz, IR, SD and OLED, firmware-dependent |
| PINGEQUA CC1101+nRF24 | Separate Sub-GHz and 2.4 GHz radios; special SPI routing |
Last documentation/source review: November 2026. This section describes source-backed procedures, not personally verified hardware tests.
Goal: select, configure, and validate external modules without mixing firmware images, UART pinouts, RF bands, or incompatible Flipper applications. The official GPIO documentation describes the 18-pin connector, supply rails and pin limits; the official Sub-GHz documentation distinguishes built-in and external CC1101 operation. Read both before powering a new board.
Important
Flipper firmware, Flipper applications (.fap), and external radio-board firmware are separate components. An nRF24 is not a Wi-Fi or Bluetooth sniffer; a CC1101 is not an nRF24; a BW16 / RTL8720DN is not an ESP32. Match the exact PCB/revision, power/antenna, firmware target and app. Never assume that an ESP32/S2/S3/C5 image runs on an RTL8720DN or that a standalone image works with a Flipper UART companion.
| Hardware / ecosystem | Actual radio or peripheral | Flipper relationship | Primary source & documentation boundary |
|---|---|---|---|
| External CC1101 | Sub-GHz SPI transceiver; antenna/module commonly tuned for 315/433/868/915 MHz variants | Uses compatible Sub-GHz app; alternative antenna/front-end, not a new protocol family | Flipper Sub-GHz ยท external-CC1101 wiring example |
| nRF24L01+/Si24R1 | 2.4 GHz proprietary packet-radio class (Enhanced ShockBurst family) | External SPI module with app- and board-specific pin mapping | PINGEQUA nRF24 support ยท community wiring reference |
| PINGEQUA CC1101 + nRF24 2-in-1 | Two chips sharing a GPIO board, non-default nRF SPI | RF Lab FAP or compatible third-party apps | The nRF device uses Extra 7 on supported Momentum configurations; other FAPs may hard-code pins |
| AWOK Dual C5 Touch / Mini | Two independently programmable ESP32-C5 Wi-Fi radios; on-board GNSS connected to both chips | Independent touchscreen/display and serial/controller roles; verify Flipper link and exact MCU port | AWOK Dual C5 Touch ยท AWOK firmware/port guide |
| BW16 / RTL8720DN | Realtek AmebaD dual-band Wi-Fi (2.4/5 GHz) | Separate BW16 firmware and matching Flipper app, not Marauder ESP32 image | PINGEQUA 5Ghost flasher ยท Flipper app installer ยท FlipperHTTP BW16 |
| Rabbit-Labs Poltergeist | ESP32-C5 Wi-Fi, BLE-capable chip, OLED, microSD, IR receiver & high-output IR LEDs | Flipper GPIO accessory or USB-C standalone board; functions depend on installed firmware | Rabbit-Labs Poltergeist ยท vendor flasher |
| Flipper official Wi-Fi Dev Board | ESP32-S2, 2.4 GHz Wi-Fi only; no BLE | Separate ESP firmware + matching FAP | Marauder for Flipper lab |
| PINGEQUA Scout Lite + SigRoam | ESP32-C5 2.4/5 GHz and board-specific GNSS/microSD | Flipper FAP drives compatible external firmware; logging location differs with selected image | SigRoam / Scout Lite |
| UART, GPS, CAN, RS-232, Video Game & IR expansion | Depends on specific adapter or peripheral | Flipper GPIO/USB app or companion MCU; no general-purpose universal firmware | GPIO documentation ยท exact peripheral vendor/PCB instructions |
Frequency caution: the internal CC1101's Flipper-documented hardware bands are approximately 300โ348, 387โ464, and 779โ928 MHz, not every frequency continuously between 300 and 928 MHz. The external module, its filters, matching antenna, local region and firmware limits further constrain usable operation. Adding a higher-gain antenna does not authorize additional transmit power or frequencies.
- Engagement scope: written owner/asset authorization, intended receiver, permitted bands/channels, test time, receive/transmit boundaries, evidence retention, stop contact and excluded neighbors.
- Identify the stack: Flipper firmware version/API, FAP name/version, board vendor/model/PCB revision, radio chip(s), current module firmware, any bootloader requirements, SD/GNSS source and exact antenna type.
- Photograph and backup the device labels, wiring, prior firmware and client-owned SD files; redact serials and coordinates from public examples. Compare source releases and binary checksums, not just filenames.
- Power down before connecting or moving GPIO boards, attaching antennas or changing jumpers. Do not guess pin 1/orientation, apply 5 V to a 3.3 V peripheral, or feed RS-232 voltage into a UART pin. Verify regulator, battery/power budget and common ground using the board maker's schematic. An RJ45 console connector alone does not establish TTL serial voltage.
- Pick the correct application for the installed firmware/API. For vendor-combined modules, check pin/bus conflicts and whether a switch/multiplexer has moved SPI/UART to nonstandard pins.
- Start read-only: boot, UI and device enumeration, then one short observation of an owned test beacon/AP. Leave deauthentication, jamming, BLE spam, credential capture, rogue AP impersonation and unrelated device interactions out of initial acceptance tests.
- Preserve evidence: operator, exact time/time zone, FAP/board versions, allowed channels, test fixture ID, actual results, screenshots, error text and rollback. A scan alone cannot prove a client is compromised.
Purpose: evaluate reception of one owned, noncritical, battery-operated 433 MHz test transmitter, contrasting the Flipper's built-in radio with an external antenna/module. No gate, car, alarm, access lock or emergency device is required.
- Verify the external module's chip, operating band, antenna match and physical pinout. A 433 MHz module/antenna is not inherently suited for 868 or 915 MHz. Keep the antenna connected throughout the RF test.
- Power down, seat the verified CC1101 module and restart. Use
Sub-GHz โ Radio Settings โ Module โ Externalwhere the installed firmware exposes this setting; some builds useRead Externalinstead. - Begin with the internal radio: activate the owned test transmitter at a fixed short distance, record signal detection/decoded protocol and an RSSI indicator if present.
- Switch to external using the same receive mode, distance, orientation and transmitter. Repeat 3 times, logging internal/external selection and receiver settings.
- Return to the internal module and confirm reception still works. Remove the expansion with Flipper powered down.
- Report relative consistency and signal indication, not a calibrated range increase from a single reading. A different antenna/front end may improve or worsen a particular test.
Failure checks: missing External option (firmware/app), unseated SPI, wrong voltage, wrong chip/board pins, defective or mismatched antenna, unsupported band, or a strong nearby transmitter saturating a receiver. Never transmit without an explicitly permitted lab frequency, power and target.
Wiring example (only for the documented 3.3 V discrete module): the quen0n community reference maps Flipper 2/MOSI, 3/MISO, 4/CS, 5/SCK, 6/GDO0, 9/3V3 and 11/GND. This is not a universal carrier-board pinout; vendor-assembled boards and combo modules may route pins differently. Validate against the specific PCB before using wires.
Purpose: validate a dedicated nRF24/Si24R1 module using one or two test-dev-board nRF24 transmitters, while documenting that a channel observation is not proof of a vulnerable mouse or a Bluetooth/Wi-Fi association.
- Identify whether the Flipper accessory is bare nRF24, an Si24R1-compatible board, or a dual-module combo. Confirm SPI wiring,
CE,CSNand 3.3 V supply; a 5 V GPIO power pin must not feed an unregulated nRF24 radio. - Install a compatible nRF24 channel/spectrum app from Flipper's official Apps catalog or the module vendor. Third-party app availability and API compatibility vary across Official, Momentum, Unleashed and RogueMaster builds.
- Configure a separate owned nRF24 dev board to send a synthetic, non-sensitive telemetry sequence on one documented 2.4 GHz channel. Keep distance short, power low and transmission constrained to the test fixture.
- Observe the test channel using the Flipper accessory's supported receive/scan workflow. Turn off the transmitter as a negative control; repeat three times.
- Record app name/API, nRF type, pin mode, channel, scan duration and presence/absence. Do not claim that a generic 2.4 GHz energy indication decodes a packet or attributes it to one transmitter.
- Confirm that unrelated BT, BLE or 802.11 activity is not automatically identifiable by an nRF24 receiver. For actual Wi-Fi inventory use a supported ESP32-C5/BW16/Kismet radio; for BLE advertisements use a compatible BLE-capable device and scanner.
Security exercise: demonstrate why unencrypted proprietary peripherals need vendor firmware updates and appropriate physical trust boundaries; use only test transceivers and synthetic data. Do not run mousejacking, HID injection, protocol spoofing or packet interference against real peripherals.
Discrete classic nRF24L01+ reference: one commonly documented scheme uses Flipper pins 2=MOSI, 3=MISO, 4=CSN, 5=SCK, 6=CE, 8=GND, 9=3V3; IRQ may be disconnected. This is a reference only, not a guarantee for Si24R1, powered-PA, combo, or re-routed bus variants. See UberGuidoZ GPIO collection.
- Confirm it is the actual PINGEQUA 2-in-1 board, not a superficially similar dual-radio product.
- Choose the module's RF Lab companion app that explicitly matches the Flipper firmware API. The vendor has distinct FAP builds; an API mismatch is a packaging/compatibility problem, not necessarily a faulty module.
- Begin with receive-only channel observations using your owned nRF24 fixture from Lab B, then switch to receive-only Sub-GHz operation using the CC1101 fixture from Lab A. Record selected chip and expected antenna.
- If testing an unrelated third-party nRF app on supported Momentum builds, consult PINGEQUA's
Settings โ Protocols โ GPIO Pins โ NRF24 SPI โ Extra 7routing instructions; the default SPI route may not work. - Switch back to the internal Sub-GHz transceiver and verify neither radio remains active unexpectedly. No transmit/jammer modes are needed for this qualification.
Interpretation: two radios on one expansion are not simultaneous general-purpose receivers unless the specific hardware/app implements that; one FAP's success does not prove another FAP's SPI routing or feature compatibility.
Use the exact AWOK guide for independent MCU, connector, GNSS and Biscuit imaging details. AWOK describes the Dual C5 Touch as two ESP32-C5-WROOM chips, with an integrated L1/L5 GNSS module communicating to both; one C5 manages the touchscreen, the other is available via CLI/GPIO. This hardware ships without a universal bundled firmware, so feature lists from Marauder or Biscuit are not automatic properties of the board.
- Power down and photograph the PCB/revision. Identify the display-side and secondary-side USB connectors per the model instructions; distinguish Touch from Mini before choosing any image.
- On an isolated PC, query boot/version information for each C5 separately and record the physical port, bootloader mode, image, chip identity and rollback source. Never flash a Mini display binary onto Touch or overwrite both chips with the same generic C5 build.
- Install only an upstream-documented compatible firmware on the intended MCU. If using Biscuit on the documented side, follow AWOK + Biscuit and the Biscuit ecosystem workflow. If using Marauder, confirm a model-specific target through the official hardware list.
- Connect the approved Flipper UART companion only after validating pins/power and FAP compatibility. A working touchscreen on one C5 does not demonstrate UART control of the other C5.
- Run two separate short scans of one owned test AP, log which MCU/radio observed it, and compare BSSID, channel, time and band. One ESP32-C5 cannot listen simultaneously to every 2.4/5 GHz channel.
- If GPS-tagging, identify whether the source is on-board GNSS or a phone/app location; Biscuit Manager's standard export uses phone GPS even if AWOK has a wired GNSS receiver. AWOK Mini/Touch do not have an onboard microSD in the reviewed Biscuit configuration.
- Power off, restore intended firmware roles and compare both C5s to the preflight inventory. Do not merge results without duplicate handling and clock/GNSS provenance.
Use case: verify a dual-receiver field survey's auditability; it is not proof of greater RF sensitivity, coordinated capture, or one-click 5 GHz support for every firmware build.
BW16 is a Realtek RTL8720DN (AmebaD) board, not an ESP32. Common Flipper ecosystems include the PINGEQUA 5Ghost firmware/app pair, jblanked FlipperHTTP, and separately distributed third-party R4TKN variants. These are not interchangeable artifacts, and an ESP32Marauder binary is not a BW16 image.
- Read the actual product label/firmware. Select one verified software family. Back up known-working firmware, UART pinout and FAP revision before changing it.
- For a PINGEQUA 5Ghost board, use the board-specific official flasher only if an update/recovery is needed: many ship preloaded. It documents the Realtek bootloader and safe USB-C data flashing; use its BOOT/RESET path rather than generic ESP32/esptool offsets.
- Install the matching 5Ghost WiFi Lab FAP on the Flipper; that app installation does not flash BW16 firmware. For FlipperHTTP, follow its separate BW16 board directory and compatible FlipperHTTP app/transport. Don't mix these clients.
- Record UART pins from the actual carrier. Bare BW16 FlipperHTTP documentation shows
SERIAL1_TX/PB1 โ Flipper pin 14 RXandSERIAL1_RX/PB2 โ Flipper pin 13 TX, plus correct supply and ground; pre-assembled modules may route differently. Never infer wiring from a different module. - On a controlled pair of APs, scan one distinct 2.4 GHz SSID and one 5 GHz SSID. Record BSSID, channel, advertised security and scan time. Check against the AP controller.
- Repeat with the controlled 5 GHz AP disabled, then enabled. A scan is a visibility test, not a throughput or management-frame security audit.
- Document BW16 firmware version, FAP/API, both AP configurations, actual bands scanned, antenna, power source and any errors. Retain the initial image for rollback.
What not to assume: dual-band means all channels or 2.4/5 GHz simultaneous packet capture; the Flipper itself still cannot scan Wi-Fi without the external board. A third-party board combining BW16+nRF24 may wire its nRF24 to the BW16, not to Flipper SPI; follow the exact vendor firmware and app rather than attempting Lab B's GPIO pinout.
The Rabbit-Labs Poltergeist is an ESP32-C5-based Flipper-compatible or standalone USB-C accessory. The vendor lists a dual-band Wi-Fi radio, OLED, microSD, IR receiver, and four high-output 940 nm IR LEDs, with optional firmware-dependent IR routing through Flipper or ESP32 and GhostESP. Features may remain unimplemented or change by release: an OLED/IR board label is not evidence every command exists.
Hardware safety from Rabbit-Labs: some boards have six LED pads with only four LEDs populated intentionally. Do not install additional LEDs: Rabbit-Labs warns this can draw too much current and damage the Flipper. A pre-flashed/QC-tested board does not guarantee suitability of every optional firmware feature.
- Record PCB revision, original firmware and OLED state; save SD data/settings. Inspect the IR LEDs/receiver and do not add components to empty LED pads.
- Attach a verified suitable power source and USB-C data cable. If changing firmware, use Rabbit-Labs' referenced flasher with the Poltergeist-specific target/recovery path; a generic ESP32-C5 image may omit display, IR routing or SD pin mapping.
- Validate standalone USB operation first: boot/OLED, SD recognition and a short owned test-AP scan. Do not initiate captive portals, disruptive association tests or broad active scans.
- If connecting to Flipper, power down first; verify GPIO/serial wiring and choose the compatible companion FAP for the installed firmware. Distinguish Flipper UI issues from Poltergeist firmware issues by testing standalone.
- Repeat Lab E's short 2.4/5 GHz AP visibility test, recording firmware, radio channel support and 5 GHz coverage caveats.
- IR receive-first exercise: point a harmless owned TV/projector remote at the receiver in a controlled room. If the installed supported GhostESP build exposes IR receiving, record a decoded protocol and button code without assuming all formats are supported.
- Optional IR transmission: only with explicit owner permission and a noncritical powered test device, send one known-safe command. Avoid eyes, safety-critical equipment, locks, vehicles and continuous transmission. Account for the vendor's focused high-output IR emitter and elevated power consumption.
- Test a synthetic file on SD, verify actual exported path, hash it on the evidence workstation and restore the normal configuration. Do not assume Marauder
wardrive_files are produced by GhostESP/Poltergeist.
Troubleshooting: wrong OLED target/image, missing SD filesystem, Flipper UART/FAP mismatch, inadequate power, RF antenna/region/channel, unsupported IR feature, or trying an ESP32-S2-only build on the C5.
- GPS/GNSS: choose a documented board/receiver with a known UART baud/pin map, record fix quality/time and compare to a known outdoor position. Do not infer geotagging from the presence of an antenna, a scanner app, or a serial stream alone. The Scout Lite/SigRoam guide describes a particular GNSS and SD route; the Biscuit app generally uses phone location.
- UART / RS-232: Flipper's exposed UART is a 3.3 V logic interface. Cisco/RJ45 console pin layouts and voltage conventions vary; use an electrically appropriate converter and check the actual target manual before wiring. A physically compatible cable is not proof of logic-level compatibility.
- IR blaster/receiver: verify whether the Flipper or expansion MCU controls the LED, whether a firmware/app route exists and what current is permitted. Start receive-only with an owned remote.
- CAN / vehicle diagnostics: require a CAN transceiver and model-specific adapter rather than raw GPIO wires. Work on an isolated bench CAN simulator; never send unexplained frames to a moving vehicle or safety-critical system.
- Video Game Module, storage, NFC/RFID front ends and microcontroller accessories: treat each as a separate firmware/peripheral target. Never assume a Wi-Fi accessory adds NFC, LF RFID, GPS or USB HID hardware.
Example client-approved workflow (no disruptive features):
- Asset 1: use internal CC1101 and an optional verified external module to observe an owned, noncritical RF fixture. Record signal consistency, antenna/band, internal vs external selection.
- Asset 2: observe an owned 2.4 GHz nRF24 telemetry test board and its disabled negative control. Do not claim it is BLE or Wi-Fi.
- Asset 3: use either AWOK Dual C5, BW16, Poltergeist or a compatible external ESP32 board to inventory a client-owned 2.4/5 GHz test SSID, verifying BSSIDs and security settings in the controller.
- Asset 4: if the installed board supports GNSS, verify the actual location source and file destination. Keep third-party/public upload disabled unless separately authorized.
- Blue-team comparison: correlate time and in-scope SSID/BSSID against Kismet + Wazuh, nzyme + Wazuh, or controller logs. These add-ons do not automatically export directly into Wazuh.
- Closure: power down each module, remove temporary test SSIDs/transmitters, confirm the Flipper internal functions work, collect redacted results and validate the planned rollback.
| Finding/record | Minimum evidence |
|---|---|
| Authorization | Signed scope, approved assets/bands/channels, operator, start/stop time |
| Hardware | Flipper firmware/API, FAP, board vendor/revision, radio chip, power & antenna |
| Image & app | Exact firmware target, source URL, checksum, update/rollback path |
| Observation | Test fixture ID, band/channel, actual logs, duplicate/GPS handling |
| Corroboration | AP controller, independent RF receiver or WIDS event and time |
| Interpretation | Expected vs observed, false positives, uncertainty and remediation |
| Cleanup | Module removed, default radio restored, evidence redacted/retained |
| Symptom | Likely cause & first recovery |
|---|---|
| Flipper reboots or expansion is hot | Power/short/overcurrent, wrong pin orientation; disconnect and inspect |
| CC1101 absent or weak | Antenna/band mismatch, wrong SPI/GDO pins, internal/external app option, supply |
| nRF24 app sees no module | SPI/CE/CSN mismatch, 3.3 V instability, FAP/API, non-default combo pins |
| Dual C5 scans mismatch | Independent MCU images, radio scheduling, band/antenna, clocks, GPS provenance |
| BW16 FAP cannot connect | Wrong firmware family, Realtek vs ESP32 image confusion, UART/power/API |
| Poltergeist OLED works, IR fails | Selected firmware has not implemented IR path; check routing and safe power |
| Scan sees no 5 GHz AP | ESP32-S2/nRF24/CC1101 cannot scan it; verify BW16/C5 target, channel and firmware |
| PCAP/CSV missing | Actual board SD/Flipper SD/app export, save mode, clock/fix and media integrity |
| App loads but errors | Firmware API mismatch, different expected hardware or stale FAP |
| Normal Flipper app misbehaves afterward | Exit companion, power down/disconnect expansion, restore default GPIO/radio state |
- Flipper GPIO and module safety ยท Flipper Sub-GHz and CC1101 ยท Apps catalog.
- Community CC1101 pinout ยท Community nRF24 wiring.
- PINGEQUA RF Lab / combo pin map ยท nRF24 vendor support.
- AWOK Dual C5 Touch specification ยท existing AWOK setup and firmware split.
- PINGEQUA BW16 5Ghost firmware ยท matching Flipper FAP ยท FlipperHTTP BW16.
- Rabbit-Labs Poltergeist and manufacturer warnings ยท GhostESP project.
- Marauder for Flipper ยท SigRoam ยท Sub-GHz & nRF24 overview ยท wireless survey index.
BLE 5.0 via the STM32WB55 co-processor. Used for:
- Flipper mobile app connectivity
- BLE HID (Bluetooth keyboard/mouse emulation)
- BLE scanning and advertising
- BLE-based attacks via apps
Apps โ Bluetooth โ BLE Spam
Floods nearby devices with BLE advertising packets, triggering pairing/notification popups on:
- Apple devices: Fake AirPods pairing, AirTag found nearby, Apple TV setup, Apple Watch pairing
- Android: Fast Pair device popups (Samsung, Google Pixel, etc.)
- Windows: Swift Pair device popups
Pentesting use: Demonstrates BLE attack surface, proximity-based notification spam, and Bluetooth advertising exploitation. Effective physical security awareness demonstration.
Modes:
- iOS: AirPods Pro, AirPods Max, various Apple product spoofs
- Android: Fast Pair with various device profiles
- Windows: Swift Pair popups
- Spam All: cycles through all profiles
Apps โ Bluetooth โ Bluetooth Remote
Pairs as a BLE HID device and presents a navigation remote. Useful for controlling presentations wirelessly without a dedicated clicker.
BLE HID keyboard injection - connects wirelessly and injects keystrokes, same as BadUSB but over Bluetooth. Requires pairing first (target must accept connection).
Use case: USB ports blocked or disabled on target workstation, but Bluetooth is available.
With the WiFi Dev Board, Marauder can perform detailed BLE scanning - see BLE section under WiFi Dev Board.
The ESP32-S2-based WiFi Development Board attaches to the Flipper's GPIO header and provides 802.11 b/g/n WiFi capabilities. Flashed with Marauder firmware, it becomes a pocket WiFi pentesting platform controlled via the Flipper's UI and screen.
- Attach WiFi Dev Board to GPIO header (keyed, only fits one way)
- Flash Marauder firmware onto the ESP32:
- Windows: Use Spacehuhn's ESP web flasher at
esptool.spacehuhn.com(general-purpose ESP32 flasher, not Marauder-specific) - Or: download Marauder binary from
github.com/justcallmekoko/ESP32Marauder/releases
- Windows: Use Spacehuhn's ESP web flasher at
- Install Marauder Companion app on Flipper (Flipper Lab)
- Scan APs: Lists all visible access points with SSID, BSSID, channel, signal strength, encryption type
- Scan Stations: Lists connected client devices
- Scan AP+Station: Combined view showing which clients are connected to which APs
802.11 deauthentication frames - disassociates clients from their AP:
-
attack -t deauth- deauth all scanned APs -
attack -t deauth -b [BSSID]- target specific AP - Select target from scan results in Marauder UI before running attack
Pentest use: Demonstrate that anyone within radio range can forcibly disconnect clients. Effective for showing client why open/public WiFi is dangerous, and why 802.11w (Management Frame Protection) should be enabled.
On compatible targets and explicitly approved laboratory networks, certain capture modes may obtain WPA2-Personal authentication material. This is not equivalent to WPA3-SAE credential recovery:
- Scan APs โ select target
-
attack -t pmkid- attempts PMKID collection where supported by AP/client exchange; PMKIDs are not simply captured from beacons - Or:
attack -t wpa- captures full 4-way handshake (requires client authentication) - Save
.pcapto SD card - Transfer to Kali โ
hashcat -m 22000 capture.hc22000 wordlist.txt
Hosts a fake WiFi login page:
- Configure SSID name in Marauder settings
- Start Evil Portal
- The connected ESP32 accessory broadcasts the SSID when supported and deliberately enabled
- Connecting clients are redirected to captive portal
- Credentials captured to SD card log
Included portal templates:
- Generic WiFi login
- Hotel portal
- Coffee shop portal
- Custom HTML (place in SD card)
Broadcasts hundreds of fake SSIDs simultaneously:
- Confuses WiFi scanners
- Can be used to broadcast custom SSID messages
- Demonstrates WiFi landscape manipulation
Real-time channel-by-channel packet activity visualization. Useful for identifying:
- High-traffic channels to avoid or investigate
- Presence of hidden networks
- Anomalous traffic patterns
BLE features require a separate Bluetooth-capable ESP32 accessory and supported Marauder build. The stock ESP32-S2 Flipper WiFi Dev Board has no Bluetooth support. On supported BLE hardware, observed advertisements may expose manufacturer/service data; availability and logging depend on firmware.
Provides UI control of Marauder from the Flipper screen without needing a serial terminal. Install from Flipper Lab.
Menu structure:
Marauder Companion
โโโ WiFi Attacks
โ โโโ Scan APs
โ โโโ Scan Stations
โ โโโ Deauth Attack
โ โโโ PMKID Attack
โ โโโ Evil Portal
โ โโโ Beacon Spam
โโโ Bluetooth
โ โโโ BLE Scan
โ โโโ BLE Spam
โโโ Packet Monitor
โโโ Settings
Critical separation: the Flipper Zero runs its own firmware and the companion application (.fap), while a compatible connected ESP32 board runs Marauder. The Flipper does not contain a Wi-Fi radio. A Flipper Zero WiFi Dev Board (ESP32-S2) takes a Marauder image ending in _flipper.bin; a Marauder Dev Board Pro, BFFB, MultiBoard S3 or C5 expansion requires its own matching target, not the same image. See the standalone Marauder field labs and upstream Flipper instructions.
- Note Flipper firmware build, Marauder companion app version, expansion model/PCB revision, ESP32 chip and Marauder version. Photograph the board label without exposing serial numbers publicly.
- Backup the Flipper SD and any board SD logs. Update the Flipper through its own trusted update path; install a companion application compatible with the installed Flipper firmware using Flipper Lab or a maintained matching build.
- With the ESP32 expansion disconnected, identify its matching target from Marauder supported hardware and use the official Marauder updater or validated flasher. For the stock Flipper WiFi Dev Board, select
_flipper.bin; do not use a standalone display image. - Power off/reseat the accessory, connect it to the Flipper GPIO header and open the companion app. Confirm supported communication before any field survey. Keep SD/serial logging settings consistent with the installed build.
- Run only the owned-test-AP scan first, not an active attack menu. If the FAP cannot communicate, verify UART, companion/resources, firmware target, power and USB CLI separately.
- Record the Flipper app and accessory firmware versions side by side.
- With a known lab AP powered on, open the companion's supported AP scan. Observe one matching BSSID/channel.
- Repeat after a deliberate app restart to distinguish transient UART errors from persistent firmware mismatch.
- Record scan result, timing, error messages and missing feature menus. Do not assume older Flipper app screenshots match a current build.
Pass: an in-scope AP can be observed reproducibly with no unexpected transmissions, reboot, or loss of operator control.
- Check whether the specific app/build writes to Flipper SD, the external ESP32 SD, or neither. Some boards need an added microSD circuit, and not all app functions save the same artifact.
- Make one short authorized observation of a synthetic SSID, then stop it and safely close logging.
- Verify actual filename and storage location. For supported GNSS wardriving, consult the Marauder GPS guide and record fix status; Wi-Fi AP scans alone do not establish location.
- Export only the in-scope result, hash the original on the evidence workstation, and note whether a PCAP contains full frames or just summaries.
- If the Flipper SD remains empty, inspect companion settings and accessory SD support before repeating a scan.
- Compare the accessory's observations of a lab SSID with the AP controller's WPA2/WPA3, channel and PMF configuration.
- Create a separate unique training SSID on a client-owned AP, record its BSSID, and observe its appearance from the Flipper app.
- Compare independent Kismet + Wazuh observations to the Flipper/app log and AP controller. A successful match verifies visibility, not exploitability.
- Stop the test AP and confirm expected disappearance and SIEM alert disposition; preserve redacted evidence.
- Place owned test APs on explicitly permitted 2.4 GHz and (when hardware supports it) 5 GHz channels.
- Use the Flipper companion to record which APs actually appear, along with band/channel, antenna orientation and dwell time.
- A stock ESP32-S2 WiFi Dev Board is 2.4 GHz only and has no Bluetooth radio. Do not interpret failure to detect a 5 GHz AP or BLE tag as a missing network/device.
- On 5 GHz-capable C5 expansions, confirm the actual model, antenna and firmware build before claiming dual-band coverage.
- Use external sensors/controller inventory when a full site survey or throughput test is needed.
- While the test accessory is disconnected, preserve a known-working firmware image and identify the board's bootloader/recovery path.
- Install only a confirmed-compatible release, restart the Flipper app, and verify F1's known-AP test.
- If the connection fails, test the ESP32 directly via supported USB serial CLI; this separates ESP firmware/radio issues from the Flipper companion link.
- Avoid flashing the wrong partition table, board family or voltage domain. Power down before modifying a breakout. Never treat a failed firmware update as license to erase client data.
- Document successful rollback and any SD-card integrity warnings.
| Symptom | Likely cause & validation |
|---|---|
| "No Marauder" / serial timeout | Unsupported FAP, wrong ESP32 firmware target, loose GPIO connection, serial Log Device conflict or insufficient power |
| Scan works, no stored PCAP | Missing SD, app export path mismatch or unsupported capture mode |
| BLE menu missing on ESP32-S2 | Expected hardware limitation; the S2 cannot run BLE scanning |
| 5 GHz SSID absent | ESP32-S2 cannot scan 5 GHz; check C5 expansion and firmware if applicable |
| Scan data differs from standalone Marauder | Companion app feature coverage, serial transport, storage and build differ |
| Failed reflash/boot loop | Restore exact board firmware and partition layout from the supported installer |
Reporting: identify Flipper firmware/FAP and ESP32 firmware separately. Include authorization, BSSID/SSID redaction, timestamps, expected versus actual result, GNSS/storage provenance, USB/UART state, AP configuration evidence, WIDS corroboration and cleanup. Do not equate credential/handshake collection with ordinary reconnaissance or infer WPA3-Enterprise vulnerabilities from a scan.
After capturing a handshake .pcap:
# Convert pcap to hashcat format
hcxpcapngtool -o hash.hc22000 -E essids capture.pcap
# Crack with hashcat
hashcat -m 22000 hash.hc22000 /usr/share/wordlists/rockyou.txt
# With rules for better coverage
hashcat -m 22000 hash.hc22000 rockyou.txt -r /usr/share/hashcat/rules/best64.rule
# PMKID only
hashcat -m 22000 hash.hc22000 rockyou.txt --attack-mode 0| App | Source | Description |
|---|---|---|
| MFKey | Flipper Lab | Mifare Classic key recovery via reader nonce capture |
| MIFARE Classic Editor | Flipper Lab | Read/write/edit Mifare Classic sector data |
| NFC Magic | Flipper Lab | Write to Gen1/Gen2 magic cards for cloning |
| Mifare Nested | Unleashed/Momentum | Nested attack for offline key recovery |
| Picopass | Flipper Lab | HID iClass card reading and emulation |
| MFP Reader | Flipper Lab | Mifare Plus SL3 reader/dumper |
| NFC Playlist | Flipper Lab | Cycle through saved NFC cards automatically |
| NFC Login | Flipper Lab | Use NFC card as PC login credential via USB HID |
| App | Source | Description |
|---|---|---|
| RFID Fuzzer | Unleashed/Momentum | Brute-force credential ranges |
| Seader | Flipper Lab | Raw Wiegand capture via GPIO (connects to real reader) |
| Wiegand | Flipper Lab | Wiegand protocol analysis and injection |
| App | Source | Description |
|---|---|---|
| Sub-GHz Bruteforcer | Unleashed/Momentum | Fixed-code fuzzing (Princeton, CAME, etc.) |
| Sub-GHz Remote | Flipper Lab | Custom remote button layouts for saved signals |
| Sub-GHz Playlist | Flipper Lab | Sequence multiple Sub-GHz transmissions |
| Spectrum Analyzer | Flipper Lab | Real-time RF spectrum visualization |
| POCSAG Pager | Flipper Lab | Decode POCSAG pager messages |
| Weather Station | Flipper Lab | Decode 433MHz weather sensor data |
| Sub-GHz Chat | Flipper Lab | Text messaging over Sub-GHz (Flipper to Flipper) |
| App | Source | Description |
|---|---|---|
| Brute Force IR | Momentum | Iterate through all codes for device type |
| IR Scope | Flipper Lab | Visualize raw IR signal waveforms |
| TV Remote (universal) | Built-in | Large built-in IR remote database |
| App | Source | Description |
|---|---|---|
| UART Terminal | Flipper Lab | Serial console via GPIO pins |
| Logic Analyzer | Flipper Lab | 4-channel digital signal capture |
| I2C Scanner | Flipper Lab | Scan I2C bus for device addresses |
| SPI Tools | Flipper Lab | SPI device communication |
| Tone Generator | Flipper Lab | Square wave output on GPIO |
| Wire Tester | Flipper Lab | Continuity testing |
| GPIO Unlocker | Flipper Lab | Unlock 5V on GPIO pin 18 |
| Oscilloscope | Flipper Lab | Basic voltage waveform display |
| PWM | Flipper Lab | PWM signal generation |
| Unitemp | Flipper Lab | Temperature/humidity sensor reading (DHT, DS18B20) |
| App | Source | Description |
|---|---|---|
| Marauder Companion | Flipper Lab | Full UI for ESP32 Marauder WiFi attacks |
| WiFi Scanner | Flipper Lab | Basic AP scanning |
| Evil Portal | Flipper Lab | Standalone captive portal (Marauder-based) |
| Diabolic Drive | Flipper Lab | WiFi-controlled BadUSB via ESP32 |
| App | Source | Description |
|---|---|---|
| BLE Spam | Momentum/Unleashed | BLE advertising spam (iOS/Android/Windows) |
| Bluetooth Remote | Built-in | BLE HID remote control |
| Bad BT | Momentum/Unleashed | BLE HID keyboard injection |
| BLE Keyboard | Flipper Lab | Custom BLE keyboard emulation |
| FindMy Flipper | Flipper Lab | Spoof Apple AirTag location beacons |
| File | Description |
|---|---|
| PNWC Payload Library | Full suite - see separate documentation |
| Rubber Ducky scripts | Compatible with existing Hak5 .txt payloads |
| UAC bypass demo | Common UAC bypass demonstration |
| Windows enumeration | Quick user/network enumeration |
| App | Source | Description |
|---|---|---|
| TOTP Authenticator | Flipper Lab | Hardware TOTP token (Google Auth compatible) |
| Password Manager | Flipper Lab | Local encrypted credential store |
| U2F | Built-in | FIDO U2F hardware security key |
| WiFi Marauder | ESP32 firmware | Full WiFi attack suite |
| Seader | Flipper Lab | Wiegand reader interface for badge capture |
| App | Source | Description |
|---|---|---|
| Multi Converter | Flipper Lab | Unit conversion, base conversion (hex/bin/dec) |
| Calculator | Flipper Lab | Basic calculator |
| Metronome | Flipper Lab | Timing tool |
| Barcode Generator | Flipper Lab | Generate and display barcodes |
| QR Code | Flipper Lab | Generate/display QR codes |
| Resistance Calc | Flipper Lab | Resistor color band calculator |
| WAV Player | Flipper Lab | Audio playback via GPIO (DTMF replay etc.) |
| Text Viewer | Flipper Lab | Read text files from SD card |
| HEX Viewer | Flipper Lab | Inspect binary files on SD card |
Portal of Flipper, Doom, Tetris, Snake, Flappy Bird - various on Flipper Lab. Useful for social engineering "hey look at this" openers.
Before any physical pentest engagement:
- Charge Flipper to 100%
- Verify SD card has all payloads loaded
- Test BadUSB payloads on your own machine
- Confirm LHOST/LPORT in reverse shell payloads
- Verify listener is reachable from test network
- Load relevant Sub-GHz frequencies for client region
- Carry blank T5577 RFID cards and Gen2 NFC magic cards
Step 1: Reconnaissance
- Visually identify card readers on target doors
- Note manufacturer logos (HID, Allegion, Bosch, Honeywell)
- Identify card format used by employees (proximity, smart card, iClass)
Step 2: Card Capture
- LF (HID Prox / EM4100):
125kHz RFID โ Read- works through wallets/purses at ~5cm - HF Mifare Classic:
NFC โ Read- brief contact needed - HF iClass:
Apps โ Picopass โ Read
Step 3: Reader Nonce Capture (Mifare Classic)
-
NFC โ Detect Reader- hold Flipper near reader - Captures crypto nonces โ
Apps โ NFC โ MFKey โ Run - Recovers sector keys in ~30 seconds
Step 4: Full Card Read
- Re-read target card with recovered keys
NFC โ Saved โ [card] โ Read (full)
Step 5: Cloning
- Write to Gen2 magic card:
NFC โ Saved โ [card] โ Write - Test clone at reader
- Write to T5577 for LF cards:
125kHz RFID โ Saved โ [card] โ Write
Step 6: Documentation
- Photograph access readers
- Note card type, reader model, facility code
- Document clone success/failure
- Provide client with physical clone card as evidence
Sub-GHz Assessment:
-
Sub-GHz โ Frequency Analyzer- identify active frequencies on site -
Sub-GHz โ Read- capture gate/door/barrier remotes - Test replay on target
-
Sub-GHz Bruteforcer- if fixed-code, demonstrate full code space compromise
WiFi Assessment (with ESP32 Dev Board):
- Marauder โ Scan APs - enumerate all SSIDs, note encryption types
- Identify any open networks or WEP (rare but still exists)
- Marauder โ PMKID - capture from all WPA2 targets
- Marauder โ Scan Stations - identify client devices
- Transfer .pcap to Kali โ crack with hashcat
- Marauder โ Deauth - demonstrate forced disconnection
- Document: open networks, weak passwords, lack of 802.11w
Testing physical security:
- Plant Flipper at workstations (with authorization)
- Run
win-lockscreen-awareness-test.txton unlocked machines - Document which machines were accessible and when
- Run
win-security-audit.txtto capture security posture - Run
win-sysinfo-full.txt+win-network-recon.txtfor full picture
Authorized reverse shell test:
- Pre-position listener:
rlwrap nc -lvnp 4444 - Deploy
win-revshell-ps.txt - Demonstrate shell access
- Run enumeration commands in shell
- Exit, run
win-cleanup.txtto remove artifacts
BLE Spam demo (client meeting room):
Apps โ BLE Spam โ iOS โ AirPods- Everyone's iPhone starts showing AirPods pairing requests
- Talking point: BLE advertising is untrusted and unauthenticated
IR demo (boardroom projector):
Infrared โ Universal Remotes โ Projector- Demonstrate ability to cut projector feed
- Talking point: IR receivers are often in boardrooms, anyone can transmit
Unlocked workstation demo:
- Find unlocked machine during walk-through
- Deploy
win-lockscreen-awareness-test.txt - Machine drops evidence file, shows popup, locks itself
- Debrief with staff: "Your workstation was unlocked and we ran code on it in under 15 seconds"
Always run win-cleanup.txt after any engagement to remove:
- All
pnwc_*.txtoutput files - Beacon scripts and logs
- Registry persistence keys
- Temp PowerShell scripts
Fast intake workflow:
- Plug Flipper into client machine
- Run
win-intake-form.txt- opens Notepad with auto-filled system info - Fill in reported issue while system info populates in background
- Run
win-inventory.txt- captures full HW/SW for your records
Common issue investigation:
- Slow machine:
win-sysinfo-full.txtโ check process list and startup items - Network issues:
win-network-recon.txtโ check IP config, DNS, active connections - Security concern:
win-security-audit.txtโ full posture check in one shot
Identify hosts on client network without Nmap:
- Edit
$subnetinwin-host-discovery.txt - Deploy โ get ARP-based host list with DNS and open ports
- Pairs with your laptop running Nmap for confirmation
Console access to networking gear:
- Connect GPIO pins 14/16/17 to RJ45 via console cable
Apps โ GPIO โ UART Terminal- Set baud rate (9600 for Cisco, 115200 for UniFi)
- Direct console session without carrying a USB-serial adapter
Quick security posture for SMB clients:
- Run
win-security-audit.txt- generates full report - Key items to check in output:
- Defender real-time protection enabled?
- UAC set to appropriate level?
- BitLocker enabled on laptops?
- RDP enabled/disabled as expected?
- SMB1 disabled?
- PowerShell logging enabled?
Active Directory review:
- From a domain-joined machine, run
win-ad-enum.txt - Key findings to look for:
- Password never expires accounts
- Stale accounts (90+ days no logon)
- Unauthorized Domain Admin members
- Weak password policy (length < 12, no lockout)
- Computers running end-of-life OS
Keep this reference on your phone or printed in your bag:
| Scenario | Payload/App |
|---|---|
| Quick system info | win-sysinfo-full.txt |
| Network map | win-host-discovery.txt |
| WiFi passwords | win-wifi-dump.txt |
| Security check | win-security-audit.txt |
| Full AD dump | win-ad-enum.txt |
| Console access | UART Terminal app |
| Badge clone | NFC โ Read โ Write |
| Gate remote copy | Sub-GHz โ Read โ Send |
| Client intake | win-intake-form.txt |
| Quick fixes | win-rapid-remediation.txt |
| Clean up | win-cleanup.txt |
| Flipper Capability | Complements | Combined Workflow |
|---|---|---|
| Sub-GHz capture/replay | HackRF One | Flipper grabs signal in field, HackRF does deep analysis back at bench (replay attacks, signal decoding, frequency deviation analysis) |
| BadUSB | Bash Bunny | Flipper for covert quick-deploy (looks like charging), Bunny for complex multi-stage payloads requiring multiple payloads |
| WiFi Marauder | WiFi Pineapple | Flipper for stealthy pocket recon, Pineapple for full engagement (deauth, PineAP, modules) |
| BLE Spam/Scan | Ubertooth One | Flipper demos attack surface to client, Ubertooth captures raw BLE traffic for analysis |
| RFID/NFC | ProxMark3 (if added) | Flipper for quick field reads, ProxMark for advanced LF/HF analysis and attacks |
| GPIO/UART | Bus Pirate 5 | Flipper for quick console access onsite, Bus Pirate for deep JTAG/SWD/SPI hardware work at bench |
| BLE HID | Rubber Ducky | Flipper covers both BadUSB and BLE, Ducky for advanced multi-payload |
| Sub-GHz | Flipper Zero SDR app | Flipper transmits, HackRF verifies signal quality |
| IR | SDR++ with RTL-SDR | Flipper quick replay, SDR for protocol analysis |
Using Flipper with Kali:
- Post-handshake capture:
hcxpcapngtoolโhashcat - BadUSB as reverse shell entry point โ catch shell in
metasploitornc - Sub-GHz captures transferred via qFlipper for URH (Universal Radio Hacker) analysis
TrueNAS / Proxmox:
- UART Terminal for serial console to servers without iDRAC/iLO
- Sub-GHz sensors can feed into Home Assistant via Marauder BLE bridge
Home Assistant:
- IR blaster integration: Flipper IR files compatible with HA
broadlinkformat (with conversion) - Sub-GHz sensor decoding via Marauder
SD:/
โโโ apps/
โ โโโ NFC/
โ โ โโโ mfkey.fap
โ โ โโโ nfc_magic.fap
โ โ โโโ mifare_nested.fap
โ โ โโโ picopass.fap
โ โโโ Sub-GHz/
โ โ โโโ subghz_bruteforcer.fap
โ โโโ Bluetooth/
โ โ โโโ ble_spam.fap
โ โ โโโ bad_bt.fap
โ โโโ GPIO/
โ โ โโโ uart_terminal.fap
โ โ โโโ logic_analyzer.fap
โ โโโ Tools/
โ โโโ totp.fap
โโโ badusb/
โ โโโ windows-recon/
โ โโโ windows-pentest/
โ โโโ windows-it-admin/
โ โโโ linux-recon/
โ โโโ network/
โ โโโ social-engineering/
โโโ nfc/
โ โโโ captures/ # Raw reads from field
โ โโโ clones/ # Cloned/ready cards
โโโ subghz/
โ โโโ captures/ # Field captures
โ โโโ raw/ # Raw captures
โโโ lfrfid/
โ โโโ captures/
โโโ infrared/
โ โโโ custom/ # Learned remotes
โ โโโ database/ # UberGuidoZ files
โโโ ibutton/
โโโ logs/
Sub-GHz signals (UberGuidoZ):
github.com/UberGuidoZ/Flipper/tree/main/Sub-GHz
Download and place in SD:/subghz/
Infrared codes (UberGuidoZ):
github.com/UberGuidoZ/Flipper/tree/main/Infrared
Place in SD:/infrared/
NFC tools and extra files:
github.com/UberGuidoZ/Flipper/tree/main/NFC
| Resource | URL |
|---|---|
| Flipper Zero official | flipper.net |
| qFlipper download | flipper.net/pages/downloads |
| Flipper Lab (app catalog) | lab.flipper.net |
| Official documentation | docs.flipper.net |
| Firmware | Repository |
|---|---|
| Unleashed | github.com/DarkFlippers/unleashed-firmware |
| Momentum | github.com/Next-Flip/Momentum-Firmware |
| RogueMaster | github.com/RogueMaster/flipperzero-firmware-wPlugins |
| Resource | URL |
|---|---|
| UberGuidoZ Signal/App Collection | github.com/UberGuidoZ/Flipper |
| Awesome Flipper Zero | github.com/djsime1/awesome-flipperzero |
| Marauder Firmware | github.com/justcallmekoko/ESP32Marauder |
| Flipper subreddit | reddit.com/r/flipperzero |
| Resource | URL |
|---|---|
| ufbt build tool | github.com/flipperdevices/flipperzero-ufbt |
| Flipper app SDK | github.com/flipperdevices/flipperzero-firmware |
| App examples | github.com/flipperdevices/flipperzero-firmware/tree/dev/applications/examples |
| Tool | Use |
|---|---|
| hashcat | WPA2 handshake cracking |
| hcxpcapngtool | Convert Marauder .pcap to hashcat format |
| Universal Radio Hacker (URH) | Analyze Sub-GHz raw captures |
| CyberChef | Decode/analyze NFC card data |
| MIFARE Classic Tool (Android) | Cross-reference NFC reads |
| Proxmark3 | Advanced LF/HF RFID (complements Flipper) |
- Computer Fraud and Abuse Act (CFAA) - 18 U.S.C. ยง 1030
- Electronic Communications Privacy Act (ECPA)
- Washington State RCW 9A.90 - Washington Cybercrime Act (RCW 9A.52.110 was repealed in 2016; current law is RCW 9A.90.040 computer trespass 1st degree, RCW 9A.90.050 2nd degree)
- FCC Part 15 - Unlicensed RF devices
| Frequency | Primary Use | Region |
|---|---|---|
| 315.000 MHz | Garage doors, auto remotes | North America |
| 390.000 MHz | Garage doors | North America |
| 433.920 MHz | EU remotes, sensors, alarms | Europe/Global |
| 434.420 MHz | Some EU systems | Europe |
| 868.350 MHz | Z-Wave EU, alarm sensors | Europe |
| 915.000 MHz | Z-Wave US, LoRa | North America |
| 925.000 MHz | ISM band devices | Global |
FFFFFFFFFFFF (default, most common)
A0A1A2A3A4A5 (MAD sector default)
B0B1B2B3B4B5
4B0B20107CCB
AABBCCDDEEFF
000000000000
D3F7D3F7D3F7 (NFC Forum)
Special: ENTER, BACKSPACE, TAB, SPACE, CAPSLOCK, DELETE
Navigation: HOME, END, INSERT, PAGEUP, PAGEDOWN
Arrows: UP, DOWN, LEFT, RIGHT
Function: F1-F12
Modifiers: CTRL, SHIFT, ALT, GUI (Windows key)
Numpad: NUMLOCK, KP_0 through KP_9
scanap Scan access points
scanst Scan stations
stopscan Stop current scan
attack -t deauth -b [BSSID] Deauth specific AP
attack -t pmkid PMKID capture all
stopattack Stop current attack
list -a List scanned APs
list -s List scanned stations
clearlist -a Clear AP list
clearlist -s Clear station list
- README.md - Documentation section index: all guides and cheat sheets in this directory
- evil_m5.md - M5Cardputer with Evil-M5Project: complementary ESP32-based WiFi attack tool
- bjorn_pi.md - Bjorn Pi: network-service brute-force and exfiltration tool (network layer vs. Flipper's RF layer)
- bruce_firmware.md - Bruce firmware alternative for Cardputer: multi-radio (Sub-GHz, NFC, IR, BLE, FM)
- WifiMarauder_CheatSheet.md - ESP32 Marauder cheat sheet (the firmware running on Flipper's WiFi Dev Board)
- WiFiMarauder_Guide.md - Full Marauder guide for WiFi pentesting workflows
-
LAB5 MonsterC5 / projectZero - separate C5 JanOS image and
Lab_C5.fapFlipper controller, not a Marauder or Evil-M5 payload - hcxtoolshashcat.md - Converting Marauder .pcap captures to Hashcat format and cracking WPA2
- ../HardwareHacking/BusPirate.md - Bus Pirate 5: deep hardware interface tool that complements Flipper's GPIO work
- ../HardwareHacking/Chapter1.md - Hardware hacking foundations (UART, SPI, I2C, JTAG)
Pacific Northwest Computers | Vancouver, WA github.com/Pnwcomputers/ULTIMATE-CYBERSECURITY-MASTER-GUIDE
Guide version: 1.0 | Last updated: 2026 For the latest version, see the GitHub repository
๐ Source: Documentation/flipper_zero_guide.md | โ๏ธ Suggest an edit | โฌ
๏ธ Back to Technical Guides & Cheat Sheets
- ๐บ๏ธ Browse by Topic
- ๐ All Repository Files
- ๐งญ Learning Paths
- ๐ Master Guide
- ๐ค Glossary
- โ๏ธ Legal & Disclaimer
๐ Foundations & Learning
๐ก๏ธ Defense & Investigations
- Incident Response
- Open Source Intelligence (OSINT)
- Reverse Engineering
- Operations Security (OPSEC)
- Compliance
โ๏ธ Platforms & Infrastructure
๐ก Hardware, Wireless & Field Projects
- PNWC Cyberdeck
- Hardware Testing
- Hardware Hacking
- Software-Defined Radio
- Wardriving
- uConsole
- Space Security
๐งฐ Assessment & Field Reference
๐ฆ Downloads & Project Resources
๐๏ธ Additional Topics