From ReverseEngineering.wiki
Naming a hash, cipher, checksum or encoding in a stripped binary by the numbers its specification fixes: initial values, round constants, S-boxes, magic strings and loop shapes, with the bytes to search in memory for MD5, SHA-1/2, CRC-32, AES, ChaCha/Salsa, Blowfish, TEA, RC4 and Base64.
Overview
Almost every cryptographic primitive, hash and checksum has numbers that its specification fixes: initial values, round constants, S-boxes, lookup tables, magic strings. A compiler and linker keep them, so they are the fastest way to name an algorithm in a stripped binary, before any decompilation. Scanners such as signsrch, findcrypt (Ghidra/IDA/YARA), capa and Detect It Easy are lists of these constants. This page lists the ones that matter, with the bytes to search as they sit in memory on a little-endian CPU (x86, x64, ARM LE) and where each value comes from.
How to search
- Search for the first 8-16 bytes of the table in both byte orders: the little-endian dump of the 32-bit words, and the big-endian one (many MIPS, PowerPC and SPARC builds, and code that stores words in network order).
- A hit proves the table, not its use: confirm by finding a loop that reads it (cross-references to the table address) and a round count that fits (10/12/14 for AES, 64 for SHA-256, 80 for SHA-1, 16 for Blowfish, 32 cycles for TEA).
- Constants may be absent: implementations may compute them at start-up (Mbed TLS builds its AES tables in a function, see Library:Mbed TLS), unroll them as 32-bit immediates in code (MD5 and SHA compress functions usually do), or use CPU instructions (
aesenc, aesdec, aeskeygenassist, sha256rnds2, sha1rnds4, ARM crypto extensions). Search the code for immediates (add eax, 0xD76AA478 stores the constant little-endian after the opcode) and for the instructions.
- Compare with the libraries first: Library:OpenSSL, Library:Mbed TLS and others carry the same constants. A constant hit inside a known library's address range means the library, not a custom cipher.
Hashes and checksums
| Algorithm |
Constant to search |
Bytes in memory (little-endian) |
Notes
|
| MD5 |
initial state 0x67452301 0xEFCDAB89 0x98BADCFE 0x10325476 |
01 23 45 67 89 AB CD EF FE DC BA 98 76 54 32 10 |
the same four words start SHA-1 (plus 0xC3D2E1F0) and RIPEMD-128/160
|
| MD5 |
sine table K[i] = floor(2^32 x abs(sin(i+1))): 0xD76AA478 0xE8C7B756 0x242070DB 0xC1BDCEEE |
78 A4 6A D7 56 B7 C7 E8 DB 70 20 24 EE CE BD C1 |
64 entries; often immediates in the code, not a table
|
| SHA-1 |
init as MD5 + 0xC3D2E1F0; round constants 0x5A827999 0x6ED9EBA1 0x8F1BBCDC 0xCA62C1D6 |
99 79 82 5A A1 EB D9 6E DC BC 1B 8F D6 C1 62 CA |
80 rounds, 4 stages of 20
|
| SHA-256 |
init 0x6A09E667 0xBB67AE85 0x3C6EF372 0xA54FF53A 0x510E527F 0x9B05688C 0x1F83D9AB 0x5BE0CD19 |
67 E6 09 6A 85 AE 67 BB 72 F3 6E 3C 3A F5 4F A5 |
fractional parts of the square roots of the first 8 primes
|
| SHA-256 |
round constants K[64] 0x428A2F98 0x71374491 0xB5C0FBCF 0xE9B5DBA5 |
98 2F 8A 42 91 44 37 71 CF FB C0 B5 A5 DB B5 E9 |
cube roots of the first 64 primes; SHA-224 uses the same K with init 0xC1059ED8 0x367CD507 0x3070DD17 0xF70E5939
|
| SHA-512 |
init 0x6A09E667F3BCC908 0xBB67AE8584CAA73B; K[80] starts 0x428A2F98D728AE22 0x7137449123EF65CD |
08 C9 BC F3 67 E6 09 6A 3B A7 CA 84 85 AE 67 BB |
SHA-384 uses other init words (0xCBBB9D5DC1059ED8 first); BLAKE2b starts from the same IV as SHA-512
|
| CRC-32 (zlib, PNG, ZIP, Ethernet; reflected) |
polynomial 0xEDB88320; table 0x00000000 0x77073096 0xEE0E612C 0x990951BA |
00 00 00 00 96 30 07 77 2C 61 0E EE BA 51 09 99 |
256 words; table-less code is shr 1 / xor 0xEDB88320 in a loop of 8
|
| CRC-32 non-reflected (bzip2, MPEG-2, POSIX cksum) |
polynomial 0x04C11DB7; table 0x00000000 0x04C11DB7 0x09823B6E 0x0D4326D9 |
00 00 00 00 B7 1D C1 04 6E 3B 82 09 D9 26 43 0D |
see Library:Bzip2
|
CRC-32C (Castagnoli, iSCSI, SSE4.2 crc32, Snappy framing) |
reflected polynomial 0x82F63B78 |
78 3B F6 82 |
Unverified for the table bytes; check against your binary
|
| FNV-1 / FNV-1a (32-bit) |
offset basis 0x811C9DC5, prime 0x01000193 |
C5 9D 1C 81, 93 01 00 01 |
from the capa FNV rule
|
Ciphers
| Algorithm |
Marker |
Bytes / values |
Notes
|
| AES (Rijndael) |
S-box |
63 7C 77 7B F2 6B 6F C5 30 01 67 2B FE D7 AB 76 |
256 bytes; the inverse S-box starts 52 09 6A D5 30 36 A5 38 BF 40 A3 9E 81 F3 D7 FB
|
| AES |
round constants Rcon |
01 02 04 08 10 20 40 80 1B 36 |
0x1B is the GF(2^8) reduction (xtime) and also appears as an immediate in table-less code
|
| AES |
T-tables Te0..Te3 / Td0..Td3 (4 x 1 KB each) |
Te0 begins 0xC66363A5 0xF87C7C84 0xFF777799 0xF67B7B8D (bytes A5 63 63 C6 84 7C 7C F8) |
Unverified in the sources listed here (standard Rijndael tables); table-less implementations compute them
|
| AES (hardware) |
instructions aesenc, aesenclast, aesdec, aesdeclast, aeskeygenassist (and vaes*) |
no constant tables |
capa rules 'encrypt/decrypt data using AES via x86 extensions'
|
| ChaCha20 / Salsa20 |
ASCII constant expand 32-byte k (16-byte keys: expand 16-byte k) |
words 0x61707865 0x3320646E 0x79622D32 0x6B206574 |
the constant row of the 4x4 state; no tables; quarter-round rotations 16, 12, 8, 7 (ChaCha) or 7, 9, 13, 18 (Salsa)
|
| Blowfish |
P-array and S-boxes from the digits of pi: P[0..3] 0x243F6A88 0x85A308D3 0x13198A2E 0x03707344; S1[0] 0xD1310BA6 |
88 6A 3F 24 D3 08 A3 85 2E 8A 19 13 44 73 70 03 |
18 P words + 4 x 256 S-box words = 4168 bytes; 16 rounds
|
| TEA / XTEA / XXTEA |
delta 0x9E3779B9 (2^32 / golden ratio) |
B9 79 37 9E; also seen as sub eax, 0x61C88647 (its two's complement) |
TEA: 32 cycles, decrypt starts with sum = 0xC6EF3720; shifts by 4 and 5; XXTEA derives its rounds from the block length
|
| RC4 |
no constants: a 256-byte state initialised S[i] = i, key schedule j = (j + S[i] + key[i % keylen]) & 255; swap(S[i], S[j]), then PRGA i++; j += S[i]; swap; out = S[(S[i] + S[j]) & 255] |
loop bound 0x100 |
look for the 256-iteration loop with a modulo by the key length and a swap; Windows API forms are SystemFunction032/033
|
| DES |
initial permutation and 8 S-boxes (the YARA set carries DES_sbox, DES_pbox) |
S1 starts 14, 4, 13, 1, 2, 15, 11, 8 |
Unverified here
|
Encodings
| Name |
Marker
|
| Base64 |
the alphabet ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789+/, padding =; URL-safe variant ends -_. Optimised implementations compute it with comparisons (libsodium does) and show no string. Custom alphabets (rotated or shuffled) are a common obfuscation: look for a 64-byte table next to a shr 2, and 0x3F loop.
|
| crypt(3) / scrypt itoa64 |
./0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz
|
| Base58 (Bitcoin) |
123456789ABCDEFGHJKLMNPQRSTUVWXYZabcdefghijkmnopqrstuvwxyz (no 0, O, I, l); Unverified, not in the sources used
|
Tools and rule sets
- capa rules (Apache-2.0), folders data-manipulation/encryption, checksum, hashing: number, bytes and mnemonic features per algorithm.
- Yara-Rules crypto_signatures.yar (GPL-2.0): BLOWFISH, MD5, SHA1, SHA512, SHA2/BLAKE2 IV, TEA, RC6, RIPEMD160, WHIRLPOOL, CRC16/32, DES and big-number rules. findcrypt-yara for Ghidra and IDA wraps similar rules.
- Reference implementations to compare tables with: B-Con crypto-algorithms (public domain: AES, Blowfish, DES, MD5, RC4, SHA-1, SHA-256, Base64), tiny-AES-c (Unlicense), libsodium (ISC).
To name the library rather than the algorithm, start with Technique:Identifying cryptographic libraries (Library:WolfSSL, Library:Libsodium, Library:Crypto++, Library:Windows CNG).
See also
Code & repositories
- https://github.com/B-Con/crypto-algorithms @
cfbde48414baacf51fc7c74f275190881f037d32 · license: CC0-1.0 (declared by the contributor; GitHub's detector did not recognize a license file)
Public-domain reference implementations (AES, Blowfish, DES, MD5, RC4, SHA-1, SHA-256, Base64) to compare constant tables with
Tested on: source read, not run: source only · checked 2026-10-18; last activity 2020-12-28
- https://github.com/kokke/tiny-AES-c @
23856752fbd139da0b8ca6e471a13d5bcc99a08d · license: Unlicense
Small AES implementation with sbox, inverse sbox and Rcon tables
Tested on: source read, not run: source only · checked 2026-10-18; last activity 2024-10-04
- https://github.com/mandiant/capa-rules @
42cbfd4da94b9b9f305451242ce7444865c54840 · license: Apache-2.0
capa rules with number/bytes/mnemonic features for crypto, checksum and hashing algorithms
Tested on: source read, not run: source only · checked 2026-10-18; last activity 2026-10-16
- https://github.com/Yara-Rules/rules @
0f93570194a80d2f2032869055808b0ddcdfb360 · license: GPL-2.0-only (declared by the contributor for the files used; GitHub reports GPL-2.0 for the repository)
YARA rule collection incl. crypto/crypto_signatures.yar constant rules (GPL-2.0: facts only taken)
Tested on: source read, not run: source only · checked 2026-10-18; last activity 2024-04-17
- https://github.com/jedisct1/libsodium @
60b751cd14418fae2d17e6f1003e43622b3e5a25 · license: ISC (declared by the contributor; GitHub's detector did not recognize LICENSE)
libsodium: SHA-2 constants, ChaCha/Salsa constant row, constant-time Base64
Tested on: source read, not run: source only · checked 2026-10-18; last activity 2026-10-15; Note: the latest release ships binaries; the wiki links only the source, never the binaries
Pitfalls
- Shared constants: 0x67452301... start MD4, MD5, SHA-1 and RIPEMD; 0x6A09E667 starts SHA-256, SHA-512 (64-bit form) and BLAKE2. Distinguish by the second table or the round structure.
- Mbed TLS and some embedded builds compute or compress tables; Mbed TLS also holds an ARIA S-box that equals the AES S-box (Fact:Mbed TLS/signature/aria sb2 table).
- A modified constant (one changed byte, custom S-box, different delta) is common in malware, game protection and private file formats: when a table is almost the standard one, diff it against the reference before concluding.
- A CRC-32 hit says little about the product: zlib, PNG and ZIP code all carry it (Library:Zlib).
- Key material (S-boxes seeded with a key, XOR keys) is data of the program, not a constant of the algorithm; do not publish keys of protected content (REWiki:Content policy).
Open questions
- Unverified: the byte lists for the AES T-tables, DES, CRC-32C and Base58 were written from the standards and not diffed against a reference build here. A later agent should confirm them with a compiled reference and update the rows.