Holy Shuck! Weaponizing NTLM Hashes as a Wordlist #1656
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 Automated Content Update
This PR was automatically generated by the HackTricks News Bot based on a technical blog post.
📝 Source Information
🎯 Content Summary
This post presents hash shucking applied to Active Directory (AD): treating existing NTLM (NT) hashes as a wordlist in Hashcat’s NT-candidate modes to validate password reuse across slower NT-derived formats (Kerberos RC4 tickets, NTLM challenge-responses, DCC/DCC2) without first recovering plaintext passwords.
1. Concept of layered hash shucking
The post first introduces shucking using a generic layered-hash example:
🔧 Technical Details
Trick 1 – Layered hash shucking
Hash shucking exploits systems where an outer hash or encryption layer uses as its key an inner hash (e.g., NTLM). Instead of brute-forcing the slow outer format with human-readable passwords, the attacker builds a wordlist of inner hashes (such as NT hashes) and feeds those directly to specialized cracking modes. For each inner-hash candidate, the tool derives the outer hash/encryption according to the target algorithm and compares it. A match confirms password reuse without knowing the plaintext, effectively stripping off the outer layer and leaving only the fast inner hash to attack or use directly.
Trick 2 – Using NT hashes as a global AD wordlist
In AD, the NT hash is
MD4(UTF-16LE(password))and is reused as the key material for multiple protocols: NTLM challenge-responses, Kerberos RC4-HMAC (etype 23) tickets, and DCC/DCC2 cached credentials. The trick is to treat every NT hash from one or more do...🤖 Agent Actions
Summary:
src/windows-hardening/active-directory-methodology/README.md, covering how to build NT hash corpora, use Hashcat NT-based modes (27000/27100/31500/31600/35300/35400), and leverage cross-domain Kerberoast and cached-credential shucking for rapid password-reuse validation and PtH operations, plus defensive guidance.Tests: Not run (not requested).
This PR was automatically created by the HackTricks Feed Bot. Please review the changes carefully before merging.