Disclaimer: This material is provided for educational purposes and authorized security testing only.
You are solely responsible for how
you use the information. Do not use these techniques on systems without explicit permission from the owner.
We
do not encourage any kind of illegal or harmful activity
- Run winPEAS to gather extensive information about the system:
.\winpeas.exe cmd > output.txt
- Run Seatbelt for a broader range of checks:
.\Seatbelt.exe -group=all -full > output.txt
- If scripts fail, use manual commands (see the enumeration section).
Step 2. Review and analyze enumeration results
- Carefully review results: Tools like winPEAS and Seatbelt produce large amounts of output. Take time to understand it.
- Make notes of interesting findings such as misconfigurations, sensitive files, or unusual permissions.
- Avoid rabbit holes: Prioritize promising leads instead of chasing low-value findings.
Step 3. File and directory inspection
- Inspect common directories for sensitive files, such as:
C:\
C:\Program Files
C:\Users\Public\Desktop
- Read through any interesting files they may contain credentials, configuration details, or escalation clues.
Step 4. Quick wins
- Prioritize easy methods: Look for registry exploits, weak service permissions, or obvious misconfigurations.
- Check running administrative processes, note versions, and search for known exploits.
- Identify internal ports that may be forwarded to your attacker machine for lateral movement or privilege escalation.
Step 5. Re-evaluate enumeration data
- If privilege escalation is not yet achieved, review all collected data again.
- Highlight anything unusual: unfamiliar processes, suspicious file names, or unexpected users.
- Reconsider kernel exploits as a last resort.
General tips
- Stay calm and methodical — privilege escalation often requires patience.
- Document your findings meticulously. Even small details may prove useful later.
- Use multiple tools: different tools (winPEAS, Seatbelt, manual enumeration) reveal different insights.
- Focus on quick wins: weak permissions, stored credentials, or misconfigured services.
- Be ready to adapt: if one approach fails, reassess and try alternatives.