ThingPulse Pendrive S3

by ThingPulse

Image of Board

The ThingPulse Pendrive S3 is a ESP32-S3 board which fits neatly into a USB pendrive

  • Wi-Fi
  • Bluetooth/BTLE
  • USB-C
  • 128MB Built-In SD-card-like flash memory
  • WS2812B RGB status LED
  • Capacitive touch button
  • Compact Pendrive Enclosure

Applications: BadUSB

Imagine having full control over any computer in seconds, simply by plugging in a device. That’s the power of tools that emulate a USB keyboard. Because computers inherently trust keyboards, these devices can take command with lightning speed.

Meet the Pendrive S3, a device that pretends to be a keyboard, bombarding the computer with hundreds of keystrokes per second—far faster than any human could type. By utilizing a straightforward scripting language, you can program the Pendrive S3 to execute any commands you want.

Now, take this concept to the next level with the Super WiFi Duck. This innovative tool lets you manage all your scripts wirelessly through a user-friendly web interface. No need for app installations, logging in, or tedious script transfers. With the Super WiFi Duck, everything is at your fingertips, making it easier than ever to unleash the full potential of a BadUSB device.



Have some info to add for this board? Edit the source for this page here.

Absolute Newest

Every time we commit new code to CircuitPython we automatically build binaries for each board and language. The binaries are stored on Amazon S3, organized by board, and then by language. These releases are even newer than the development release listed above. Try them if you want the absolute latest and are feeling daring or want to see if a problem has been fixed.

Previous Versions of CircuitPython

All previous releases of CircuitPython are available for download from Amazon S3 through the button below. For very old releases, look in the OLD/ folder for each board. Release notes for each release are available at GitHub button below.

Older releases are useful for testing if you something appears to be broken in a newer release but used to work, or if you have older code that depends on features only available in an older release. Otherwise we recommend using the latest stable release.