Hexis
Hexis is a professional, cross-platform hardware pentesting and firmware pentesting framework. It acts as the "Ghidra + Wireshark + Flashrom" of hardware security, providing an end-to-end pipeline from physical flash extraction to binary security analysis.
Features
- Modular Driver Architecture (C23): Native C core engineered for extreme performance with capability-based driver routing and transactional hooks (
CAP_SPI,CAP_UART). - Dual-Format Project System: Store sessions as
.hexisprojdirectories with Content-Addressed Storage (CAS) for firmware deduplication, or export as portable.hexiszip archives. - Session Replay Engine: Logs all read/write/erase interactions to recreate automated hardware pentesting sessions.
- Knowledge Graph & Virtual Filesystem: Maps extracted firmware chunks into a hierarchical VFS and outputs findings to a native graph database structure.
- Event Bus & Job System: Completely asynchronous Pub/Sub backend ensuring the GUI remains perfectly responsive during massive memory dumps.
- Firmware Analysis Engine: Calculate Shannon entropy, parse ELF architectures, and scan for magic filesystem bytes (
SquashFS,uImage, etc.). - Secret & Vulnerability Scanner: Lightning-fast POSIX regex scanner identifying AWS keys, private certificates, and weak crypto markers directly inside firmware blobs.
Building
Requires a Unix-like environment (Linux / macOS / WSL) with CMake, GCC/Clang, Qt6, and libusb-1.0.
mkdir build && cd build
cmake ..
cmake --build .
Quick Start (CLI)
# Detect connected chip
python3 -m hexis.cli detect --driver ch341a
# Read firmware
python3 -m hexis.cli read firmware.bin
# Launch the GUI
./build/gui/hexis-gui
Architecture Overview
Hexis is split into three main layers:
libhexis(C23): The native shared object handling USB communication, chip databases, memory analysis, and plugins.hexis-gui(C++20/Qt6): The graphical dashboard for interactive hardware analysis.hexis(Python): High-level bindings and Typer CLI.
Developed by l3tchupkt / letchu.geek@gmail.com
Metadata
Release files for hexiskit 0.1.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| hexiskit-0.1.2.tar.gz | 37.7 kB | Without provenance | Details for hexiskit-0.1.2.tar.gz |
Release files / hexiskit-0.1.2.tar.gz
| Download URL | hexiskit-0.1.2.tar.gz |
|---|---|
| Size | 37.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6d82059717071e17f0c819b71e62227021ec1bb2c8ff0cd416f5c92af1ce1588
|
|
BLAKE2b-256 checksum How to use checksums |
feefd02478d976bbe3abdbb62fe931a2c42464dd8186332bf3747afd2733cb71
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.12
|
Security for hexiskit 0.1.2
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.