Advanced Search Keywords:

opsec:low - Show techniques with low noise level (stealthy)
phase:"initial access" - Filter by phase (use quotes for spaces)
category:lateral - Filter by category
platform:windows - Filter by platform
tag:credential - Find items with specific tag in results
external:true - Show only external techniques

Combining Keywords:

tag:stealth phase:"initial access" password

Searches for "password" within low-noise techniques in the initial access phase

RTT· red team

RTT · red team

Advanced Search Keywords:

opsec:low - Show techniques with low noise level (stealthy)
phase:"initial access" - Filter by phase (use quotes for spaces)
category:lateral - Filter by category
platform:windows - Filter by platform
tag:credential - Find items with specific tag in results
external:true - Show only external techniques

Combining Keywords:

tag:stealth phase:"initial access" password

Searches for "password" within low-noise techniques in the initial access phase

Search techniques, tools, commands…⌘K

No scenario

No scenario · all techniques in scope

IdleStatus

0Scenarios

Advanced Search Keywords:

opsec:low - Show techniques with low noise level (stealthy)
phase:"initial access" - Filter by phase (use quotes for spaces)
category:lateral - Filter by category
platform:windows - Filter by platform
tag:credential - Find items with specific tag in results
external:true - Show only external techniques

Combining Keywords:

tag:stealth phase:"initial access" password

Searches for "password" within low-noise techniques in the initial access phase

Back to Techniques

Techniques›Credentials & User Impersonation›Credential Extraction via Debugger

Credentials & User Impersonation

Credential Extraction via Debugger

Conceptual Windows credential-access behavior in which a debugger attaches to a credential-bearing process and inspects its runtime state. Attaching alone does not establish credential extraction: sufficient process access and a validated way to identify and recover credential material are required. For LSASS memory specifically, ATT&CK maps access to stored credential material to T1003.001; enabled LSA protection prevents debugger attachment to LSASS. This record has no verified tool or step sequence and is not an executable procedure.

Steps1

CategoryCredential Dumping

Discuss in Advisor

Walkthrough

Step 1

RESTRICTED_ACCESS_BLUR_MARKER

RESTRICTED_ACCESS_BLUR_MARKER

Requirements: ALL(RESTRICTED_ACCESS_BLUR_MARKER)

Variant:

Full outcome coverage

Cobalt Strike · Inject a shellcode payload into a process from Beacon

Inject a shellcode payload into a process from Beacon

powershell

RESTRICTED_ACCESS_BLUR_MARKER

Version: RESTRICTED_ACCESS_BLUR_MARKER. Requirements: ALL(RESTRICTED_ACCESS_BLUR_MARKER)Documents all requested outcomes. This is a candidate, not proof of execution or compatibility.

RESTRICTED_ACCESS_BLUR_MARKER

Detection signal

Detection 01

RESTRICTED_ACCESS_BLUR_MARKER

Mitigations

Mitigation 01

RESTRICTED_ACCESS_BLUR_MARKER

OPSEC notes

RESTRICTED_ACCESS_BLUR_MARKER

References

Extended details

RESTRICTED_ACCESS_BLUR_MARKER