githubEdit

Lateral Movement


The Double Hop Problem

After lateral movement via WinRM/PsExec, the new Beacon may fail to authenticate to other domain resources.

Reason: Network logon type doesn't cache credentials in LSASS on the remote target. Both WinRM and PsExec use Network logon type.

# After WinRM lateral movement
powershell-import C:\Tools\PowerSploit\Recon\PowerView.ps1
powerpick Get-DomainTrust

ERROR: Exception calling "FindOne" with "0" argument(s): "An operations error occurred."

After moving laterally, you only have the service ticket that allowed the connection:

Cached Tickets: (1)

#0>	Client: tmorgan @ INLANEFREIGHT.LOCAL
	Server: HTTP/ilf-ws-1 @ INLANEFREIGHT.LOCAL
	KerbTicket Encryption Type: AES-256-CTS-HMAC-SHA1-96

Solution: Use impersonation technique (make_token or ptt) to populate the session with credentials.

Or, run enumeration from the original session that already has credential material.


WinRM

Beacon runs in context of current/impersonated user.


PsExec

Beacon runs as SYSTEM.

⚠️ LOUD - Service creation is relatively rare and easily detected.


SCShell (Quieter PsExec)

Modifies an existing service temporarily instead of creating a new one.

Setup: Load C:\Tools\SCShell\CS-BOF\scshell.cna via Cobalt Strike > Script Manager


WMI

Upload payload and execute via WMI.


MavInject (OPSEC Warning)

⚠️ BAD OPSEC - Avoid if possible.

Injects DLL into remote process using signed Microsoft executable.


SOCKS Proxy

Start SOCKS Proxy

Add Targets to Hosts File

Required for Kerberos (needs hostnames):

Proxifier (Windows)

  1. Profile > Proxy Servers - Add team server IP and SOCKS port

  2. Profile > Proxification Rules - Target internal IP range only

  3. Run tools through proxy (e.g., AD Explorer: C:\Tools\SysinternalsSuite\ADExplorer64.exe)

AD Enumeration via SOCKS

Kerberos Authentication via SOCKS

Create process with injected ticket:

Request service tickets manually:


Reverse Port Forwards

Forward traffic from compromised host back to team server.

Example: Forward HTTP to Team Server

Check View > Web Log for incoming requests.

Cleanup


Quick Reference

Technique
Runs As
OPSEC
Use Case

jump winrm64

Current user

Medium

General lateral movement

jump psexec64

SYSTEM

Loud

Need SYSTEM access

jump scshell64

SYSTEM

Quieter

Avoid service creation

remote-exec wmi

Current user

Medium

Custom payload execution

MavInject

Target process

Bad

Last resort DLL injection

Last updated