Skip to main content
Mallory
← Back to News
persistence-methoddetection-content-updatecommand-and-control-method

Elastic Details Detection of Linux Persistence Across Boot, PAM, Packages, and Containers

Attack Tradecraft · 8 sources · Updated 2mo ago · First seen Feb 11, 2025

Elastic Details Detection of Linux Persistence Across Boot, PAM, Packages, and Containers

Elastic Security Labs published a series of Linux detection-engineering guides covering attacker persistence through scheduled tasks, systemd units, shell profiles, XDG autostart, permission and account changes, SSH keys, SysV/Upstart/rc.local startup paths, dynamic MOTD scripts, udev rules, package-manager hooks, Git hooks, process capabilities, and system-binary hijacking. The research maps techniques to MITRE ATT&CK and uses the PANIX simulation tool to demonstrate how adversaries can retain access or launch reverse shells, while recommending endpoint, file-integrity, process, network, service-state, and syslog telemetry alongside Elastic rules, ES|QL, and OSQuery hunts.

The latest guidance highlights high-impact persistence through malicious PAM changes, DPKG/RPM lifecycle scripts, and dangerous Docker deployments. Defenders should monitor PAM and package-management paths, suspicious child processes and outbound connections, lifecycle-script execution, and container settings such as privileged mode, host PID namespaces, and sensitive host mounts. Elastic cautions that boot-time persistence may execute before endpoint agents collect process events, making early file-change detection and proactive hunting essential; organizations should also tune detections for legitimate administration and remove obsolete Upstart systems from production.

Who uses this technique?Get the actors, campaigns, and ATT&CK mapping behind it.
Get the tradecraft
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events
  1. Reported May 24, 20224y ago

    Elastic publishes scheduled-job unusual-location behavioral rule

    Elastic published the Linux behavioral protection rule "Scheduled Job Executing Binary in Unusual Location" (ID f2a52d42-2410-468b-9910-26823c6ef822). It detects systemd or cron-launched binaries and shell commands from atypical directories and is configured to terminate detected processes.

    protections-artifacts/behavior/rules/linux/persistence_scheduled_job_executing_binary_in_unusual_location.toml at main · elastic/protections-artifacts · GitHub
  2. Reported Jun 17, 20206y ago

    Elastic creates cron job creation or modification detection rule

    Elastic created the production Linux EQL rule "Cron Job Created or Modified" (ID ff10d4d8-fea7-422d-afb1-e5a2702369a9). The rule detects creation or rename activity in cron and anacron locations that could indicate persistence, privilege escalation, or scheduled command execution.

    detection-rules/rules/linux/persistence_cron_job_creation.toml at main · elastic/detection-rules · GitHub
  3. Reported Jun 17, 20206y ago

    Elastic creates shell configuration creation detection rule

    Elastic created the production Linux EQL rule "Shell Configuration Creation" (ID 28f6f34b-8e16-487a-b5fd-9d22eb903db8) to detect suspicious creation of system-wide, user, and root Unix shell configuration files used for persistence or privilege escalation.

    detection-rules/rules/linux/persistence_shell_configuration_modification.toml at main · elastic/detection-rules · GitHub
  4. Reported Jun 17, 20206y ago

    Elastic updates Linux persistence file-modification detection rule

    Elastic updated its production "Potential Persistence via File Modification" Linux FIM detection rule, which monitors sensitive persistence-related paths and excludes selected expected benign changes.

    detection-rules/rules/integrations/fim/persistence_suspicious_file_modifications.toml at main · elastic/detection-rules · GitHub
  5. Reported Jun 17, 20206y ago

    Elastic creates Linux persistence file-modification detection rule

    Elastic created the production EQL rule "Potential Persistence via File Modification" (ID 192657ba-ab0e-4901-89a2-911d611eee98) to detect updates to Linux files commonly abused for persistence and privilege escalation.

    detection-rules/rules/integrations/fim/persistence_suspicious_file_modifications.toml at main · elastic/detection-rules · GitHub
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, breaches, and observables Mallory has linked to this story. Indicator values are masked here and available in full in the app.

Open in app →

Malware

1 linked

Affected products

2 linked
DpkgDocker

Observables

2 linked

Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.

Do you run this?Get the adversaries, campaigns, and ATT&CK mapping behind this technique, with detections ready to deploy.
See Who Uses This Technique
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.