hcxtools
2026-10-03 open-sourceThe section your link pointed to isn't on hcxtools's page any more, so we've brought you to the top.
hcxtools converts packets from capture files to hash files for use with Hashcat or John the Ripper.
hcxeiutool -i rockyou.txt -d digits.txt -x hexdigits.txt -c alpha.txt -s cswords.txt meson setup build -Dcurl=disabled -Dopenssl=disabled -Dzlib=enabled hcxpsktool --genpattern -o candidates.txt wpa_supplicant.conf $ hcxeiutool -i elist -d digitlist -x xdigitlist -c charlist -s sclist hcxessidtool --pmkid1=file1.16800 --pmkid2=file2.16800 --pmkidout12=joint.16800 hcxessidtool --pmkid1=file1.16800 -l 10 --pmkidout=filtered.16800 whoismac -e default
Summary
hcxtools is an open-source command-line toolset, free to use, that converts WiFi packet capturespacket capturesA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic. (pcappcapA packet capture, recorded network packets that can be inspected later. Analysts use it to reconstruct communication and investigate protocol behavior or suspicious traffic., pcapng, cap) into hash formats readable by Hashcat and John the Ripper, letting someone check whether a WPAWPAA Wi-Fi authentication and encryption standard maintained by the Wi-Fi Alliance, replacing WEP; cyber tools target it to audit wireless network credentials and key exchange handshakes./WPA2 key or PMK was transmitted unencrypted. It targets people auditing their own wireless networks rather than general pentesters, and it is explicit about scope: it does not crack WPA PSKs, WEP, or WPS itself, and it does not decrypt traffic, deferring those jobs to Hashcat, JtR, aircrack-ng, Reaver, Bully, or Wireshark, which places it as a conversion and filtering step feeding into those tools rather than a competitor to any of them. It runs on Linux only, with no Windows, macOS, or Android support. First committed in 2017, it has 39 contributors and 137 commits in the past year, with its most recent release about six months ago.
hcxtools converts packets from capture files to hash files for use with Hashcat or John the Ripper.
How hcxtools helps
Was the WPA/WPA2 key or PMK for this network ever sent unencrypted?
converts the capture into the WPA-PBKDF2-PMKID+EAPOL hash format and lets that hash be checked, showing whether the key material appeared in the traffic rather than staying protected
Which of the hashes pulled from a capture are actually worth feeding to a cracking run?
filters the converted hash file down by user-specified criteria, so only the entries that meet those conditions carry forward
Is my access point or a connected client using a weak or guessable password?
produces the hash formats that Hashcat or John the Ripper accept, or the raw capture that can be submitted to an online password-recovery service, so the weakness check happens in those tools rather than here
Is this dump file too large to hand off conveniently?
writes its output with single-file gzip compression so the converted hash file can be stored or transferred compressed
Languages
Command line
No command matches.
| option | found in | since | description |
|---|
Values are placeholders taken from each option’s declared default. Nothing is executed here — the output shown is a recording of a run that already happened.
Score card
-
Shipping velocity releases a month, last 12 months
-
Documentation quality release-notes rubric, 0–100
-
Breaking-change discipline how rarely a release breaks users, and notice given
-
Maintenance risk quiet time against its own cadence, maintainers
-
Innovation & surface new capabilities, API and MCP surface
- Community health
-
Contributor trend distinct committers, this year against last
-
Maintainer concentration bus factor now against a year ago
-
Issue backlog trend issues closed per issue opened, 12 months
-
Responsiveness median time to a maintainer’s first reply
Nine scores for hcxtools, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.
Score cards are part of every paid plan.
See plans → Already subscribed? Sign in →Trajectory
Blank means never measured; nothing here is a filled-in zero.
Peer standings are included with Researcher and Business. See how this tool ranks against its competitors, using data we don't publish anywhere else.
See plans →Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.
How this is scored
- Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
- Documentation quality — the release-notes rubric published on the analytics page, unchanged.
- Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
- Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
- Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
- Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
- Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
- Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.
Release-note detail over time
See how much detail hcxtools puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.
Checking release-note history…
Releases
54 entries
No entries match these filters.
- October 20264
- August 20261
- March 20261
- January 20262
- February 20251
- January 20241
- December 20231
- November 20231
- May 20231
- December 20221
- September 20211
- August 20212
- March 20211
- February 20211
- December 20201
- October 20202
- September 20201
- June 20201
- May 20201
- April 20201
- January 20201
- September 20193
- August 20191
- June 20193
- May 20192
- April 20191
- March 20191
- February 20192
- January 20191
- December 20182
- September 20181
- July 20181
- March 20181
- February 20181
- January 20184
- December 20172
- October 20171
Project health
Issue, contributor and maintainer activity in ZerBea/hcxtools, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.
- Contributors 9 +4 vs prior 12 months
- Maintainers 1 +0 joined · −0 left, last 12 months
- Bus factor 1 committers behind half the commits
- Community-filed 100% of issues opened, last 12 months
- Median time to close < 1 day first maintainer reply 3.1 hours
- Open backlog 1 of 185 issues ever filed
- Issues opened / month 0 · 0 communitymaintainers
- Open backlog 1
- Contributors / month 1
- Commits / month 3
- Stars 2,446
- other 100%
Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this
Libraries its release ships
What its latest release locks, checked against known advisories.None of its release's images build from a lockfile we can read.
Add the badge to your README
Maintain this project? The badge links readers straight to this page, so they can follow every release here.