Home

FlipDeFlock

Snoop onto them as they snoop onto us.

FlipDeFlock is a Flipper Zero app that pairs with an ESP32 board to survey the radio around you for surveillance hardware: Flock Safety / ALPR cameras, Bluetooth trackers that follow you, weak or spoofed Wi-Fi, and active Wi-Fi attacks. The Flipper handles the screen, GPS tagging, and logging; the ESP32 does the Wi-Fi sniffing the Flipper's BLE-only radio can't.

It's for security assessments, anti-surveillance awareness, and CTF/research.

Passive recon only. It listens; it never transmits — no deauth, injection, or jamming. Detections are indicators, not proof: OUI-only matches are possible, not confirmed, so verify by eye. Use it only where you are authorized to. Full statement: Legal & Disclaimers.

Current release: v0.45, built against Flipper API 87.1 (stock OFW and Momentum).

Who this is for

• People at risk of being followed — Bluetooth tracker stalking is a documented pattern in intimate-partner abuse, and detection here runs offline, on a device that isn't a phone.
• Journalists and researchers documenting surveillance infrastructure.
• Civic transparency mappers, including the DeFlock community.
• Security practitioners running authorized site surveys and access-control reviews.

Get started

• Installation — install a release, or build from source with ufbt.
• Features & Board Modes — what each screen does, Marauder vs. Companion firmware, the detection confidence ladder.
• Hardware Compatibility — which ESP32 boards work, wiring, optional GPS.
• FAQ — legality, privacy, reliability, and how this relates to Flock Safety and DeFlock.
• Troubleshooting — common failure modes and what they mean.
• Legal & Disclaimers — license, trademark, and the passive-only stance, stated in full.

Elsewhere in the repo

• README
• LICENSE (GPL-3.0-or-later)
• CONTRIBUTING.md
• SECURITY.md
• changelog.md — full version history

FlipDeFlock is actively developed, not finished. Features are still landing and detection signatures change as surveillance hardware changes. Treat detections as indicators, verify by eye, and if you're relying on it for anything that matters, read the code and confirm the behavior yourself.