MITRE ATT&CK T1003: OS Credential Dumping
When to use this skill
Use this skill when the task involves T1003, OS Credential Dumping, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.
Technique context
- ATT&CK domain: enterprise
- ATT&CK ID: T1003
- Technique name: OS Credential Dumping
- Type: technique
- ATT&CK URL: https://attack.mitre.org/techniques/T1003
- Tactics: credential-access
- Platforms: Linux, macOS, Windows
- Required permissions: Not specified
- Effective permissions: Not specified
- Defenses bypassed: Not specified
ATT&CK description
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password. Credentials can be obtained from OS caches, memory, or structures.(Citation: Brining MimiKatz to Unix) Credentials can then be used to perform Lateral Movement and access restricted information.
Several of the tools mentioned in associated sub-techniques may be used by both adversaries and professional security testers. Additional custom tools likely exist as well.
Agent workflow
- Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.
- Load bundled resources as needed: use
references/technique-profile.json for structured metadata, references/detection-and-mitigation.md for triage and telemetry guidance, references/known-threat-context.md for ATT&CK relationship context, and templates/ for repeatable outputs.
- Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.
- Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.
- Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.
- Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.
Bundled resources
references/technique-profile.json: machine-readable ATT&CK metadata for this technique.
references/detection-and-mitigation.md: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.
references/known-threat-context.md: ATT&CK relationship context with attribution cautions.
templates/detection-brief.md: detection engineering brief template.
templates/hunt-plan.md: threat hunt plan template.
templates/incident-response-note.md: incident response note template.
templates/coverage-assessment.md: ATT&CK coverage assessment template.
scripts/render_brief.py: local helper that renders a Markdown defensive brief from technique-profile.json.
assets/output-schema.json: JSON schema for structured technique analysis outputs.
To generate a quick brief, run python scripts/render_brief.py --output brief.md from inside this skill directory, or adapt the templates directly.
Detection guidance
No ATT&CK detection guidance was present in the source STIX object.
Useful telemetry and data sources
- Not specified in the STIX object.
Mitigations to consider
- Active Directory Configuration
- Behavior Prevention on Endpoint
- Credential Access Protection
- Encrypt Sensitive Information
- Operating System Configuration
- Password Policies
- Privileged Account Management
- Privileged Process Integrity
- User Training
Known threat context
Use these examples only as contextual leads, not as proof that an observed event is this technique:
- APT28 (intrusion-set)
- APT32 (intrusion-set)
- APT39 (intrusion-set)
- Axiom (intrusion-set)
- BlackByte (intrusion-set)
- Carbanak (malware)
- Ember Bear (intrusion-set)
- HOMEFRY (malware)
- Leviathan (intrusion-set)
- MgBot (malware)
- Mustang Panda (intrusion-set)
- OnionDuke (malware)
- PinchDuke (malware)
- Poseidon Group (intrusion-set)
- Revenge RAT (malware)
- Sowbug (intrusion-set)
- Storm-0501 (intrusion-set)
- Suckfly (intrusion-set)
- Tonto Team (intrusion-set)
- Trojan.Karagany (malware)
Recommended output pattern
When responding with this skill, structure the answer as:
- Assessment: whether the evidence supports this ATT&CK mapping and why.
- Evidence: specific indicators, logs, behaviors, and assumptions.
- Detection: telemetry sources, analytic logic, and tuning considerations.
- Response: containment, eradication, recovery, and validation actions.
- Coverage gaps: missing logs, sensors, controls, or environmental details.
- References: include the ATT&CK URL and any user-provided evidence references.
ATT&CK contributors
- Vincent Le Toux
- Ed Williams, Trustwave, SpiderLabs
- Tim (Wadhwa-)Brown
- Yves Yonan
1---2name: attack-ent-t1003-os-credential-dumping3description: "Analyze MITRE ATT&CK T1003 OS Credential Dumping in the enterprise matrix. Use for TTP triage, detection engineering, hunting, defensive emulation planning, mitigations, incident response mapping, ATT&CK coverage, or questions mentioning T1003, OS Credential Dumping, or enterprise ATT&CK. Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password."4license: MITRE ATT&CK Terms of Use apply to ATT&CK-derived content. See https://attack.mitre.org/resources/terms-of-use/5metadata:6 source: https://skillmd.com/skills/santosomar/attack-ent-t1003-os-credential-dumping7 upstream: mitre-attack/attack-stix-data8 domain: enterprise9 attack_id: T100310 attack_stix_id: attack-pattern--0a3ead4e-6d47-4ccb-854c-a6a4f9d96b2211 attack_version: "2.2"12 attack_modified: "2025-10-24T17:48:22.201Z"13---1415# MITRE ATT&CK T1003: OS Credential Dumping1617## When to use this skill1819Use this skill when the task involves T1003, OS Credential Dumping, enterprise ATT&CK, TTP mapping, detection engineering, hunting, incident-response enrichment, control validation, or authorized adversary-emulation planning. Treat it as a defensive analysis aid: keep outputs focused on understanding, detecting, mitigating, and safely validating this ATT&CK technique.2021## Technique context2223- ATT&CK domain: enterprise24- ATT&CK ID: T100325- Technique name: OS Credential Dumping26- Type: technique27- ATT&CK URL: https://attack.mitre.org/techniques/T100328- Tactics: credential-access29- Platforms: Linux, macOS, Windows30- Required permissions: Not specified31- Effective permissions: Not specified32- Defenses bypassed: Not specified3334## ATT&CK description3536Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password. Credentials can be obtained from OS caches, memory, or structures.(Citation: Brining MimiKatz to Unix) Credentials can then be used to perform [Lateral Movement](https://attack.mitre.org/tactics/TA0008) and access restricted information.3738Several of the tools mentioned in associated sub-techniques may be used by both adversaries and professional security testers. Additional custom tools likely exist as well.3940## Agent workflow41421. Clarify scope: identify the system, asset class, log sources, cloud or endpoint platform, and whether the user wants triage, detection, coverage assessment, or safe emulation planning.432. Load bundled resources as needed: use `references/technique-profile.json` for structured metadata, `references/detection-and-mitigation.md` for triage and telemetry guidance, `references/known-threat-context.md` for ATT&CK relationship context, and `templates/` for repeatable outputs.443. Map observations to ATT&CK: compare the user's evidence to the ATT&CK description, tactics, platforms, and known procedure patterns before asserting a match.454. Produce defensive outputs: prioritize hypotheses, telemetry requirements, detection logic ideas, validation steps, containment guidance, and mitigations.465. Preserve uncertainty: distinguish confirmed evidence, plausible indicators, assumptions, and gaps. Recommend what to collect next.476. Stay safe: do not provide malware, credential theft, persistence, evasion, destructive automation, or unauthorized exploitation instructions. For adversary emulation, keep steps bounded to approved lab or control-validation contexts and omit operational abuse details.4849## Bundled resources5051- `references/technique-profile.json`: machine-readable ATT&CK metadata for this technique.52- `references/detection-and-mitigation.md`: detection notes, telemetry checklist, triage questions, mitigation candidates, and false-positive considerations.53- `references/known-threat-context.md`: ATT&CK relationship context with attribution cautions.54- `templates/detection-brief.md`: detection engineering brief template.55- `templates/hunt-plan.md`: threat hunt plan template.56- `templates/incident-response-note.md`: incident response note template.57- `templates/coverage-assessment.md`: ATT&CK coverage assessment template.58- `scripts/render_brief.py`: local helper that renders a Markdown defensive brief from `technique-profile.json`.59- `assets/output-schema.json`: JSON schema for structured technique analysis outputs.6061To generate a quick brief, run `python scripts/render_brief.py --output brief.md` from inside this skill directory, or adapt the templates directly.6263## Detection guidance6465No ATT&CK detection guidance was present in the source STIX object.6667## Useful telemetry and data sources6869- Not specified in the STIX object.7071## Mitigations to consider7273- Active Directory Configuration74- Behavior Prevention on Endpoint75- Credential Access Protection76- Encrypt Sensitive Information77- Operating System Configuration78- Password Policies79- Privileged Account Management80- Privileged Process Integrity81- User Training8283## Known threat context8485Use these examples only as contextual leads, not as proof that an observed event is this technique:8687- APT28 (intrusion-set)88- APT32 (intrusion-set)89- APT39 (intrusion-set)90- Axiom (intrusion-set)91- BlackByte (intrusion-set)92- Carbanak (malware)93- Ember Bear (intrusion-set)94- HOMEFRY (malware)95- Leviathan (intrusion-set)96- MgBot (malware)97- Mustang Panda (intrusion-set)98- OnionDuke (malware)99- PinchDuke (malware)100- Poseidon Group (intrusion-set)101- Revenge RAT (malware)102- Sowbug (intrusion-set)103- Storm-0501 (intrusion-set)104- Suckfly (intrusion-set)105- Tonto Team (intrusion-set)106- Trojan.Karagany (malware)107108## Recommended output pattern109110When responding with this skill, structure the answer as:111112- Assessment: whether the evidence supports this ATT&CK mapping and why.113- Evidence: specific indicators, logs, behaviors, and assumptions.114- Detection: telemetry sources, analytic logic, and tuning considerations.115- Response: containment, eradication, recovery, and validation actions.116- Coverage gaps: missing logs, sensors, controls, or environmental details.117- References: include the ATT&CK URL and any user-provided evidence references.118119## ATT&CK contributors120121- Vincent Le Toux122- Ed Williams, Trustwave, SpiderLabs123- Tim (Wadhwa-)Brown124- Yves Yonan