Individual skill
extracting-credentials-from-memory-dump
Extract cached credentials, password hashes, Kerberos tickets, and authentication tokens from memory dumps using Volatility and Mimikatz for forensic investigation.
internal/tools/skills/data/digital-forensics/extracting-credentials-from-memory-dump/SKILL.md
Source commit d42f381ad34843e71a42658e5c57290c713e85af
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Instructions only
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,331
- Repository last updated
- Nov 9, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- cybersecurity Repository topic
- security Repository topic
- bug-bounty Repository topic
- automation Repository topic
- autonomous-pentesting Repository topic
- ai-agent Repository topic
- ai-security Repository topic
- ethical-hacking Repository topic
- golang Repository topic
- penetration-testing Repository topic
- forensics Declared skill tag
- credential-extraction Declared skill tag
- memory-forensics Declared skill tag
- volatility Declared skill tag
- mimikatz Declared skill tag
- password-hashes Declared skill tag
- incident-response Declared skill tag
- security Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Extracting Credentials from Memory Dump
## When to Use
- During incident response to determine what credentials an attacker had access to
- When assessing the scope of credential compromise after a breach
- For identifying accounts that need immediate password resets
- When investigating lateral movement and pass-the-hash/pass-the-ticket attacks
- For recovering encryption keys or authentication tokens from process memory
## Detection Gaps & Validation
- **Credential Guard defeats LSASS scraping.** When VBS/Credential Guard is enabled, derived secrets (NTLM, Kerberos keys) live in the isolated LSAIso process and `pypykatz`/`mimikatz`/`windows.lsadump` return little or nothing. Confirm Credential Guard state before concluding "no credentials present."
- **No plaintext by default.** WDigest plaintext requires `UseLogonCredential=1` (HKLM\SYSTEM\...\WDigest); on Windows 8.1+ it is off, so an empty WDigest field is expected, not a tool failure.
- **RunAsPPL / LSA Protection** blocks process access to lsass.exe, so a memory image taken without it (or an offline dump) is required; live `windows.memmap --pid <lsass>` may yield smeared/partial data.
- **Volatility symbol mismatch = false negatives.** A wrong build/symbol table makes `windows.hashdump`/`pslist` return empty. Verify with `windows.info` and confirm the lsass PID is actually present before trusting an empty result.