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›Defense Evasion›Run Virtual Instance with Bridged Networking

Defense Evasion

Run Virtual Instance with Bridged Networking

T1564.006 · MITRE ATT&CK

Configure and start an existing VirtualBox VM with bridged networking. VirtualBox exchanges packets through a selected host network interface, circumventing the host OS network stack; the guest may appear with an IP address or hostname that differs from the host and can be harder to attribute. This may evade controls that rely specifically on the host network stack, but it does not guarantee unmonitored access or isolate guest traffic.

ArtifactsRESTRICTED_ACCESS_BLUR_MARKER

Steps1

CategoryObfuscation

Discuss in Advisor

Walkthrough

Step 1

RESTRICTED_ACCESS_BLUR_MARKER

RESTRICTED_ACCESS_BLUR_MARKER

Requirements: none specified (operational prerequisites may still apply)

Check before starting: RESTRICTED_ACCESS_BLUR_MARKER

Variant:

Full outcome coverage

Ekko · Run the proof-of-concept executable

Run the proof-of-concept executable

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.preconditions: RESTRICTED_ACCESS_BLUR_MARKERverification: RESTRICTED_ACCESS_BLUR_MARKERlimitations: RESTRICTED_ACCESS_BLUR_MARKERcleanup: RESTRICTED_ACCESS_BLUR_MARKER

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