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›SpawnAs

Credentials & User Impersonation

SpawnAs

T1134.002 · MITRE ATT&CK

Use Cobalt Strike Beacon's spawnas command to start a temporary process under an alternate user's credentials and inject the selected listener payload to open a new Beacon session. The new session has the supplied account's effective rights; spawnas does not itself grant elevated privileges.

ArtifactsRESTRICTED_ACCESS_BLUR_MARKER

Steps1

CategoryToken Impersonation

Discuss in Advisor

Walkthrough

Step 1

RESTRICTED_ACCESS_BLUR_MARKER

RESTRICTED_ACCESS_BLUR_MARKER

Requirements: ALL(RESTRICTED_ACCESS_BLUR_MARKER)

Check before starting: RESTRICTED_ACCESS_BLUR_MARKER

Variant:

Full outcome coverage

Impacket · RPC session enumeration (impacket)

RPC session enumeration (impacket)

powershell

RESTRICTED_ACCESS_BLUR_MARKER

Version: RESTRICTED_ACCESS_BLUR_MARKER. Requirements: none specified (operational prerequisites may still apply)Documents all requested outcomes. This is a candidate, not proof of execution or compatibility.Source references: RESTRICTED_ACCESS_BLUR_MARKER. Source support does not verify execution.

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