windows-discovery

Enumerate Windows systems for local privilege escalation vectors and misconfigurations.

253|37|Updated Feb 22, 2026
One-click install
npx skills add https://github.com/blacklanternsecurity/red-run --skill windows-discovery
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: windows-discovery
Source: https://github.com/blacklanternsecurity/red-run/tree/main/skills/privesc/windows-discovery
Command: npx skills add https://github.com/blacklanternsecurity/red-run --skill windows-discovery

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill helps penetration testers identify potential pathways to escalate privileges on Windows systems by enumerating configurations, services, and user contexts.

Core Features & Use Cases

  • System Enumeration: Gathers essential system information like OS version, architecture, and hotfixes.
  • Privilege Analysis: Checks user token privileges and group memberships for escalation opportunities.
  • Service Misconfiguration Detection: Identifies unquoted service paths, writable service binaries, and other service-related vulnerabilities.
  • Credential Hunting: Performs quick scans for stored credentials in various locations.
  • Use Case: After gaining initial access to a Windows machine, run this Skill to quickly find common misconfigurations that allow a low-privileged user to become an administrator.

Quick Start

Use the windows-discovery skill to enumerate potential privilege escalation vectors on the current Windows host.

Frequently Asked Questions about windows-discovery

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find Windows privilege escalation vectors after getting initial access?

You can enumerate local privilege escalation vectors by analyzing Windows system configurations, user privileges, services, scheduled tasks, and stored credentials to identify misconfigurations like unquoted service paths and AlwaysInstallElevated settings.

What common Windows service misconfigurations allow a low-privileged user to become an administrator?

Common Windows service misconfigurations that allow privilege escalation include unquoted service paths, writable service binaries, and AlwaysInstallElevated settings, detected by analyzing service configurations and user token privileges.

Can I use WinPEAS and PowerUp for comprehensive Windows post-exploitation enumeration?

Yes, this enumeration process supports using tools like WinPEAS, PowerUp, and Seatbelt to perform comprehensive Windows post-exploitation analysis and detect local privilege escalation vectors across system configurations.

Does Windows privilege escalation enumeration check for stored credentials and network information?

Yes, Windows privilege escalation enumeration performs quick scans for stored credentials in various locations and analyzes network information, alongside gathering OS version, architecture, hotfixes, and user token privileges.

What is the best way to enumerate Windows systems for local privilege escalation during red teaming?

The best way to enumerate Windows systems for local privilege escalation during red teaming is to comprehensively analyze system configurations, user privileges, services, scheduled tasks, network information, and stored credentials to identify exploitable misconfigurations.