Skip to content
NewCybercrime Report 2026 · Eight Chapters · A Post Is Not An Incident → Explore The ChaptersCybercrime Report 2026 → Explore

Odin Research / What is / Offensive and testing tools

What Is PrintSpoofer? Windows Impersonation Privilege Escalation

A small public tool that turns a web or database service account into SYSTEM on Windows. Why it works, where Odin Research found it staged, and how to catch it.

By
Odin by Brandefense
Updated
21 Nov 2026
Reading time
7 min read
Type
Offensive tool

In short

PrintSpoofer is a public Windows privilege escalation tool. It abuses the SeImpersonatePrivilege right, which many service accounts hold, by tricking the Print Spooler service into connecting to a named pipe the attacker controls. The attacker then impersonates the spooler's SYSTEM token. It works after an attacker already runs code as a service account.

Key takeaways

What it is
An open-source proof-of-concept by the researcher itm4n, published in 2020, that escalates from a service account to SYSTEM on Windows 10 and Windows Server 2016 and 2019.
How it works
It uses the "printer bug" to make the SYSTEM-level Print Spooler connect to an attacker-controlled named pipe, then impersonates that connection's token.
Why it matters
Web shells and database command execution usually start as service accounts. PrintSpoofer is one of the quickest ways from there to full control of the host.
What Odin Research saw
PrintSpoofer binaries or source staged on attacker servers in Monographs 03, 05 and 07, including next to a confirmed Sliver C2 listener and MSSQL pivot scripts.
What to do first
Limit SeImpersonatePrivilege to the accounts that need it, disable the Print Spooler where nobody prints, and alert on PrintSpoofer file names and command lines.

What is PrintSpoofer?

PrintSpoofer is a public Windows privilege escalation tool. It turns an account that holds the SeImpersonatePrivilege right, such as a web or database service account, into the all-powerful SYSTEM account. It does this by abusing the Print Spooler service and a named pipe. Attackers use it after they already run code on a server.

The researcher itm4n released PrintSpoofer on GitHub with a blog post dated 2 May 2020. The README describes it as abusing impersonation privileges through the "printer bug". It lists Windows 10 and Windows Server 2016 and 2019 as targets. The repository was archived and made read-only in September 2024.

PrintSpoofer is not an exploit for a software bug with a CVE number. It abuses intended Windows behavior. According to itm4n, Microsoft treats impersonation-based escalation from service accounts as expected behavior rather than a vulnerability.

How PrintSpoofer works

The technique has three ingredients:

  1. An impersonation right. Windows lets services act on behalf of clients that connect to them. Microsoft documents that the "Impersonate a client after authentication" right (SeImpersonatePrivilege) goes by default to Administrators, Local Service, Network Service and Service. Components such as IIS and ASP.NET may need it for more accounts.
  2. A named pipe the attacker controls. A named pipe is a channel that Windows processes use to talk to each other. The attacker creates one with a crafted name.
  3. A SYSTEM service that connects to it. The "printer bug" is a call to the Print Spooler's remote interface that makes the spooler, running as SYSTEM, send a notification to a pipe path. itm4n showed how to steer that connection to the attacker's pipe.

When the spooler connects, the attacker's process impersonates it and gains a SYSTEM token. MITRE ATT&CK files this behavior under Token Impersonation/Theft (T1134.001), a sub-technique of Access Token Manipulation.

PrintSpoofer is part of a family of "Potato" tools that abuse the same right through different services. itm4n explained that older Rotten Potato and Juicy Potato methods broke on newer Windows 10 builds, which is why a new path through the spooler was useful.

How attackers use PrintSpoofer

PrintSpoofer is a second-stage tool. Attackers reach for it once they can run commands as a service account, which happens often:

  • After a web shell. A web shell runs as the web server's identity. Microsoft notes that IIS and ASP.NET may need SeImpersonatePrivilege for their accounts.
  • After SQL Server command execution. Odin Research has seen toolkits that chain xp_cmdshell into PrintSpoofer loaders.
  • Before credential theft. SYSTEM access lets the attacker dump credentials with tools such as Mimikatz, add hidden admin accounts or turn off defenses.

The public source code is small and easy to rebuild or load from memory, so file hashes alone are a weak control. See Exploitation for Privilege Escalation for the wider tactic.

What Odin Research observed

Odin Research found PrintSpoofer staged on attacker-controlled or exposed servers in three monographs. All were files on staging servers. Nothing showed the tool running on a victim.

  • Beside a Sliver C2 server. Monograph 07 describes a confirmed Sliver server in China that also staged PrintSpoofer64.exe and a 13,670-byte PrintSpoofer.cpp source file with its -i, -d and -c options. The server's own web log recorded local downloads of the binary.
  • Inside an MSSQL pivot chain. Monograph 03 describes a 1,824-record workbench with scripts that chain MSSQL xp_cmdshell into reflective .NET PrintSpoofer loaders. It also staged NtApiDotNet.dll, a .NET token and RPC library used by those loaders. The report weighs this against red-team and lab explanations.
  • With other Potato tools. Monograph 05 found PrintSpoofer64.exe beside GodPotato and an EFS Potato source file, Kerberos ticket caches and AS-REP roasting logs, in a tree aimed at Active Directory and local escalation.

The pattern is consistent: PrintSpoofer sits in the toolkit between first access as a service account and domain-level credential theft.

How to detect PrintSpoofer

  • File names and downloads. Alert on PrintSpoofer.exe, PrintSpoofer64.exe or its source files on servers, and on outbound downloads of them.
  • Command lines. Flag processes that pass -i or -d together with -c cmd or -c powershell.
  • Parent and child processes. A web worker such as w3wp.exe or sqlservr.exe whose child process runs as SYSTEM is a strong sign of impersonation abuse.
  • Named pipe activity. EDR products that log pipe creation can catch new pipes with unusual names followed by spooler connections.
  • New admins after a web alert. Watch for new local administrators or service installs shortly after a web shell or xp_cmdshell alert.

Odin Research publishes rules for this. Monograph 07 carries a Suricata signature for staged PrintSpoofer downloads and a Sigma rule for PrintSpoofer binaries and command lines. Monograph 03 adds a Sigma rule set for Java-spawned encoded PowerShell and hidden MSSQL$ accounts. All rules are in the Defense Kit.

How to defend against PrintSpoofer

  1. Limit the right. Review which accounts hold SeImpersonatePrivilege. Microsoft advises that on member servers only Administrators and the service groups should have it. See least privilege.
  2. Turn off what you do not use. Disable the Print Spooler on servers that do not print, especially domain controllers and web servers.
  3. Harden the first step. PrintSpoofer needs an existing foothold. Patch public web apps, keep xp_cmdshell disabled, and run services under low-privilege virtual or managed accounts.
  4. Assume SYSTEM if you find it. If PrintSpoofer is found on a host, treat the host as fully controlled, reset local and cached credentials, and check for new accounts. See EDR for the telemetry you need.

PrintSpoofer compared with other Potato tools

ToolAbused service or pathNeedsOdin sighting
PrintSpooferPrint Spooler and a named pipeSeImpersonatePrivilegeMonographs 03, 05 and 07
Rotten Potato and Juicy PotatoCOM activation over local TCPSeImpersonatePrivilegeOlder Windows; broken on newer Windows 10 per itm4n
GodPotatoA different service pathSeImpersonatePrivilegeMonograph 05
EFS PotatoA different service pathSeImpersonatePrivilegeMonograph 05 (source file)

Frequently asked questions about PrintSpoofer

What is PrintSpoofer?

PrintSpoofer is a public Windows privilege escalation tool by itm4n. It abuses SeImpersonatePrivilege and the Print Spooler service to turn a service account into SYSTEM.

Is PrintSpoofer malware?

It is an open-source proof-of-concept and a hacking tool, not self-spreading malware. Finding it on a server you did not test is a serious sign.

Is PrintSpoofer a vulnerability with a CVE?

No. It abuses intended Windows impersonation behavior. According to its author, Microsoft treats this kind of service-account escalation as expected behavior rather than a security bug.

Which Windows versions does PrintSpoofer work on?

The project README lists Windows 10 and Windows Server 2016 and 2019. The author's blog post also reports it working on Windows 8.1 and Server 2012 R2.

What is SeImpersonatePrivilege?

It is the Windows right called Impersonate a client after authentication. It lets a service act on behalf of a client. By default Administrators, Local Service, Network Service and Service hold it.

How do I detect PrintSpoofer?

Alert on PrintSpoofer file names, command lines with -i or -d and -c, web or database workers that spawn SYSTEM processes, and unusual named pipes. Odin Research publishes Suricata and Sigma rules in its Defense Kit.

Does disabling Print Spooler stop PrintSpoofer?

It removes the service PrintSpoofer relies on. Other Potato tools abuse different services, so also limit SeImpersonatePrivilege and fix the access that got the attacker onto the host.

PrintSpoofer vs JuicyPotato: what is the difference?

Both abuse SeImpersonatePrivilege. JuicyPotato relies on COM activation over local TCP, which newer Windows 10 builds broke. PrintSpoofer uses the Print Spooler and a named pipe instead.

Sources

  1. itm4n, PrintSpoofer repository, GitHub. github.com/itm4n/PrintSpoofer (checked 21 November 2026)
  2. itm4n, "PrintSpoofer - Abusing Impersonation Privileges on Windows 10 and Server 2019", 2 May 2020. itm4n.github.io/printspoofer-abusing-impersonate-privileges/ (checked 21 November 2026)
  3. Microsoft Learn, Impersonate a client after authentication (security policy setting). learn.microsoft.com/en-us/windows/security/threat-protection/security-policy-settings/impersonate-a-client-after-authentication (checked 21 November 2026)
  4. MITRE ATT&CK, T1134.001 Access Token Manipulation: Token Impersonation/Theft. attack.mitre.org/techniques/T1134/001/ (checked 21 November 2026)

Related tools and terms

All Odin Research explanations · Brandefense glossary

Odin Research

Get the rules, not just the definition

Every Odin Research report ships with verified indicators and detection rules you can load today.

Open the Defense Kit