network-credential-cracking
Crack hashes and handshakes captured during an engagement — identify the format, pick the right hashcat/john mode, and run wordlist + rules. Load when you've recovered a hash, ticket, or handshake and need the plaintext. Signals: bcrypt $2b$/PBKDF2/sha512crypt $6$, NTLM/NetNTLMv2, Kerberos $krb5tgs$
v2026.10.14-ee0e0c53 instalaciones+3 en 7 días27 EstrellasMITsincronizado hace 22 horas
Instalar
¿Aún no tienes la CLI de NotHoly? Instálala primero.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install noorqureshi/network-credential-crackingEscribe en ~/.notholy/skills después de comprobar la firma y el SHA-256.
FirmaFirmado, ed25519
Paquete3ef4a27b…ab997e96
3ef4a27befcb…0b91ab997e961 archivo · 2.1 KBEscaneoBajosin hallazgos
Fuentegithub.com/NoorQureshi/security-skills/tree/main/skills/network/network-credential-cracking@ee0e0c5
Esta entrada todavía no está escrita en tu idioma, así que aparece en English.
En esta página
When it applies
You've captured something crackable — an application DB hash, a Windows NTLM/NetNTLMv2 hash, a
Kerberos ticket (ad-kerberoasting), or a WPA2 handshake — and the plaintext unlocks the next step
(login, lateral movement, privesc). This is the offline counterpart to network-password-spraying.
Why it works
Most stored credentials are one-way hashes, but users pick guessable passwords and many hash schemes are fast to compute. Given the format, you brute the hash offline against a wordlist (optionally mutated by rules) at millions/billions of guesses per second — no lockout, no network.
Method
Identify the format first — this is the whole game.
hashid/haition the sample, and look at the shape:$2b$= bcrypt,$6$= sha512crypt,$argon2= Argon2,pbkdf2:sha256:...= Werkzeug PBKDF2,$krb5tgs$= Kerberoast,$krb5asrep$= AS-REP. A wrong mode wastes hours.Map to the mode:
Hash hashcat -mMD5 / SHA1 / SHA-256 (raw) 0 / 100 / 1400 bcrypt ( $2*$)3200 sha512crypt ( $6$)1800 NTLM 1000 NetNTLMv2 (responder capture) 5600 Kerberoast TGS-REP 13100 AS-REP roast 18200 Werkzeug PBKDF2-SHA256 10900 WPA/WPA2 (hcxtools .22000)22000 Extract a hash from a protected file when the "hash" is a locked artifact, then crack that:
ssh2john id_rsa,zip2john f.zip,rar2john f.rar,keepass2john db.kdbx,office2john doc.docx,pdf2john f.pdf,pfx2john cert.pfx→ feed the output to john/hashcat. An encrypted SSH key, Office doc, KeePass DB, or ZIP found on a target is often the fastest win.Run wordlist + rules:
hashcat -m <mode> hashes.txt rockyou.txt -r rules/best64.rule(start withbest64, escalate toOneRuleToRuleThemAll). Add target-specific words (company, seasons, app names) to the wordlist — context beats a bigger dictionary. Build one withcewl <url> -m5(words from the site),crunch(patterns), orusername-anarchy(name → username permutations).Mask/brute only when the keyspace is small or a pattern is known:
hashcat -m <mode> hashes.txt -a 3 '?u?l?l?l?l?d?d!'.Reuse and pivot — a cracked password is worth spraying elsewhere (
network-password-spraying) and checking for reuse across accounts/services.
Gotchas
- Slow hashes (bcrypt/Argon2/sha512crypt) — a good rule + targeted wordlist beats raw brute; don't waste days masking a bcrypt.
- Format ambiguity — a 32-hex could be raw MD5 or NTLM; try the likely context (Windows → NTLM).
- Kerberoast/AS-REP must be captured in hashcat's exact
$krb5*$format — use Impacket/Rubeus output verbatim. - WPA2 is
-m 22000now (the old-m 2500 .hccapxis deprecated) — convert withhcxpcapngtool. - Handle cracked creds like live secrets — keep them in the git-ignored
engagements/tree; the report shows that a weak password existed, not a wall of plaintext.
Verify success
A recovered plaintext that authenticates against the intended service, or that demonstrably matches the captured hash — the concrete lead for the next step.
References
hashcat mode reference & rule sets; John the Ripper; hcxtools; MITRE ATT&CK T1110.002.
Online counterpart: network-password-spraying.
Archivos de esta versión
- SKILL.md4.0 KB
Permisos
| Permiso | Declarado | Hallado en el escaneo |
|---|---|---|
| Lee archivos | No | No |
| Escribe archivos | Sí | Sí |
| Ejecuta comandos de shell | No | No |
| Usa la red | No | No |
| Usa conectores | No | No |
| Controla un navegador | No | No |
Hallazgos del escaneo
Revisado el 13 nov 2026
El escaneo no encontró nada que señalar en esta versión.
Un escaneo limpio baja el riesgo, pero no prueba que el paquete sea seguro. Lee lo que instalas.
| Versión | Publicada | Commit | SHA-256 | Firma | Cambio de permisos |
|---|---|---|---|---|---|
| v2026.10.14-ee0e0c5 | 13 nov 2026 | ee0e0c5 | 3ef4a27b | Firmada | – |
Más de NoorQureshi
Todo de este publicadorMás en Red, wireless y telecom
Ver la categoría- performing-network-packet-capture-analysismukul975/performing-network-packet-capture-analysis4
- network-segmentation-reviewsecurityskills/network-segmentation-review3
- performing-ssl-stripping-attackmukul975/performing-ssl-stripping-attack3
- implementing-next-generation-firewall-with-palo-altomukul975/implementing-next-generation-firewall-with-palo-alto3
- configuring-zscaler-private-access-for-ztnamukul975/configuring-zscaler-private-access-for-ztna3
- implementing-canary-tokens-for-network-intrusionmukul975/implementing-canary-tokens-for-network-intrusion3
Pregunta todo lo que tu alcance permite.
Crea la cuenta, añade créditos y haz la primera pregunta en el chat o en la terminal.
- 1/3
Crea la cuenta
Individual o empresa. Puedes pasar a empresa después sin perder saldo ni claves.
IndividualEmpresa - 2/3
Añade créditos
Con tarjeta. Pagas por token, sin suscripción.
$5.00recarga mínima - 3/3
Pregunta
En el chat, o instala el CLI y ejecuta notholy login en tu terminal.
$ notholy login