What is Linux persistence?
Persistence is how an intruder makes sure their access survives a reboot, a password reset or a closed session. On Linux there is no single registry to check: it is spread over cron tables, systemd units, init scripts, shell startup files, SSH keys, sudo rules, PAM stacks, udev rules, package-manager hooks, the dynamic linker and more.
This tool reads all of those places from a collection or a disk export, lists every entry with what it runs, as whom and when, and flags the ones that deserve a look first. It works like Sysinternals Autoruns does on Windows, for Linux, offline.
How it separates the normal from the planted
- Package layer: with the dpkg database (/var/lib/dpkg), every file is checked against the package that installed it. Untouched packaged files are shown as information only; modified ones and files no package owns stand out.
- Command heuristics: downloads piped to a shell, reverse shells, decoded payloads, LD_PRELOAD, programs run from /tmp or hidden folders, history switched off.
- Mechanism checks: @reboot and every-minute cron jobs, drop-ins that change what a unit runs, NOPASSWD sudo rules, pam_exec, preloaded libraries, root SSH keys, keys that copy another key's comment.
- Cross-checks: the same program started by several mechanisms, the same key in several accounts, recent changes relative to the collection time, enablement from systemd wants links and rc links.
What it reads
- cron, anacron and at: /etc/crontab, /etc/cron.*, /var/spool/cron, /var/spool/at
- systemd: services, timers, sockets, paths, drop-ins, generators, user units and lingering
- SysV init scripts, rc links and rc.local
- Shell startup files: /etc/profile, /etc/profile.d, bashrc, zshrc and every user's dotfiles
- /etc/ld.so.preload and ld.so.conf.d
- SSH: authorized_keys, ~/.ssh/rc, sshd_config and its drop-ins
- Accounts and groups (passwd, group, shadow dates), sudoers and sudoers.d
- PAM stacks and modules (hashed against dpkg)
- udev rules, APT/dpkg/yum/dnf hooks, update-motd.d, XDG autostart, kernel module loading, network hooks, logrotate
Limits
- It reads files, not a running system: in-memory implants, kernel rootkits and running processes need memory forensics.
- Package checks use dpkg (Debian, Ubuntu and derivatives). On RPM systems everything is still parsed and flagged, but packaged and added files cannot be told apart.
- Binaries are not analysed: a modified /usr/sbin/sshd shows up only through the paths and units that start it. PAM modules are the exception: they are hashed against dpkg's checksums.
- A flag is a reason to look, not a verdict. Administrators do write @reboot jobs and NOPASSWD rules.
Questions
Are my files uploaded?
No. The page reads the files in your browser with JavaScript and a Web Worker; nothing is sent to a server. You can disconnect from the network after the page has loaded.
What should I collect?
/etc, /var/spool/cron, /var/spool/at, /var/lib/dpkg, /var/lib/systemd/linger, the systemd and udev folders under /usr/lib, and the dotfiles of /root and every home folder. The collection command above does exactly that, and UAC output or a folder exported from Disk Image Parser works too.
Can it handle several hosts at once?
Yes. Each top-level folder or archive that holds its own etc/ is treated as a host, with its own accounts and package database.
Why is a file from a package still listed?
Every entry is listed so the inventory is complete. Packaged files that match dpkg's checksums are marked as information; use "Hide packaged files" to focus on the rest.
Is this the same as rkhunter or chkrootkit?
No. Those run on the live host and look for known rootkit signatures. This tool inventories every persistence mechanism from a copy of the files, offline, and explains why an entry stands out.