Loading story…
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.
Get the actors, campaigns, and ATT&CK mapping behind it.
5 events from the most recent confirmed update back to the earliest known activity.
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.
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.
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.
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.
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.
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.
Indicator values are masked on this page. See the values in Mallory Domains, IPs, hashes, and URLs are exportable to your SIEM.
Get the adversaries, campaigns, and ATT&CK mapping behind this technique, with detections ready to deploy.
8 references tracked. Mallory keeps watching after this page renders.
elastic.co
Open sourceelastic.co
Open sourceelastic.co
Open sourcegithub.com
Open sourceredhat.com
Open sourcegithub.com
Open sourcegithub.com
Open sourcegithub.com
Open sourceMap indicators from this story to your assets and identify affected systems in minutes.
Every observed campaign, victim, and pivot linked to actors named in this story.
Malware, exploits, and IOCs connected to the activity described here.
YARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Get matching new stories delivered to your team as they break — not the next morning.
Ask questions about this story and take action on the answers.
Other stories Mallory is tracking that overlap on entities, sources, or topic labels.
A series of DFIR case studies documented how attackers are increasingly relying on living-off-the-land techniques, uncommon runtimes, and legitimate administration tools to maintain access while evading detection. On Windows, investigators dissected a PHP backdoor that used `php-win.exe`, a scheduled task named **ClockLauncher**, and a **ClockSystemService** service to fetch and execute second-stage code invisibly; a separate intrusion used mailbombing and Microsoft Teams vishing to deliver a modular **Deno**-based RAT and proxy that persisted via the `HKCU\Run` key and communicated over WebSocket infrastructure hosted behind CloudFront. Another investigation traced a malicious `.lnk` file to a WebDAV-hosted **Remcos** payload cached under `TfsStore\Tfs_DAV`, while repeated compromises of a vulnerable **Kentico CMS** server led to webshell deployment, SEO spam, PowerShell-based payload retrieval, and installation of a malicious IIS module, **HTTPCacheLog**, that accepted commands through HTTP cookies. On Linux and cloud infrastructure, researchers showed how attackers abused both commodity malware and stealthier post-exploitation tooling. TeamTNT-linked activity used **tmate** as a covert backdoor on Linux servers, often without normal login traces, while analysis of the **REPTILE 2.0** rootkit loader showed it bypassing `insmod` by decrypting an embedded kernel module and loading it directly with the `init_module` syscall. A separate **Sysrv** botnet infection established cron persistence, masqueraded as `kthreaddk`, and included exploitation and brute-force features for propagation. In AWS, an extortion actor deleted S3 buckets and supplied a fake Linux “recovery” binary that merely simulated restoration rather than recovering cloud data. Across the investigations, defenders were urged to hunt for recurring artifacts such as scheduled tasks, Run keys, suspicious services, unusual binaries in user-writable paths, outbound SSH or WebSocket traffic, and syscall-level module loading, using telemetry and tools including **Velociraptor**, AutoRuns, Sysmon, and CloudTrail.
Aug 1, 2026
Security content from Elastic and Splunk highlights two Linux behaviors that defenders should monitor closely: unauthorized privilege escalation through `setuid` execution and deletion of web server access logs. Splunk published an anomaly detection for Linux `auditd` that flags `execve` syscall 59 events where a non-root user gains effective UID 0 without a matching successful PAM authentication event in the same audit session, a pattern associated with privilege escalation and mapped to MITRE ATT&CK `T1068`; the rule also references `CVE-2026-46331` and notes that some scheduled tasks can produce false positives. Elastic separately documented a prebuilt rule for detecting deleted web server access logs, while ThreatBear provided tuning guidance showing how legitimate activity on Mitel MiCollab systems can create noisy process trees and trigger alerts such as suspicious Java child processes and logfile deletion detections. The combined guidance underscores that Linux monitoring programs should pair coverage for high-risk behaviors with environment-specific exceptions so defenders can preserve visibility into real attacks without overwhelming analysts with benign alerts.
Jul 31, 2026
Splunk published new endpoint detections for suspicious changes to Linux EFI boot components that could indicate **bootkit installation**, firmware-level persistence, or tampering with the system boot chain. One analytic flags deletion of `.efi` files in `/boot/efi/EFI/BOOT/`, while another monitors processes that modify files in the EFI boot volume using EDR telemetry such as process GUIDs, parent-child relationships, and full command-line logging. Splunk said both behaviors are unusual in normal operations, though legitimate administrator activity, package updates, OS reinstalls, and tools such as `grub` or `shim` may generate false positives. The detections map to MITRE ATT&CK **Pre-OS Boot** techniques `T1542.001` and `T1542.003`, which cover malicious changes to system firmware and bootkits that execute before the operating system loads. MITRE notes that attackers can persist by overwriting legacy BIOS boot records such as the **MBR** or **VBR**, or by creating or modifying files in the **EFI System Partition (ESP)** on UEFI systems so attacker-controlled code runs during boot. Splunk also linked the bootloader-modification analytic to `CVE-2024-7344`, underscoring concern that EFI boot artifacts remain a high-value target for stealthy persistence and difficult-to-remediate compromise.
Aug 12, 2026