Tool Files & Artifacts
Linux Persistence Reader
Read a crontab line, a systemd unit or an auditd record, and see what runs, when, and as whom.
On Linux, persistence usually comes down to three questions: what runs, when, and as whom. This page answers them for a crontab line, a systemd unit, or an auditd record.
This runs in your browser. Nothing you type or open is uploaded.
How to read it
In a systemd unit, read ExecStart and User first, then the WantedBy line that decides when it starts.
A cron line runs as the user whose crontab holds it, unless it sits in /etc/crontab or /etc/cron.d, where the sixth field names the user.
An auditd record splits across several lines with one serial number. Read them together, and compare auid with uid, since auid keeps the original login even after sudo.
Tab by tab
auditd and systemd
An auditd record or a systemd unit is a list of terse fields where one or two matter. This annotates each field and points at the ones worth a second look.
In auditd, uid and euid are who the process runs as now. auid is the account that logged in, and the kernel keeps it across su and sudo. So auid=1000 uid=0 means user 1000 became root, and 1000 is the number that names a person.
An auid of 4294967295 means no login session at all: a daemon, a service, or something started outside a login.
In a unit file, ExecStart is the whole story, and ExecStartPre runs before it with the same privileges. A second command hidden there is easy to skip.
Cron
A cron expression is five fields, and a malicious one hides well in a crontab full of ordinary jobs. This reads one back in plain English, or builds one field by field.
Paste an expression, pick a common schedule, or switch to Build. The tool follows the crontab(5) grammar from cronie, a practical superset of POSIX that adds names and step values.
When both day-of-month and day-of-week are restricted, cron runs the job when either one matches, not both. That trap is the most common misread.
@reboot runs once when cron starts. It is a favorite for persistence because it never appears in a time-based review.
| Field | Allowed values |
|---|---|
| Minute | 0-59 |
| Hour | 0-23 |
| Day of month | 1-31 |
| Month | 1-12 or Jan-Dec |
| Day of week | 0-7 (0 and 7 are both Sunday) or Sun-Sat |
Terms behind it
- cron and systemd Timers: Time-based job schedulers on Unix and a classic persistence and execution vector.
- auditd: The Linux kernel audit subsystem's user-space logging daemon.
- Persistence Mechanism: The means malware uses to survive reboots and keep running.
- LD_PRELOAD Hijacking: Forcing a malicious shared library to load first so it overrides legitimate functions.
- systemd Journal: Structured, indexed binary log managed by systemd-journald on modern Linux.
Sources
- cronie's crontab(5) man page (man7.org). The crontab(5) documentation for cronie (the crond most Linux distributions ship), and the actual source this page's field grammar (names, step values, the day-of-month/day-of-week OR rule, the 0-7 day-of-week range, and the 7 '@'-nickname extensions) was verified against.
- The Open Group Base Specifications: crontab utility (POSIX). The narrower POSIX crontab specification this page contrasts its own (wider, cronie-based) grammar against: numeric-only fields, day-of-week strictly 0-6, and no step values or names at all.
Worth using too
- crontab.guru. Cronitor's well-known interactive cron editor: a quick second opinion alongside this page's own parser, plus a library of common schedule examples worth skimming for inspiration.