Skip to main content

Overview

Potato attacks exploit SeImpersonatePrivilege or SeAssignPrimaryTokenPrivilege to escalate from a service account (IIS, MSSQL, etc.) to SYSTEM.

Check Privileges

If either is Enabled → potato attacks viable.
Service accounts like IIS APPPOOL, NT AUTHORITY\LOCAL SERVICE, NT AUTHORITY\NETWORK SERVICE, and SQL Server accounts typically have these privileges by default.

Which Potato to Use


Download

Kali Linux

GitHub

Check Architecture


JuicyPotato

Abuses COM servers with CLSID to impersonate SYSTEM token.

Basic Usage

Reverse Shell

With Specific CLSID

Finding Valid CLSIDs

Common working CLSIDs:
JuicyPotato does NOT work on Windows 10 build 1809+ and Server 2019+. Use PrintSpoofer or GodPotato instead.

PrintSpoofer

Abuses the print spooler service to capture SYSTEM token. Simpler than JuicyPotato.

Interactive SYSTEM Shell

Execute Command as SYSTEM

Reverse Shell


GodPotato

Works on most modern Windows versions. Needs .NET Framework 2.0+ — pick the matching binary (GodPotato-NET2.exe / GodPotato-NET35.exe / GodPotato-NET4.exe).

Check .NET Version

Execute Command

Reverse Shell

Add Admin User


SweetPotato

Combines multiple potato techniques (EfsPotato, PrintSpoofer, JuicyPotato).

Execute Command

Reverse Shell


RoguePotato

For Windows 10 1809+ / Server 2019. Requires attacker-controlled machine for OXID resolution.

Attacker (redirect port 135)

Victim


Named Pipe Impersonation

The primitive behind potato attacks: create a named pipe, trick a privileged process into connecting, then impersonate its token (requires SeImpersonatePrivilege).

PowerShell PoC

Coerce Privileged Auth

Force a machine/service account to authenticate to your pipe:
Capture with Responder or relay with ntlmrelayx. For domain coercion/relay chains, see PetitPotam and NTLM Relay.

Quick Decision