Individual skill
detecting-mimikatz-execution-patterns
Detect Mimikatz execution through command-line patterns, LSASS access signatures, binary indicators, and in-memory detection of known modules.
internal/tools/skills/data/threat-hunting/detecting-mimikatz-execution-patterns/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
- Yes
- 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,325
- 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
- threat-hunting Declared skill tag
- mitre-attack Declared skill tag
- mimikatz Declared skill tag
- credential-dumping Declared skill tag
- edr Declared skill tag
- t1003 Declared skill tag
- proactive-detection 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
SKILL.mdcore · 4,812 bytes
Read excerpt
# Detecting Mimikatz Execution Patterns
## When to Use
- When proactively hunting for indicators of detecting mimikatz execution patterns in the environment
- After threat intelligence indicates active campaigns using these techniques
- During incident response to scope compromise related to these techniques
- When EDR or SIEM alerts trigger on related indicators
- During periodic security assessments and purple team exercises
## Detection Gaps & Validation
- **String/hash signatures are trivially evaded.** Renamed binaries, in-memory execution (Invoke-Mimikatz, reflective PE load, Cobalt Strike BOFs), and renamed module strings (`sekurlsa::logonpasswords`) defeat command-line and file-hash detection. Don't anchor on `mimikatz` keywords.
- **The durable signal is LSASS access.** Hunt Sysmon **EID 10** ProcessAccess targeting `lsass.exe` with `GrantedAccess` of `0x1010`, `0x1410`, `0x143a`, or `0x1fffff` from a non-system process. Verify EID 10 is enabled and lsass is not excluded in the Sysmon config — a common gap.