Contents
PEASS-ng is a suite of scripts that look for settings that could be used for privilege escalation and print them in color. linPEAS (a shell script) covers Linux, Unix, and macOS. winPEAS (.exe, .bat, and .ps1) covers Windows. The advisory in the official README asks you to use the tools for authorized penetration testing or education, and only on your own machines or machines whose owner has given permission.
This review is for people who manage their own servers and PCs and want to check them first for weaknesses an attacker could find after getting in. After reading it, you can do the following:
- Know what PEASS-ng checks and how to read its output
- Know what traffic it sends outside and that the output file can contain secrets, then choose your options
- Know how to run linPEAS in a throwaway Linux environment, fix one finding, and run it again
This article was written on 2026-11-06 after checking the official repository’s README, LICENSE, source code, and releases.
What PEASS-ng does
According to the official README, PEASS-ng looks for local privilege escalation paths and prints them in color so misconfigurations are easy to spot. The linPEAS help lists what it examines: known vulnerabilities, users, process and file permissions, files with special permissions, readable and writable files, and passwords. With -r, it also searches the file system for strings that look like API keys for many services.
linPEAS comes in three variants.
| File | Contents |
|---|---|
linpeas.sh |
All checks. Of the third-party tools, only linux exploit suggester is embedded (the default) |
linpeas_fat.sh |
All checks. Other third-party tools are embedded too, as base64 |
linpeas_small.sh |
A smaller version with only the important checks |
According to the README, linPEAS is written in /bin/sh syntax and has no dependencies. It says the script was tested on Debian, CentOS, FreeBSD, OpenBSD, and macOS. If you run linpeas.sh on macOS, MacPEAS runs automatically. The latest release also includes Linux binaries such as linpeas_linux_amd64.
winPEAS comes as an .exe (it needs .NET 4.5.2 or later), a .bat, and a .ps1. The README says the .exe version is based on Seatbelt.
The colors help you read the output. The README explains them like this:
- Red and yellow: a setting that leads to privilege escalation
- Red: a suspicious setting that might lead to privilege escalation
- Green: a setting judged to be fine, but the judgment is based on the name, not the content
Green does not mean the content was checked, so don’t treat a green item as proof of safety. The README’s update notes also call the eBPF findings “candidates to review”, not evidence of compromise. Read the output as a guide to what to look at first.
According to the README, linPEAS by default writes nothing to disk and does not try su as other users. It does not carry out privilege escalation. It shows leads. However, -a adds a step that tries to brute-force each user with su (the README calls this step very noisy).
This review’s reading of the source does not match the README’s “writes nothing”. The host lookup (which -n stops) writes its response to ${TMPDIR:-/tmp}/linpeas_host_checker_<PID>.json (and a .err file). No code that deletes these files was found. This has not been confirmed on a real machine.
Network traffic
The linPEAS and winPEAS source code (release 20261105-ec02c390, commit 6c7340b) has the following code that sends data outside. What follows comes from reading the source. It has not been confirmed on a real machine.
- Host lookup (linPEAS): By this review’s reading of the source, a default run sends your host name to a third party’s server. If curl or wget is available, it starts sending the host name, the name
linpeas, and the version as JSON tohttps://tools.hacktricks.wiki/api/host-checker(HackTricks) at the start of theSystem Informationsection. Only-nstops it.-sdoes not. In a default run, whetherhttps://1.1.1.1is reachable in theInternet Access?section, and-s, only decide whether the result is displayed. They do not decide whether the data is sent. If you use-oto dropsystem_informationand keepnetwork_information, the start of the lookup is not embedded in the first section and begins from the display part of theInternet Access?section instead. In that case, the reachability of 1.1.1.1 and-salso become conditions for sending (from reading the source). The source describes the feature as checking whether the public IP and host name appear in known malicious lists or leaks. - Package list upload (linPEAS): With
-V, it also sends OS information and the package list to the same address. The help text says it sends the package and kernel inventory to HackTricks for an online vulnerability lookup.-aturns this on too. The default limit is 300 packages. The vulnerable packages that come back are shown with their CVE numbers, up to 50 packages. - Connectivity checks (linPEAS): In the source, the
Internet Access?section runs unless-oor the MITRE filter leaves it out, so it runs by default. It pings 1.1.1.1, sends a DNS query, connects tohttps://1.1.1.1with curl or wget, and connects to TCP ports 80 and 443 on104.18.74.230.-ndoes not stop these. The README, and the startup message that appears only with-a, say-tcalls the connectivity checks, which disagrees with the source. - Network scanning (linPEAS):
-truns an automatic scan of the local network and, according to the README, writes to files.-dlooks for machines with fping or ping.-p(used with-d) and-iconnect to ports on the machines you give, using nc. - Cloud sections (linPEAS): Some checks use curl or wget. Where they connect was not examined, so this is unverified.
- winPEAS: In the source, it starts a lookup before the checks begin that sends the host name and OS information to the same URL.
dont-check-hostnamestops it.-vulnpackages, or theallargument, also sends package names and versions.-linpeas=fetcheslinpeas.shand runs it in the default WSL distribution. The default source in the code is the GitHub release (github.com/carlospolop/PEASS-ng/releases/latest/download/linpeas.sh). The winPEAS (.exe) README saysraw.githubusercontent.com, which disagrees with the source.
How the tools are distributed and run also needs care. The first example in the linPEAS README is a single line that downloads linpeas.sh from the GitHub release with curl and pipes it straight to sh. The winPEAS README also shows downloading with PowerShell and running in memory. This form runs what it downloads without a look, so you can’t notice a tampered or wrong source. It also points to latest, so the version can change from run to run. The release API returns a SHA-256 (digest) for each file, so you can compare it with the hash of the file you downloaded before running it.
Beyond network traffic, there are three more effects to know before you use it.
- The output file can contain secrets: The README says the tools search for passwords and API keys. No official instruction on handling the output was found, so this is the site’s own view: treat the output as containing secrets. Save it with restricted permissions, don’t share it, and delete it when you are done. Change any password or key it finds.
- Legal position: Article 3 of Japan’s Unauthorized Computer Access Act says that no one may commit an unauthorized access act. Article 2, paragraph 4, items 1 and 2, define such an act as entering, through a telecommunication line, another person’s identification code (item 2: information or commands that get around the access control) into a computer that has an access control function, so that it can be used in a way the control restricts. Acts by the access administrator, and acts done with the administrator’s consent, are excluded; item 1 also excludes acts done with the consent of the user the identification code belongs to. The penalty in Article 11 is imprisonment of up to 3 years or a fine of up to 1 million yen. This article does not judge whether any single operation falls under the law. Use the tools only on your own machines or machines you have written permission to test.
- Security products can detect it: The winPEAS README explains that the obfuscated build exists to bypass some antivirus products. The linPEAS README has a section with the same intent. This reads as written on the assumption that detection can happen. Tell your administrator beforehand in case your own security products detect it and raise an alert. This article does not cover how to avoid detection.
The impact is set to “reaches others”. The “sends nothing out” standard does not fit. By this review’s reading of the source, even a default run with no options can send your host name to a third party’s server (HackTricks). -V and -a add the package list. The -t family of options connects to machines on the same network. Use it only inside your own environment. Passing -n stops the host name and package list from being sent. But -n does not stop the connectivity checks in the Internet Access? section, so to stop all traffic, run it in an environment with the network cut off.
Try it safely in a throwaway Linux environment and fix one finding
Start in a throwaway Linux environment you built yourself, such as a virtual machine or a container. For how to build one, see How to set up a safe test lab.
-
Log in to the throwaway environment as a regular user. Cut off outside network access or limit it to the host only.
-
Download
linpeas.shfrom the releases page. Don’t run it withcurl ... | sh. Save it as a file first. -
Compare the SHA-256 that GitHub returns with the hash of the file you downloaded.
gh api repos/peass-ng/PEASS-ng/releases/latest --jq '.assets[] | select(.name=="linpeas.sh") | .digest' sha256sum linpeas.shIf the two don’t match, don’t run it. The file is about 1.8 MB, too large to read in full. Check only that the code in “Network traffic” above does not run with the options you use.
-
Make the output file unreadable to other users and run with the option that stops the host name upload. The README says a run takes about 4 minutes.
umask 077 sh linpeas.sh -n -q > ~/linpeas-out.txt-nstops the host lookup, and-qhides the startup banner. Don’t add-aor-V.-ndoes not stop the connectivity checks in theInternet Access?section (connections to 1.1.1.1 and so on), so keep the network cut off as in step 1. -
Read the output in color. The README example uses
less -r.less -r ~/linpeas-out.txt -
Pick one red item. The README says each check is explained on book.hacktricks.wiki. Find out why it was flagged, then fix the permission or setting.
-
Run the same command again and compare to see whether the item is gone.
-
Delete the output file.
rm ~/linpeas-out.txt
Common uses
These are linPEAS options. The README’s list is out of date, so they were checked against the help text in the source. -h prints the list for your copy.
| Goal | Option |
|---|---|
| Stop the host lookup | -n |
| Skip time-consuming checks | -s |
| Limit the kinds of checks | -o system_information,users_information, comma separated |
| Turn off colors | -N |
| Hide the startup banner | -q |
| Run extra enumeration | -e |
| Search for strings that look like API keys (minutes to hours) | -r |
Run everything except -r (includes 1 minute of process monitoring, the su brute force, extra enumeration, and the package upload) |
-a |
| Send the package list for an online lookup | -V |
| Scan the network automatically (writes files) | -t |
The names you can pass to -o, according to the README’s list, are system_information, container, cloud, procs_crons_timers_srvcs_sockets, network_information, users_information, software_information, interesting_files, and api_keys_regex.
These are winPEAS (.exe) options.
| Goal | Option |
|---|---|
| Turn off colors | notcolor |
Write the result to out.txt |
log |
| Limit the kinds of checks | systeminfo userinfo, for example |
| Also check domain information | domain |
| Stop sending the host name | dont-check-hostname |
Send the package list for an online lookup (all turns it on too) |
-vulnpackages |
How it differs from Lynis and Vuls
Lynis and Vuls also check the inside of a server. They look from a different angle.
| PEASS-ng | Lynis | Vuls | |
|---|---|---|---|
| Purpose stated by the project | Look for leads to privilege escalation paths | Test your defenses and suggest hardening | List known vulnerabilities (CVEs) |
| Output | A long color-coded list (some CVEs with -V) |
Warnings, suggestions, a hardening index | CVE numbers and CVSS scores |
The PEASS-ng README describes its output as a display of the settings it found. In what was read, it has no list of improvement suggestions like Lynis. With -V it sends the package list to HackTricks and shows the CVEs that come back for up to 50 packages. That differs from Vuls, which looks up CVEs in a local database and adds CVSS scores. A realistic split is Lynis for configuration weaknesses, Vuls for package vulnerabilities, and PEASS-ng to check what is visible after an intrusion. This split is the site’s own view.
Cautions
- Use it only on machines you manage or have written permission to test. The official advisory also limits use to machines whose owner has given permission.
- Treat the output file as containing secrets. Don’t put it in a shared folder or paste it outside.
-aincludes thesubrute force. Even in your own environment, it can leave a large number of authentication log entries and lock accounts (the site’s view). Don’t use it for a normal audit.- To stop the host name upload, pass
-nand avoid-Vand-a.-ndoes not stop the connectivity checks (1.1.1.1 and so on). To stop traffic for certain, run it in an environment with the outside network cut off. - Security products can detect it. Tell your administrator beforehand.
- No statement that root is required was found in the official README. The tool seems to examine what the user who runs it can read (the site’s view).
- Colors are a guide. A red item is not always exploitable, and green does not mean the content was checked.
- Versions change often. When you compare against a previous result, use a file of the same version. The latest release is
20261105-ec02c390, dated 2026-11-05 (checked on 2026-11-06). - The README’s option list has fewer entries than the help text in the source.
-nand-Vwere missing from the README’s list.
Read next
Sources
- Official repository README (overview, platforms, advisory)github.com/peass-ng/PEASS-ng
- License (LICENSE text)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/LICENSE
- linPEAS README (variants, options, examples, color meanings)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/linPEAS/README.md
- winPEAS README (flavours)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/winPEAS/README.md
- winPEAS (.exe) README (.NET requirement, parameters, examples)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/winPEAS/winPEASexe/README.md
- Latest release (assets, version)github.com/peass-ng/PEASS-ng/releases/latest
- GitHub API: latest release response (SHA-256 digest of each asset)api.github.com/repos/peass-ng/PEASS-ng/releases/latest
- Source: linPEAS options and help (0_variables_base.sh)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/linPEAS/builder/linpeas_parts/linpeas_base/0_variables_base.sh
- Source: where the linPEAS host lookup starts (1_Operative_system.sh, System Information section)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/linPEAS/builder/linpeas_parts/1_system_information/1_Operative_system.sh
- Source: how linPEAS sections are assembled (linpeasBaseBuilder.py)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/linPEAS/builder/src/linpeasBaseBuilder.py
- Source: linPEAS package vulnerability output (21_Online_package_vulnerabilities.sh)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/linPEAS/builder/linpeas_parts/1_system_information/21_Online_package_vulnerabilities.sh
- Source: linPEAS host lookup (check_external_hostname.sh)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/linPEAS/builder/linpeas_parts/functions/check_external_hostname.sh
- Source: linPEAS Internet Access section (11_Internet_access.sh)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/linPEAS/builder/linpeas_parts/5_network_information/11_Internet_access.sh
- Source: winPEAS host and package lookup (HackTricksHostChecker.cs)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/winPEAS/winPEASexe/winPEAS/Info/NetworkInfo/HackTricksHostChecker.cs
- Source: winPEAS startup and parameters (Checks.cs)github.com/peass-ng/PEASS-ng/blob/20261105-ec02c390/winPEAS/winPEASexe/winPEAS/Checks/Checks.cs
- e-Gov Law Search: Act on Prohibition of Unauthorized Computer Accesslaws.e-gov.go.jp/law/411AC0000000128
- Lynis official repository README (Lynis's purpose)github.com/CISOfy/lynis
- Vuls official repository (Vuls's purpose)github.com/future-architect/vuls
Checked on 2026-11-06
Similar tools
Lynis
Impact Local onlyAn auditing tool for Linux and other Unix-like servers. It checks the system's configuration and lists warnings and suggestions for hardening. It runs on the server you are checking.
- Purpose
- Audit
- Type
- Command line
- Difficulty
- Intermediate
- License
- CopyleftGPL-3.0
- Category
- Defense and hardening / Vulnerability scanning
Metasploit Framework
Impact Can harm othersAn open-source penetration testing framework of modules that check whether a weakness can really be exploited. Use it only in a lab or with written permission.
- Purpose
- Offensive testing
- Type
- Command line
- Difficulty
- Advanced
- License
- PermissiveBSD-3-Clause
- Category
- Red teaming and C2 / Exploits and PoCs
osquery
Impact Local onlyA tool that lets you query the state of an operating system, such as running processes, listening ports, users, and startup items, with SQL.
- Purpose
- Defense
- Type
- Command line
- Difficulty
- Intermediate
- License
- Check termsApache-2.0 OR GPL-2.0-only
- Category
- Defense and hardening / Incident response
Vuls
Impact Reaches othersAn agentless vulnerability scanner that checks the packages installed on a server and lists the ones affected by known CVEs.
- Purpose
- Defense
- Type
- Command line
- Difficulty
- Intermediate
- License
- CopyleftGPL-3.0
- Category
- Vulnerability scanning
Wazuh
Impact Local onlyA free security platform (SIEM/XDR) that collects logs, configuration, and vulnerability data from agents on your endpoints and shows it all in one dashboard.
- Purpose
- Defense
- Type
- Self-hosted server
- Difficulty
- Advanced
- License
- CopyleftGPL-2.0(一部の構成要素は Apache-2.0)
- Category
- Vulnerability scanning / Forensics