Skip to main content

PEASS-ng

LinPEAS, WinPEAS, and macPEAS scripts that audit Linux, Windows, and macOS systems for privilege escalation paths and exposed credentials.

Technical Architecture & Overview

PEASS-ng bundles LinPEAS, WinPEAS, and macPEAS into a single framework of privilege escalation audit scripts. Each script inspects system configuration, file permissions, and process states for paths that could lead to unauthorized access. The results help administrators close misconfigurations and harden endpoints before an adversary can misuse them.

Targeted Technical Use Cases

Authorized internal audits and hardening exercises on Linux, Windows, and macOS endpoints.

Evaluation & Trade-offs

Core Strengths

  • +Covers Linux, Windows, and macOS in one project with color-coded output.
  • +Actively maintained with frequent rule updates.
  • +Fast execution with no installation requirements on target systems.

Trade-Offs & Limitations

  • -Can produce false positives on heavily customized systems.
  • -Output can be noisy without manual review and filtering.
  • -Some checks require local execution with sufficient privileges.

Defensive Security Application

Use PEASS-ng to find and remediate privilege escalation paths before external assessments.

Frequently Asked Questions

What is PEASS-ng?

PEASS-ng bundles LinPEAS, WinPEAS, and macPEAS into a single framework of privilege escalation audit scripts. Each script inspects system configuration, file permissions, and process states for paths that could lead to unauthorized access. The results help administrators close misconfigurations and harden endpoints before an adversary can misuse them.

What is PEASS-ng used for?

Authorized internal audits and hardening exercises on Linux, Windows, and macOS endpoints.

What are the strengths of PEASS-ng?
  • +Covers Linux, Windows, and macOS in one project with color-coded output.
  • +Actively maintained with frequent rule updates.
  • +Fast execution with no installation requirements on target systems.
What are the limitations of PEASS-ng?
  • +Can produce false positives on heavily customized systems.
  • +Output can be noisy without manual review and filtering.
  • +Some checks require local execution with sufficient privileges.
How is PEASS-ng used defensively?

Use PEASS-ng to find and remediate privilege escalation paths before external assessments.