tools-hashcat
Crack password hashes offline with hashcat (GPU) and John the Ripper (CPU) — hash-mode selection, attack modes (straight/mask/combinator/rules), the -m type table, *2john extractors, and potfile discipline. Load when loot includes hashes: NTLM/NetNTLMv2 dumps, Kerberos TGS (kerberoast), JWT secrets,
v2026.10.14-ee0e0c53 instalações+3 em 7 dias27 EstrelasMITsincronizado há 22 horas
Instalar
Ainda não tem a CLI da NotHoly? Instale primeiro.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/tools-hashcatGrava em ~/.notholy/skills depois de conferir a assinatura e o SHA-256.
AssinaturaAssinado, ed25519
Pacotef079a04d…c5987fa7
f079a04df043…ef89c5987fa71 arquivo · 2.5 KBVarreduraBaixo1 achado
- Links para domínios externos
Fontegithub.com/NoorQureshi/security-skills/tree/main/skills/tools/tools-hashcat@ee0e0c5
Este item ainda não foi escrito no seu idioma, então aparece em English.
Nesta página
When it applies
You hold in-scope credential material (tradecraft-scope-roe) that must be proven crackable: NTLM
dumps, NetNTLMv2 captures (network-credential-cracking), Kerberos TGS tickets (ad-kerberoasting),
JWT HMAC secrets (web-auth-jwt), /etc/shadow, or password-protected archives/keys. In defense
mode, the same workflow audits whether org passwords survive a real cracking run.
Why it works
Offline cracking has no lockout and no rate limit — speed is set by hash algorithm and hardware.
hashcat drives GPUs (billions of guesses/sec on fast hashes like NTLM); John the Ripper is the
flexible CPU fallback with extractors (*2john) that turn encrypted files into crackable hashes.
Rules and masks exploit how humans actually pick passwords, so a small wordlist + mutation beats
blind brute force.
Method
- Identify the hash before choosing a mode — wrong
-mwastes the whole run. Usehashid/hashcat --identify hash.txt, or match the format against the table:text -m 0 MD5 -m 1000 NTLM -m 5600 NetNTLMv2 -m 100 SHA1 -m 1800 sha512crypt -m 13100 Kerberos TGS (kerberoast) -m 1400 SHA256 -m 3200 bcrypt -m 16500 JWT (HS256) -m 1700 SHA512 - Straight dictionary first (attack mode
-a 0):hashcat -m 1000 ntlm.txt /usr/share/wordlists/rockyou.txt(Kali:gzip -d /usr/share/wordlists/rockyou.txt.gzonce — ~14M words.) - Add rules — mutations (leet, append digits, capitalize) crack what plain lists miss:
hashcat -m 0 hash.txt wordlist.txt -r rules/best64.rule - Combinator for paired words:
hashcat -m 0 -a 1 hash.txt words1.txt words2.txt. - Mask attack when you know the policy (attack mode
-a 3):hashcat -m 0 -a 3 hash.txt ?u?l?l?l?l?d?d?d(e.g. "5 letters, capital first, 3 digits"). Charsets:?llower,?uupper,?ddigits,?ssymbols,?aall,?b0x00–0xff. - Read results:
hashcat -m 0 hash.txt --show(cracked plaintexts come from the potfile — rerunning the attack skips already-cracked hashes). - John path (CPU, exotic formats):
bash unshadow /etc/passwd /etc/shadow > mypasswd && john --wordlist=rockyou.txt mypasswd zip2john protected.zip > zip.hash && john --wordlist=rockyou.txt zip.hash rar2john protected.rar > rar.hash # same pattern ssh2john id_rsa > ssh.hash # SSH private-key passphrase john --format=raw-md5 --wordlist=rockyou.txt hash.txt # force a format john --incremental hash.txt # pure brute force, last resort john --show hash.txt - Sanity-check hardware:
hashcat -bbenchmarks; if bcrypt (-m 3200) shows tiny rates, that is the algorithm working as designed — switch strategy (better wordlist/rules), not patience.
Gotchas
- Slow hashes are meant to be slow — bcrypt/scrypt/argon make masks above ~7 chars futile; invest in wordlist quality (target-specific lists, breached-corpus lists like the CrackStation 15 GB dictionary) instead of length.
- GPU/driver problems are environmental — no OpenCL/CUDA device = fix drivers or fall back to John; do not grind a mask attack on CPU.
- Potfile confusion —
--showreads the potfile, not the hash file; a "cracked" result that never prints usually means you're--show-ing the wrong-mmode. - Salted vs unsalted — mode choice must match (raw MD5
-m 0vs md5crypt-m 500); a correct password list against the wrong mode cracks nothing and looks like "strong passwords". - Cracked =/= authorized — only crack hashes from in-scope systems; recovered credentials go in
loot/, never in the report body (report the fact and rate of cracking).
Verify success
--show output maps hashes to plaintexts for a stated percentage of the set, and you can name the
mode, wordlist/rules/mask, and runtime — reproducible evidence for the finding ("X% of domain
passwords cracked in N minutes with a commodity GPU").
References
hashcat example-hashes page (mode identification); hashcat wiki (rules/masks); John jumbo docs.
Where hashes come from: network-credential-cracking, ad-kerberoasting, web-auth-jwt.
Portions adapted from reverse-skill by zhaoxuya520, MIT License.
Arquivos desta versão
- SKILL.md4.9 KB
Permissões
| Permissão | Declarada | Encontrada na varredura |
|---|---|---|
| Lê arquivos | Não | Não |
| Grava arquivos | Sim | Sim |
| Roda comandos no shell | Sim | Sim |
| Usa a rede | Sim | Sim |
| Usa conectores | Não | Não |
| Controla um navegador | Não | Não |
Achados da varredura
Revisado em 13 de nov. de 2026
- InfoLink · Links para domínios externos
Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.
| Versão | Publicada em | Commit | SHA-256 | Assinatura | Mudança de permissão |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 de nov. de 2026 | ee0e0c5 | f079a04d | Assinada | – |
Mais de NoorQureshi
Tudo deste publicadorMais em Criptografia e Web3
Ver a categoriaPergunte tudo o que o seu escopo permite.
Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.
- 1/3
Crie a conta
Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.
Pessoa físicaEmpresa - 2/3
Adicione créditos
No cartão. Você paga por token, sem assinatura.
$5.00recarga mínima - 3/3
Pergunte
No chat, ou instale o CLI e rode notholy login no terminal.
$ notholy login