windows-privilege-escalation

Provide systematic methodologies for discovering and exploiting privilege escalation vulnerabilities on Windows systems during penetration testing engagements.

By sickn33 · 203 installs

npx skills add sickn33/agentic-awesome-skills --skill windows-privilege-escalation

Source repository · Upstream listing

⚠️ AUTHORIZED USE ONLY This skill is for educational purposes or authorized security assessments only. You must have explicit, written permission from the system owner before using this tool. Misuse of this tool is illegal and strictly prohibited. Mandatory confirmation gate Before running any command that probes, exploits, changes, persists on, extracts data from, or attempts credential access against a target: 1. Ask the user to state the exact target URL, IP, account, or resource. 2. Ask the user to confirm written authorization and the permitted scope. 3. Show the exact command(s) and explain their expected effect. 4. Wait for explicit confirmation in the current conversation. Without that confirmation, remain read only and provide defensive guidance only. Prefer a sandbox, disposable VM, or controlled lab. AUTHORIZED USE ONLY: Use this skill only for authorized security assessments, defensive validation, or controlled educational environments. Windows Privilege Escalation Detailed Guide Read [the detailed guide](references/detailed guide.md) before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end to end work, read the guide completely. Constraints and Limitations Operational Boundaries Kernel exploits may cause system instability Some exploits require specific Windows versions AV/EDR may detect and block common tools Token impersonation requires service account context Some techniques require GUI access Detection Considerations Credential dumping triggers security alerts Service modification logged in Event Logs PowerShell execution may be monitored Known exploit signatures detected by AV Legal Requirements Only test systems with written authorization Document all escalation attempts Avoid disrupting production systems Report all findings through proper channels Examples Example 1: Service Binary Path Exploitation Example 2: AlwaysInstallElevated Exploitation Example 3: JuicyPotato Token Impersonation Example 4: Unquoted Service Path Example 5: Credential Harvesting from Registry When to Use This skill is applicable to execute the workflow or actions described in the overview.