JA4 Fingerprinting
Also called JA4, JA4+.
A newer, more resilient family of network traffic fingerprints.
What it is
A successor to JA3 that produces more structured, human-readable fingerprints of TLS and other protocol behavior, with a family of related hashes covering clients, servers, HTTP, and more. It was designed to resist the trivial evasion that plagued older hashes.
Why it matters
Adversaries learned to randomize handshake order to defeat JA3, so the more resilient and granular JA4 fingerprints help analysts keep tracking tooling across encrypted sessions.
In practice
Correlating two seemingly unrelated infections after both exhibited the same JA4 fingerprint, pointing to a shared toolkit.
What to look for
- JA4 client fingerprints tied to scanners or implants.
- JA4S and JA4H for server and HTTP views.
- Fingerprints that stay stable when extension order changes.
Common mistake
Treating a fingerprint as proof of a family. It narrows things down; confirm with other evidence.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Wireshark Open source
Opens a capture packet by packet so you can see exactly what crossed the wire. Our notes.
-
Zeek Open source
Turns traffic into structured logs for connections, DNS, HTTP, TLS and more. Our notes.
-
Suricata Open source
An IDS that alerts on known patterns and logs protocol metadata alongside. Our notes.
-
Arkime Open source
Indexes full packet capture at scale so you can search and pull sessions later. Our notes.
Read next
- JA3 Fingerprinting: Hashing TLS handshake fields to fingerprint the client software.
- Encrypted Traffic Analysis: Inferring intent from encrypted traffic's shape and metadata.
- Malleable C2 Profile: A config that reshapes C2 traffic to mimic benign protocols.