win-privesc

win-privesc is a command for Claude Code from pashki975/thm-claude-kit. It costs 9 tokens per session (418 once invoked), scanned A, original, MIT.

A checklist for finding ways to gain higher permissions on a Windows computer after getting access to it. Local privilege escalation means moving from a limited account to an administrator or system account.

In plain words
What is it for?
Use it to inspect Windows privileges and groups, check for vulnerable services and unquoted paths, analyze command output, and choose relevant tools or privilege-based techniques in a TryHackMe challenge.
Why use it?
It organizes common checks so you can find likely paths quickly instead of testing Windows settings at random. It covers account privileges, groups, system details, services, and other common weaknesses.

Command for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Good fit Use it to inspect Windows privileges and groups, check for vulnerable services and unquoted paths, analyze command output, and choose relevant tools or privilege-based techniques in a TryHackMe challenge.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/pashki975/thm-claude-kit/win-privesc
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Clone the repo
git clone --depth 1 https://github.com/pashki975/thm-claude-kit

Made for: Claude Code.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for win-privesc

README.md
[![agentmods](https://agentmods.dev/badge/commands/pashki975/thm-claude-kit/win-privesc.svg)](https://agentmods.dev/commands/pashki975/thm-claude-kit/win-privesc)
Your own site
<a href="https://agentmods.dev/commands/pashki975/thm-claude-kit/win-privesc"><img src="https://agentmods.dev/badge/commands/pashki975/thm-claude-kit/win-privesc.svg" alt="Measured on agentmods" height="20"></a>
Per session 9 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 418 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00009 $0.00418
Opus 5 $0.00005 $0.00209
Sonnet 5 $0.00002 $0.00084
Haiku 4.5 $0.00001 $0.00042

Measured 7d ago against content hash f1a97723a3cc, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

win-privesc scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/commands/win-privesc.md · 36 lines

What it actually says

Guide Windows privesc on the shell we have. Args (optional): $ARGUMENTS

Walk me through enumeration, then analyze whatever output I paste back. Prioritize the quick wins first.

1. Quick manual checks (paste output back to me)

  • whoami /priv — look for SeImpersonatePrivilege, SeBackupPrivilege, SeDebugPrivilege, etc.
  • whoami /groups — group memberships
  • systeminfo — OS build + hotfixes (for kernel-exploit matching)
  • net user / net localgroup administrators

2. Token privilege exploits (very common on THM)

  • SeImpersonatePrivilege → Potato attacks (PrintSpoofer / GodPotato / JuicyPotato). This is the single most common Windows CTF privesc. If present, prioritize it.
  • SeBackupPrivilege → dump SAM/SYSTEM hives, extract hashes offline
  • SeDebugPrivilege → dump lsass / migrate into a SYSTEM process

3. Automated enum (upload and run one)

  • winPEAS: winPEASx64.exe (host it over HTTP, download to the box, run)
  • PowerUp: powershell -ep bypass -c ". .\PowerUp.ps1; Invoke-AllChecks"
  • Serve files from Kali: python3 -m http.server 80

4. Other classic vectors to check

  • Unquoted service paths, weak service permissions (accesschk / PowerUp)
  • AlwaysInstallElevated registry keys
  • Stored creds: cmdkey /list, registry autologon, unattend.xml, saved PowerShell history
  • Scheduled tasks running as SYSTEM

5. Analysis

When I paste enum output, hand it to the win-privesc-advisor agent for a ranked plan with exact commands. Record the winning path and the root/administrator flag in notes.md.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 7d ago First seen · 36 lines · 9 tokens per session scan A f1a97723a3cc

Subscribe to this mod's changes

win-privesc is a command published in the GitHub repository pashki975/thm-claude-kit (2 stars, last pushed 23d ago), licensed MIT. It adds 9 tokens to every session and 418 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.