PortaPack Mayhem: a C firmware fork three generations deep
The firmware for the HackRF+PortaPack H1/H2/H4/H4M
At a glance
- What is it?
- Mayhem is the firmware behind the HackRF plus PortaPack H1, H2, H4 and H4M, forked from Havoc and from PortaPack before it. It ships nightly tags, a containerized Alpine build, and buying advice that spends more words on seller compatibility than on compiling anything.
- Who is it for?
- Mayhem is a reasonable choice if you own HackRF hardware, can accept a firmware line that moves nightly, and read the release description before flashing. It is a poor fit if you need a build process spelled out in the repository, a list of supported models, or hardware bought from a seller who ships a private firmware recipe.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 1 day ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- portapack-mayhem/mayhem-firmware5,540 ★ · +119
| Repository | 2026-09-23 | 2026-11-15 |
|---|---|---|
| portapack-mayhem/mayhem-firmware | 5.4k | 5.5k |
119 Stars in the last 53 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
Three forks deep, and the branch that builds by default
Mayhem sits at the end of a fork chain. The PortaPack firmware by sharebrained is an add-on for the HackRF radio. Havoc forked that, and Mayhem forked Havoc, adding features and fixes on top of both. The code is C under GPL-3.0, and the repository summary names the hardware it targets as the HackRF plus PortaPack H1, H2, H4 and H4M.
Two details matter before you clone anything. The default branch is next, so a plain checkout lands on the development line rather than on a settled one. And the last push on 2026-11-01 arrived alongside three nightly tags inside the same week: nightly-tag-2026-10-29, nightly-tag-2026-10-30 and nightly-tag-2026-11-01.
The releases page is the install path, not the source tree
Installing Mayhem is a download, not a build. The stable build is the one behind the releases/latest link, and the instruction to follow sits in that release's own description, which means the flashing procedure travels with the build instead of living in the repository. Nightly builds are listed one page over on the releases index, and the tag names carry their dates.
The tree does hold the machinery around that step. There is a flashing/ directory for writing to hardware, a docker-compose.yml at the root, five dockerfile variants, dockerize.sh and a scripts/ directory, all of which cover building rather than installing. A prebuilt container image is also published under the eried/portapack repository on the Docker Hub, and the project homepage is hackrf.app, where the shortened purchase links in the buying section resolve.
The compose file builds against Alpine and mounts one output folder
Building happens inside a container defined at the repository root:
version: '3.9'
services:
portapack-mayhem-dev:
build:
context: .
dockerfile: dockerfile-alpine
volumes:
- "./bin:/havocbin"The service is named portapack-mayhem-dev, it builds from the dockerfile-alpine file in the same directory, and it mounts a local bin folder at /havocbin so compiled output outlives the container. The file names describe the variants: dockerfile-nogit, dockerfile-nogit-alpine and dockerfile-nogit-arm cover builds without repository history or for a different architecture, and docker-compose-nogit.yml pairs with them. The rest of the root is housekeeping: CMakeLists.txt as the build entry, .clang-format with format-code.sh and format-code.ps1 for the two shell families, and directories for firmware/, hardware/, mbt/, sdcard/, tools/, docs/ and hackrf.
The buying advice spends more words on the seller than the radio
The purchase section is the longest part of the README, and most of it is about who you buy from rather than what you get. Two units are endorsed. The H4M is offered as a complete kit or an upgrade, described as carrying improvements and accessories, sold by OpenSourceSDRLab, with Lab401 named as the route for customers in the EU. The PortaPack H2 is called the recommended one because it includes everything needed along with a plastic case inspired by the 3d-printed-enclosure page in the wiki.
A metal enclosure version of the H2 gets its own line with the advantages left open, and the wiki hardware overview is named as the place where that argument continues. The rest of the section is a compatibility check to run before paying: ask the seller whether the unit supports the latest releases.
Hardware running a private recipe stays unmaintained
The failure the README warns about twice is a device that nobody maintains afterwards. Its advice is to read the listing closely: if the seller provides firmware files for an older version or attaches custom setup instructions, the unit might not be compatible with what you are trying to run. If the listing looks too different from what you expected, the likely reason is that the seller is running their own recipe rather than the current line.
The named example is the H3 and the clones of that version. Those units use their own version of the firmware, they do not contribute the changes back, and the result is exactly the situation the section is warning against: hardware that runs, that nobody tracks upstream, and that you have to maintain alone. The same page points at a PortaPack versions entry in the wiki to compare models before buying.
The FAQ heading answers none of the usual questions
Under a heading called Frequently Asked Questions, the README moves straight into buying advice, then into where the latest version lives, how to collaborate, and where to get help. It never lists the applications, never gives the compile steps, and never names which models the current build supports beyond the H1, H2, H4 and H4M named in the repository summary.
The missing parts live in the wiki: Contributing Guidelines, a how to collaborate guide, a hardware overview, and a PortaPack versions page. Reading order matters, then, because the repository answers the shopping question and leaves the working question to the wiki. Two things at the root are worth knowing about as a contributor rather than a user. There is an AGENT.md file that the README points coding agents at, sitting beside CONTRIBUTING.md, CODE_OF_CONDUCT.md and SECURITY.md, and there is an editor configuration in .vscode/ for people who work on the firmware in place.
Feature requests go through a labelled issue template
Two routes exist for anything the firmware is missing. A request that makes sense to more than one person belongs in an issue opened from the 02_feature_request.yml template with the enhancement label applied, and anything more open ended gets discussed on the Discord linked from the badge row at the top. Bugs travel the same way through the issue chooser, and the wiki documentation pages are open contributions in their own right.
The README also asks that effort go into collaborating with the people already there first, on the grounds that the hardware and the firmware were built by a long list of contributors, and it closes the money question by asking readers to buy a genuine HackRF and PortaPack rather than a clone. The badges above that text point at the nightly release workflow, the release index, the code scene project and the community server.
Editorial conclusion
Mayhem is a reasonable choice if you own HackRF hardware, can accept a firmware line that moves nightly, and read the release description before flashing. It is a poor fit if you need a build process spelled out in the repository, a list of supported models, or hardware bought from a seller who ships a private firmware recipe. Check which branch and which tag you are on, confirm the seller supports the current release, and read what GPL-3.0 asks of anything you distribute.
Frequently asked questions
What is Mayhem firmware?
It is the C firmware for the HackRF plus PortaPack H1, H2, H4 and H4M, released under GPL-3.0. It is a fork of the Havoc firmware, which was itself a fork of the sharebrained PortaPack firmware, an add-on for the HackRF. The default branch is next, and the last push was 2026-11-01.
How to install Mayhem firmware?
Take the stable build from the releases/latest page and follow the instructions written in that release's own description, since the flashing steps travel with the build. Nightly builds are listed on the releases index under dated tags such as nightly-tag-2026-11-01. The repository keeps a flashing/ directory and the docker files for building, while the written procedure sits in the release description.
What does Mayhem firmware do?
It extends earlier PortaPack work with new features, bugfixes and documentation meant to make further development easier. Alongside the stable release the project publishes nightly tagged builds, and its homepage is hackrf.app, which is where the shortened purchase links in the README lead.
Is a firmware update necessary for Mayhem?
Ask the seller before buying and treat older firmware files or custom setup instructions as a warning that the unit may not match the current releases. Hardware running someone else's recipe, such as the H3 and its clones, does not contribute changes back, so you end up owning a device that nobody maintains.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/portapack-mayhem-mayhem-firmware)Star history chart for your README
[](https://hysenlabs.com/projects/portapack-mayhem-mayhem-firmware)Was this useful?