National Cyber Warfare Foundation (NCWF)login

Raw 802.11 frame injection on ESP32 with esp-idf-injection-ng


0 user ratings
2026-11-10 23:31:04
milo
Red Team (CNA)
"Raw

esp-idf-injection-ng restores raw 802.11 frame transmission on modern ESP-IDF builds via a single objcopy patch, enabling authorized wireless research on ESP32 hardware.








Toolmahdamin/esp-idf-injection-ng — enables raw 802.11 frame injection on ESP-IDF v5+/v6+ through a one-command objcopy --weaken-symbol patch
CategoryWireless / embedded security tooling for ESP32
Primary UseRestoring access to esp_wifi_80211_tx() on ESP-IDF v5+/v6+ to transmit Authentication (SAE Commit), Deauth, Reassociation, Disassociation and Control (RTS/CTS/ACK) frames in authorized lab environments
Safe UseIntended for authorized wireless security assessments, isolated lab networks, protocol research, and defensive validation of 802.11 resilience on equipment you own or have written permission to test
Telemetry NoteInjected management and control frames are observable by wireless intrusion detection systems as anomalous deauth/disassoc bursts, malformed SAE exchanges, or unsolicited RTS/CTS sequences; enterprise WIPS platforms correlate these as deauth-flood and injection signatures

mahdamin/esp-idf-injection-ng is a small but consequential piece of ESP32 tooling: it re-enables raw 802.11 frame transmission on firmware built against ESP-IDF v5+ and v6+, a capability that Espressif progressively made harder to reach in the component's default symbol visibility. The project's core trick is a one-command objcopy --weaken-symbol patch applied to the compiled wifi library, which demotes the internal symbol guarding esp_wifi_80211_tx() from a strongly-bound local definition into a weak one that application code can reference directly. The result is that a researcher working with a stock ESP32 or ESP32-S3 can transmit arbitrary management and control frames without maintaining a fork of the entire ESP-IDF tree, which is the maintenance burden that historically killed most injection projects on this platform.


The context available for this repo is unusually thin — the repository description and the curator summary carry essentially all of the substantive information, and the kitploit page content surfaced in the context is broken Next.js hydration payload rather than readable article text, so it contributes nothing beyond what the repo metadata already states. What we can confirm from the metadata is solid, though: sixty stars, C as the language, an MIT license, and a topic list spanning 802-11, esp-idf, esp32, esp32-s3, ieee80211, injection-attacks, marauders, reverse-engineering, and wifi-security. The marauders topic is a deliberate signal — it references the ESP32 Marauder ecosystem, the well-known flipper-adjacent wireless toolkit whose functionality depends on precisely this kind of low-level transmit primitive.


Mechanically, the approach deserves attention because of how little it disturbs. Traditionally, getting esp_wifi_80211_tx() usable meant either patching the ESP-IDF source and rebuilding the whole framework, or relying on older ESP-IDF v4.x releases where the symbol was more accessible. Weakening the symbol post-compilation via objcopy sidesteps both paths: you keep an unmodified, current ESP-IDF v5+/v6+ installation, apply the patch as a build step, and the linker then resolves your application's calls against the weakened symbol rather than rejecting the reference. This matters operationally for anyone maintaining long-lived research firmware, because ESP-IDF majors carry breaking changes and staying on v4.x for injection support means inheriting stale Wi-Fi stack fixes and eventual incompatibility with newer toolchains.


The frame types enumerated in the project description map cleanly onto the standard 802.11 attack-and-research surface: Authentication frames including SAE Commit constructs, Deauthentication, Reassociation and Disassociation frames, and control frames such as RTS, CTS, and ACK. In an authorized context, each of these has a legitimate research role. SAE Commit transmission lets researchers study WPA3 handshake behavior, including how clients and APs respond to malformed or out-of-order SAE exchanges — relevant to the class of WPA3 downgrade and DoS issues documented in the literature. Disassociation and reassociation frames let teams validate that their wireless infrastructure and client fleet behave correctly and recover gracefully under management-frame stress, once protected-management-frame (PMF) handling is examined. RTS/CTS/ACK injection supports lower-layer experiments around channel occupancy, clear-channel-assessment behavior, and rate adaptation that are simply not possible from a monitor-mode host adapter alone.


It is worth stating the obvious dual-use reality plainly: deauth and disassoc transmission is one of the most abused primitives in opportunistic wireless mischief, and it is also entirely ineffective against properly deployed PMF/802.11w networks. This tool is positioned for people who need the primitive for legitimate work — protocol conformance probing, captive-lab resilience testing, demonstrating to stakeholders why management frame protection matters, and building detection datasets for wireless intrusion systems. Anyone using it against infrastructure they do not own is both outside its authorized scope and, in most jurisdictions, on the wrong side of computer misuse and radio regulations. ESP32 devices are unlicensed transmitters operating under FCC/regional ISM rules, and transmitting deliberately crafted 802.11 frames on networks you do not administer carries legal exposure independent of intent.


The defensive angle is arguably the more interesting one. WIPS and enterprise wireless monitoring platforms (Cisco, Aruba, Extreme, and open-source Kismet-based deployments) already fingerprint deauth floods, unsolicited SAE frames, and anomalous RTS/CTS bursts. Cheap ESP32-based injection lowers the barrier for noise on the spectrum, which paradoxically strengthens the case for blue teams: if your organization's monitoring cannot correlate and alert on a $5 microcontroller emitting management frames, it will not catch a determined adversary either. Labs building detection content can use tooling like this — under controlled conditions — to generate the exact traffic classes their WIPS rules claim to catch, and validate tuning empirically rather than on vendor assertions.


From an engineering-architecture standpoint, the objcopy --weaken-symbol technique is also a nice case study in binary-level intervention as a minimal-diff alternative to source patching. The same pattern generalizes: any static library where an internal symbol blocks access to a useful function can, in principle, be adjusted at the object level and reintegrated as a pre-build step, keeping the upstream dependency pristine and the patch auditable as a single line in a build script. For teams building marauders-style tooling or custom 802.11 research firmware on ESP32-S3, that auditability is the practical selling point — one command to review, one artifact diff, and full compatibility with current ESP-IDF releases rather than a fork frozen in time.


Given how sparse the repository's own documentation in the context is, the honest assessment is that this is a capability-enabling shim rather than a full toolkit: it gives you the transmit primitive, and what you build on top — frame constructors, channel hopping, sequencing logic — is your own work. That narrow scope is a feature. It keeps the maintenance surface tiny, tracks ESP-IDF releases closely, and stays out of the business of shipping higher-level attack workflows, which is consistent with its research-oriented framing. Expect the practical setup to follow standard ESP-IDF patterns — an idf.py project with the patch wired into the build — and verify the exact objcopy invocation against the repo before integrating, since symbol names in the wifi library have shifted across ESP-IDF minors.


For the right audience — wireless researchers, embedded security engineers, WIPS detection developers, and educators teaching 802.11 internals on hardware students already own — esp-idf-injection-ng removes the single most annoying obstacle in the ESP32 wireless research pipeline. It is not a scanner, not a suite, and not a weapon; it is a key to a door Espressif deliberately leaves locked, and like any such key it belongs in authorized hands operating in isolated lab RF environments. Sixty stars is modest, but the repo topics and the ESP32-S3 support suggest an active niche, and anyone maintaining marauders-adjacent firmware on current ESP-IDF will want to bookmark it.



Official project repository for mahdamin/esp-idf-injection-ng.

Download Tool

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






Source: OffensiveSec
Source Link: https://www.offsecblog.com/2026/11/raw-80211-frame-injection-on-esp32-with.html


Comments
new comment
Nobody has commented yet. Will you be the first?
 
Forum
Red Team (CNA)



Copyright 2012 through 2026 - National Cyber Warfare Foundation - All rights reserved worldwide.