$0.00
0

Cart

BomberCat

Read, emulate, and relay NFC and magnetic-stripe card data from one open-source board — the field tool for pentesters auditing contactless readers and payment terminals.

$119.00

In stock

In the box

BomberCat board (RP2040 + PN7150 + ESP32, black)
NFC antenna
USB-C to USB-A cable (1 m)
Antistatic bag + product/spec labels

Not included

Battery (3.7 V LiPo/Li-Ion) — buy separately
Case — provided as 3D-print STL files in the repo, not shipped
A second BomberCat, only if you want a board-to-board relay

You also need

A 3.7 V LiPo/Li-Ion battery to run it off USB (onboard charger included; battery not)
For an NFCGate relay: a second peer (another BomberCat or the NFCGate Android app), a PC running the nfcgate-server, and a shared WiFi network
A Linux PC for the bombercat CLI (macOS/Windows should work, untested); Wireshark for APDU capture
A card and a reader/terminal you are authorized to test

What is BomberCat?

BomberCat is an open-source security tool that combines the two card technologies you meet most in the field: NFC and magnetic stripe, used in access control, identification, and payment cards.

On one board it reads and emulates NFC tags and smart cards, spoofs magnetic-stripe tracks wirelessly through an embedded coil (MagSpoof), and fingerprints the readers and terminals that probe it.

It also works as an NFCGate-compatible relay endpoint. NFCGate is the open-source project for relaying contactless sessions over a network — so a card in one place can be presented to a reader you are authorized to test somewhere else.

An RP2040 handles USB and control, an NXP PN7150 drives the NFC front end, and an ESP32 co-processor adds WiFi and BLE. Its DetectReaders firmware fingerprints EMV terminals and skimmers — the reader-detection job the retired Hunter Cat NFC used to do.

Hardware and firmware are open source, on GitHub. It is a wireless pentesting tool for authorized security audits only.

Demonstrate an NFC relay against a reader you're authorized to test

Situation: you need to show an NFCGate relay against a contactless or EMV terminal on systems you’re authorized to test. What you do: the board ships with NFCGate pre-flashed, so you just pair two peers (two BomberCats, or one BomberCat and the NFCGate Android app) through an nfcgate-server on a shared WiFi, set the role and a matching session byte, and start the relay from the CLI. Result: a full EMV transaction relayed end-to-end — validated on real hardware at roughly 4.5 s per transaction — with every APDU tapped straight into Wireshark for your report.

Audit a legacy magstripe reader, or fingerprint an unknown terminal

Situation: a magnetic-stripe reader is in scope, or you can’t identify a terminal before trusting it. What you do: load MagSpoof to replay track data from your own test cards wirelessly over the reader (all three tracks, including Track 1+2), or flash DetectReaders so the board presents an emulated card and fingerprints whatever reads it. Result: the stripe reader reacts with no physical card present, and DetectReaders flags the terminal — a PPSE SELECT means an EMV payment terminal; known AIDs mean Visa/Mastercard/Amex or NDEF readers.

Run a hands-on NFC lab, workshop, or CTF

Situation: you’re teaching contactless security or running a CTF station and want everyone on real hardware. What you do: flash DetectTags to read UIDs and technologies (ISO 14443-A/B, ISO 15693, FeliCa), or the all-in-one WiFiWebServer firmware so each board becomes its own WiFi access point with a browser UI. Result: a self-contained NFC and magstripe bench, reprogrammable in Arduino, CircuitPython, or MicroPython, that each participant drives from a phone or laptop.

Start in 10 minutes

  1. Install the bombercat CLI on a Linux PC (Python; add your user to the dialout group for serial access): github.com/ElectronicCats/bombercat-tools
  2. Configure the NFCGate relay over USB-serial: set the nfcgate-server host:port (default TCP 5566), a matching session byte (1–255) on both peers, and the role (reader or card). Config persists in flash.
  3. Stand up the nfcgate-server yourself following the repo deployment guide (Docker or systemd), and pair the second peer (another BomberCat or the NFCGate Android app) on the same WiFi.
  4. Start the relay from the CLI and capture the APDUs to Wireshark with :apdu + bombercat capture (classic pcap, DLT_ISO_14443).
  5. To switch modes, run bombercat flash DetectReaders (or DetectTags / MagSpoof) — resets to UF2 automatically, no Arduino toolchain required.
Weight0.050 g
Dimensions18 × 12.5 × 2 cm
MCU

RP2040 (dual-core ARM Cortex-M0+, 133 MHz)

NFC chip

PN7150 (NXP)

WiFi + BLE

ESP32 co-processor — WiFi (WiFiNINA), BLE (ArduinoBLE)

MagSpoof

TC4424 driver, embedded coil (30 turns / 30 mm) since HW v1.3

Operating voltage

3.3 V I/O · 5 V input over USB-C

External flash

16 Mbit (2 MB) QSPI (W25Q16JV)

RAM / ROM

264 kB SRAM · 16 kB boot ROM

Connector

USB-C 2.0 (USB, Serial/UART, NFC)

Bootloader

UF2 (double-tap reset to enter)

Battery

3.7 V LiPo/Li-Ion, not included (onboard MCP73831 charger, green CHG LED)

RF protocols

NFCIP-1/2, ISO 14443A/B, FeliCa, MIFARE Classic 1K/4K, NFC Forum tags 1–5, ISO 15693/ICODE

Dimensions / weight

~65 × 38.5 mm board · 10 g (40 g with 3D-printed case)

Programming

Arduino · CircuitPython · MicroPython

Open hardware

CERN-OHL v1.2 (hardware) · GPL-3.0 (firmware)

FeatureBomberCatHunter Cat NFC (retired)MagSpoof V5NFCGate + 2 Android phones
What it doesNFC read/emulate, magstripe spoof, WiFi relay, reader detection — one boardDetected NFC readers/skimmers (defensive sensor)Emulates magnetic-stripe cardsRelays NFC/APDUs between two phones via a server
NFC read / emulateYes (PN7150)Detection onlyNoYes (phone NFC)
Relay over networkYes — NFCGate-compatible over WiFi/TCP (~4.5 s)NoNoYes (the reference app)
Magstripe (MagSpoof)Yes — embedded coil, Track 1+2NoYes (its whole purpose)No
Reader / terminal detectionYes — DetectReaders firmwareYes — its core functionNoNo
What you needOne board (+ a second peer & server for board-to-board relay)The boardThe boardTwo Android phones (with NFCGate’s rooted module) + a server
Does this replace the Hunter Cat NFC?
Yes. The Hunter Cat NFC is retired, and BomberCat is its successor. Its DetectReaders firmware does the same reader and terminal fingerprinting the Hunter Cat NFC was built for — it emulates a card and fingerprints whatever reader probes it (a PPSE SELECT flags an EMV terminal; known AIDs flag Visa/Mastercard/Amex or NDEF readers) — now as one mode among NFC read/write, card emulation, MagSpoof, and NFCGate relay on a single board.
Yes. BomberCat is an NFCGate-compatible relay endpoint with selectable reader and card roles. It pairs with a second BomberCat or with the NFCGate Android app through an nfcgate-server. Both paths are validated end-to-end on real hardware, relaying full EMV transactions over WiFi/TCP at roughly 4.5 s per transaction, on systems you’re authorized to test. Note: the TCP link is currently plaintext (no TLS yet).
Not necessarily. A relay needs two peers, but the second peer can be the NFCGate Android app instead of a second board. For non-relay work — reading tags, detecting readers, MagSpoof — one board is enough. The phone-as-reader path works on a stock phone; the phone-as-card path needs a rooted Android with NFCGate’s module.
No. BomberCat ships with the NFCGate firmware pre-flashed and is driven from the bombercat CLI. Switching to another mode (DetectTags, DetectReaders, MagSpoof) is one bombercat flash command over UF2 — no Arduino toolchain required. If you want to change how it behaves, it’s fully open source and programmable in Arduino
Free shipping to the US on orders +$200 USD · to Mexico on orders +$75 USD