Skip to content
New

DeepSeek V4.1 Flash free for 7 days: 10M tokens a day after a top-up of $10 or more. Until Nov 30.

How it works
noorqureshi/privesc-enumerationLinux, cloud and containers

privesc-enumeration

⁨Systematic post-foothold host enumeration and credential/loot hunting on Linux and Windows — build situational awareness and find the lead that escalates or moves laterally. Load the moment you land a shell and think "now what?". Signals: fresh foothold, low-priv user, "enumerate the box", "situatio⁩

v2026.10.14-ee0e0c53 installs+3 in 7 days27 StarsMITsynced 22 hours ago

Install

No NotHoly CLI yet? Install it first.

$ curl -fsSL https://notholy.com/install.sh | sh
$ notholy skills install noorqureshi/privesc-enumeration

Writes to ⁦~/.notholy/skills⁩ after checking the signature and the SHA-256.

SignatureSigned, ed25519
EDJX0lBIFP…oWzNyYAQ==The CLI checks the SHA-256 and the signature before it writes a file.
Packageef55b4b0…04b4fea2
ef55b4b0a9ab…f8ae04b4fea21 file · ⁦2.6 KB⁩
ScanLowno findings
The scan found nothing to flag in this version.See the full scan
Sourcegithub.com/NoorQureshi/security-skills/tree/main/skills/privesc/privesc-enumeration@ee0e0c5

When it applies

You have a shell as a low-privileged user and need to know what you're standing on and where to go next. This is the situational-awareness pass that precedes escalation: it surfaces the leads that privesc-arsenal (local privesc vectors) and ad-pivot-arsenal (domain) then exploit. On Windows run whoami /priv and on Linux sudo -l first — an enabled privilege or sudo rule is a shortcut past all of this.

Why it works

Machines leak their own secrets: config files hold DB and service passwords, history files record typed credentials, home directories and shares carry keys, and the OS records who runs what. A methodical sweep — then a targeted grep for secrets — finds the reused password or private key that turns one foothold into root/SYSTEM or the next host. Enumerate before you exploit; noise and dead ends come from skipping this.

Method

Work top-down; note every lead in notes.md and follow the strongest one.

1 · Who/where am I — id/whoami /all, groups (a docker/lxd/adm group or SeImpersonate/SeBackup privilege is often the whole game), hostname, OS/kernel/patch level (uname -a / systeminfo), and am-I-in-a-container (/proc/1/cgroup, /.dockerenv).

2 · Automated first pass (then read the output, don't scroll it): linpeas.sh > lp.txt / winPEASx64.exe, plus pspy64 (Linux, catches root cron without root) and Seatbelt.exe -group=all / PowerUp (Windows). Treat highlights as leads to verify.

3 · Users, processes, services, scheduled jobs — other users (/etc/passwd, net user), running processes and their owners (ps auxf / tasklist /v), services (esp. unquoted paths / weak perms on Windows), and cron/systemd-timers / scheduled tasks. A privileged process reading a file you can write is a lead.

4 · Network & internal reach — listeners bound to 127.0.0.1 (ss -tulnp / netstat -ano) are internal services to port-forward to; ARP/routes/extra NICs reveal a pivot (network-pivoting-tunneling).

5 · Hunt credentials & loot — the highest-yield step:

  • Config files: web roots and app configs (grep -ri "password\|DB_PASS\|secret" /var/www /opt 2>/dev/null), .env, wp-config.php, web.config, *.conf, connection strings.
  • History: ~/.bash_history, ~/.mysql_history, ~/.psql_history; Windows PowerShell history (ConsoleHost_history.txt).
  • Keys & secrets: find / -name id_rsa -o -name "*.pem" -o -name "*.key" 2>/dev/null, ~/.ssh/, cloud creds (~/.aws/credentials), Kubernetes ~/.kube/config, tokens.
  • Windows stores: cmdkey /list (+ runas /savecred), autologon/PuTTY/VNC in the registry, unattend.xml/sysprep.inf/GPP Groups.xml, netsh wlan show profile name=* key=clear, DPAPI/browser creds, and C:\Windows\System32\config\RegBack\ (SAM/SYSTEM copies).
  • Databases: local DB running as root/SYSTEM you can log into with found creds.

6 · Files of interest — recently modified files (find / -mmin -10), backups (*.bak/*.old), readable /etc/shadow, writable files/dirs in privileged paths, and Windows Alternate Data Streams (dir /r).

7 · Route the lead — cracked/found password → try it everywhere (reuse is rampant; network-password-spraying); crackable hash/keyfile → network-credential-cracking; escalation vector → privesc-arsenal; domain context → ad-pivot-arsenal.

Gotchas

  • Read linpeas/winPEAS output, don't drown in it — pipe to a file and grep the red/yellow flags.
  • Password reuse is the #1 pivot — always retry a found secret as other users/services/root (su, WinRM, SMB) before hunting harder.
  • noexec/nosuid mounts change what works — check mount before dropping a binary.
  • Enumerate quietly on a live/bounty-adjacent host — heavy find / and linpeas are noisy; pace them and stay in RoE.
  • Don't hoard — pull the one cred/keyfile that advances you into engagements/<target>/loot/, not whole home directories.

Verify success

A concrete next-step lead in hand — a working credential, a private key, an internal service to tunnel to, or a confirmed escalation vector — recorded with where it came from.

References

HackTricks (Linux/Windows local privesc checklists); PEASS-ng; pspy, Seatbelt. Exploit the leads with privesc-arsenal; domain leads with ad-pivot-arsenal.

Files in this version

Permissions

PermissionDeclaredFound by the scan
Reads filesNoNo
Writes filesYesYes
Runs shell commandsNoNo
Uses the networkNoNo
Uses connectorsNoNo
Drives a browserNoNo

Scan findings

Reviewed on Nov 13, 2026

The scan found nothing to flag in this version.

A clean scan lowers the risk but does not prove a package is safe. Read what you install.

VersionPublishedCommitSHA-256SignaturePermission change
v2026.10.14-ee0e0c5Nov 13, 2026ee0e0c5ef55b4b0Signed–

Ask anything your scope allows.

Create an account, add credits and ask the first question in the chat or the terminal.

  1. 1/3

    Create the account

    Individual or company. You can switch to a company later without losing balance or keys.

    IndividualCompany
  2. 2/3

    Add credits

    By card. Pay per token, no subscription.

    $5.00minimum deposit
  3. 3/3

    Ask

    In the chat, or install the CLI and run notholy login in your terminal.

    $ notholy login