pspy
Observe short-lived Linux processes and filesystem activity without root. Use to correlate scheduled jobs, process arguments, and timestamps.
v2026.11.13-21cd5683 installs+3 in 7 days39 StarsMITsynced 10 hours ago
Install
No NotHoly CLI yet? Install it first.
$ curl -fsSL https://notholy.com/install.sh | sh$ notholy skills install aeondave/pspyWrites to ~/.notholy/skills after checking the signature and the SHA-256.
SignatureSigned, ed25519
Package9cc3816c…34878ea9
9cc3816c108c…337b34878ea91 file · 1.2 KBScanLow1 finding
- Links to outside domains
Sourcegithub.com/AeonDave/malskill/tree/main/offensive-tools/linux/pspy@21cd568
Observe process execution through procfs scans triggered by polling and inotify events. Capture timestamp, UID, PID, and command line; missed events remain possible.
Workflow
- Select the correct architecture.
pspy32/pspy64are static; the smallersvariants depend on libc. Check the downloaded binary's help. - Choose an observation window from the job schedule or reproducer. Start with process output; enable filesystem output only when it answers the question.
- Save the log, correlate events with the triggering action, and stop after the needed observation.
./pspy64 --help
./pspy64 -p -i 1000 > process-observations.log
# Process output plus filesystem events; interval is milliseconds
./pspy64 -pf -i 1000
# Recursive watches versus a single directory without its children
./pspy64 -r /var/www -d /tmp| Option | Meaning |
|---|---|
-p |
Print process commands; enabled by default |
-f |
Print filesystem events; disabled by default |
-i N |
Periodic procfs scan interval in milliseconds |
-r DIR |
Recursive inotify watch; repeat for multiple roots |
-d DIR |
Non-recursive watch; repeat for multiple directories |
--debug |
Include normally hidden errors |
Interpret correctly
- Inotify triggers a scan; it is not an audit record of every execution. Short-lived processes can still be missed.
- Procfs visibility depends on mount settings, namespaces, and permissions. An empty log does not prove inactivity.
- Broad watches consume inotify resources; inspect startup watch lists and errors before expanding them.
- Lower polling intervals increase overhead. Measure whether a shorter interval captures the missing event.
- Keep logs private: command arguments may contain secrets. Record the observation window and visibility limits with the result.
Sources: upstream usage, v1.2.1 release.
Files in this version
- SKILL.md2.3 KB
Permissions
| Permission | Declared | Found by the scan |
|---|---|---|
| Reads files | No | No |
| Writes files | Yes | Yes |
| Runs shell commands | Yes | Yes |
| Uses the network | Yes | Yes |
| Uses connectors | No | No |
| Drives a browser | No | No |
Scan findings
Reviewed on Nov 13, 2026
- InfoLink · Links to outside domains
A clean scan lowers the risk but does not prove a package is safe. Read what you install.
| Version | Published | Commit | SHA-256 | Signature | Permission change |
|---|---|---|---|---|---|
| v2026.11.13-21cd568 | Nov 13, 2026 | 21cd568 | 9cc3816c | Signed | – |
More from AeonDave
All from this publisherMore in Linux, cloud and containers
See the category- detecting-aws-credential-exposure-with-trufflehogmukul975/detecting-aws-credential-exposure-with-trufflehog5
- cloud-gcpnoorqureshi/cloud-gcp4
- container-image-hardeningsecurityskills/container-image-hardening3
- performing-cloud-incident-containment-proceduresmukul975/performing-cloud-incident-containment-procedures3
- implementing-taxii-server-with-opentaxiimukul975/implementing-taxii-server-with-opentaxii3
- detecting-cryptomining-in-cloudmukul975/detecting-cryptomining-in-cloud3
Ask anything your scope allows.
Create an account, add credits and ask the first question in the chat or the terminal.
- 1/3
Create the account
Individual or company. You can switch to a company later without losing balance or keys.
IndividualCompany - 2/3
Add credits
By card. Pay per token, no subscription.
$5.00minimum deposit - 3/3
Ask
In the chat, or install the CLI and run notholy login in your terminal.
$ notholy login