Monday, November 16, 2026

Raspyjack for pocket-sized wireless testing on Raspberry Pi and Cardputer

Raspyjack for pocket-sized wireless testing on Raspberry Pi and Cardputer

Raspyjack packages Wi-Fi, Bluetooth LE, NFC/RFID and sub-GHz radio testing workflows into a small offensive toolkit for Raspberry Pi and M5Stack Cardputer, aimed at authorized red-team work.

Tool7h30th3r0n3/Raspyjack — small offensive network toolkit for Raspberry Pi with a Waveshare 1.44″ LCD HAT and M5Stack Cardputer
CategoryWireless and hardware offensive security toolkit (Python)
Primary UsePortable Wi-Fi, bluetooth-le, nfc, rfid and sub-ghz assessment workflows plus wardriving from a pocket-sized device
Safe UseFor authorized penetration tests, red-team engagements, lab environments and hardware you own or have written permission to test
Telemetry NoteRadio activity from this toolkit (deauthentication frames, BLE scanning bursts, NFC polling) is directly observable by wireless intrusion detection systems, RF monitoring and AP controller logs; the on-device LCD makes its use conspicuous in physical environments

Raspyjack is a compact offensive security toolkit written in Python, designed to run on two very specific pieces of hardware: a Raspberry Pi (the repo topics call out the pi-zero-2w in particular) paired with a Waveshare 1.44″ LCD HAT, and the M5Stack Cardputer / CardputerZero. The choice of platform tells you a lot about the design philosophy before you read a single line of documentation: this is a pocket-scale device for wireless work, not a framework you install on a beefy assessment laptop. At roughly 1,340 stars under an MIT license, it has clearly resonated with the hardware-hacking community that clusters around the Cardputer ecosystem.

The topic list on the repository is unusually informative, effectively functioning as a feature map when the README itself is sparse. It spans wifi, bluetooth-le, nfc, rfid, sub-ghz, sdr and wardriving, along with deauth and ethical-hacking. Taken together, this describes a multi-radio Swiss-army knife: the same physical device can move between 2.4 GHz Wi-Fi analysis, BLE scanning, contactless card interaction, and lower-frequency sub-GHz probing, which is exactly the radio surface a red-teamer encounters when testing physical and wireless perimeter controls.

The inclusion of the Waveshare 1.44″ LCD HAT is not cosmetic. On a headless pi-zero-2w you would normally drive such a toolkit over SSH from another machine, which halves its portability. A small display plus the Cardputer's built-in keyboard means the operator can interact with menus, read scan output and trigger workflows entirely on-device — the form factor of a purpose-built pentest gadget rather than a general-purpose computer. That interaction model is a recurring theme in the small-screen offensive tooling niche that has grown around M5Stack hardware since the Cardputer shipped.

It is worth pausing on the deauth topic, because it is the capability most likely to draw scrutiny. Wi-Fi deauthentication attacks are trivially detectable and legally hazardous outside owned infrastructure: they inject management frames that knock clients off an access point, and every mainstream wireless IDS product signatures them. In an authorized context — testing the resilience of your own lab network, validating that 802.11w protected management frames are enforced, or demonstrating to a client why their wireless monitoring should alarm on this traffic — it is a legitimate teaching and assessment primitive. Outside that context it is a denial of service against someone else's network, and readers should treat it accordingly.

The wardriving topic points to a passive-collection workflow: enumerating access points and their beacons, typically logging BSSID, SSID, channel and security configuration to a file for later analysis. This is the most defensible capability in the toolkit from a legal standpoint in most jurisdictions, since it is fundamentally about observing radio emissions rather than injecting anything. It maps cleanly onto defensive use cases too: a wardrive of your own campus is a cheap way to find rogue APs, misconfigured WEP/legacy networks, or APs that were deployed and forgotten. A Python implementation suggests the output is likely CSV or similar plaintext logs that drop straight into spreadsheet or mapping tooling.

The nfc/rfid pairing suggests tooling for reading and interacting with contactless credentials — the proximity cards that dominate physical access control. For defenders and blue teams, tools in this category are valuable for auditing your own badge estate: checking whether issued cards are UID-only clones waiting to happen, or whether they implement mutual authentication properly. The sub-ghz topic extends the same idea to the RF remotes and sensors that run on 315/433 MHz bands — garage doors, wireless doorbells, sensor pendants — which are a classic weak link in physical pentests. The sdr topic implies at least some workflow built around software-defined radio rather than dedicated transceiver add-on boards.

Architecturally, a Python toolkit targeting these two platforms is almost certainly a layer of menus and workflow glue over existing radio interfaces — the standard Linux wireless stack for Wi-Fi, BlueZ-adjacent tooling for bluetooth-le, and whatever NFC/RFID reader or SDR dongle the operator attaches. That is the sensible design: Python gives fast iteration and readable code, and the heavy lifting of frame injection and radio control lives in the kernel and driver layer. The dual-platform targeting (Raspberry Pi and Cardputer, which is itself ESP32-based) means the author has kept the workflow layer portable rather than baking it into one board's quirks — though it is reasonable to expect some feature asymmetry between the two targets given their very different CPUs.

For the professional evaluating whether to deploy this, the honest caveat is that the repository README is empty at the time of writing, so the topic-driven picture above is inferred from the author's own metadata rather than documented behavior. That matters operationally: you do not yet have documented statements about dependencies, supported radio chipsets, or what hardware add-ons are required for the nfc and sub-ghz features. Before fielding it on an engagement, an authorized assessor should review the source on the main branch, verify what the deauth workflows actually send, and confirm the radio hardware in their kit is supported.

On the defensive side of the ledger, tools like Raspyjack are worth studying even if you never run them, because they define the baseline capability of a sub-$50 adversary platform. If your wireless monitoring does not alert on deauthentication bursts, if your badge system trusts UIDs without cryptographic challenge, or if your 433 MHz door controller accepts replayed codes, then a pocket toolkit like this turns those gaps into a five-minute physical-breach demo. Building your detection story against exactly this class of device is a productive use of the repo.

In sum, Raspyjack sits at the intersection of three trends: cheap single-board computers, the M5Stack Cardputer hacking-gadget scene, and multi-radio offensive tooling consolidated into menu-driven Python. Its value is portability and breadth — one device covering wifi, ble, nfc and sub-ghz — with the corresponding responsibility that half its feature set is only lawful against infrastructure and credentials you are explicitly authorized to test. Read the source, test it in a lab, and it is a capable addition to an authorized wireless assessment kit.

Official project repository for 7h30th3r0n3/Raspyjack.
Download Tool

Educational analysis for authorized security professionals. Use only in controlled, authorized environments.

Sponsored
Share articleFacebookXLinkedIn

Continue exploring

Browse all articles →

0 comentários:

Post a Comment

Note: Only a member of this blog may post a comment.