
Payload injector and HID emulator for Android like Hak5 and rubber ducky
Hardware Emulation & Proximity Exploitation
Hak5 gear is heavy and obvious. My phone has a full Linux kernel in it, so I made it do the same job — HID emulation, RNDIS, mass storage, the whole thing — straight through ConfigFS. No extra hardware. No cables dangling out of a bag.
Plug into a target, pick a payload, run it. Keystrokes go to /dev/hidg0 directly. Nothing in between.
/dev/hidg0. Fast, and most EDRs see it as a generic keyboard..txt files from local storage or pull directly from the Hak5 community repo inside the app.usb0) and runs a tiny web server for swapping payloads or checking status from another machine. Windows picks it up automatically. macOS is annoying about composite USB signatures, fair warning..bin or .img to usb_f_mass_storage. Phone shows up as a flash drive on the target.Kotlin frontend, C++ for anything that touches hardware.
sysfs directly to figure out what the kernel actually has compiled inNeeds root. That's the hard requirement.
CONFIG_USB_CONFIGFS and CONFIG_USB_CONFIGFS_F_HID. Stock kernels usually don't have them. Flash NetHunter if yours doesn't.BT HID works reliably across most devices. Wired ConfigFS is a different story — it depends entirely on what your OEM left in the kernel. If you get it working on something unusual (old Pixel, OnePlus, whatever), paste your
dmesgoutput in the Issues tab. Trying to build a compatibility list.
git clone https://github.com/cipher-attack/chimera.git
cd chimera
# Set NDK path in local.properties first or the JNI build will fail immediately
./gradlew assembleDebug
DELAY 1000 at the top of every payload.DOCUMENTATION.md covers the JNI bridge and the composite USB setup in detail. Read CONTRIBUTING.md and CODE_OF_CONDUCT.md before opening a PR.
Disclaimer: Built for authorized red team and physical security work. Get written permission before you plug into anything.