>systemctl

Systemctl controls the systemd system and service manager. Sudo privileges on systemctl allow linking or creating transient unit files that execute root commands upon service start.

Default Executable Paths

/bin/systemctl
/usr/bin/systemctl

Integrity & Metadata

Original Name: systemctl
File Version: systemd
Category Count: 1 weaponized patterns
Forensics & Triage Insight

Attackers create a temporary .service file pointing ExecStart to an implant and start it via systemctl.

Detection Engineering Notes

Monitor systemctl execution linking or starting services located in /tmp, /dev/shm, or user home directories.

Executive Summary & AI Quick Reference

High-Fidelity Telemetry Profile

systemctl is a native utility pre-installed on Linux systems. Threat actors and red teams abuse systemctl as a Living-off-the-Land Binary (LOLBin) to achieve Persistence without triggering traditional antivirus file-hash alerts. Legitimate system administrators use it for routine administration, making behavioral command-line telemetry essential for differentiation.

Primary Abused Tactics
Persistence
Minimum Privilege
Root
Key Telemetry Source
auditd EXECVE
ATT&CK Mapping
T1543.002

Weaponized Parameters & Proof-of-Concepts

Documented attack commands, parameter flags, and privilege prerequisites.

1 documented methods
Filter Purpose:
PersistencePrivileges: Root
T1543.002: Systemd Service

Links an arbitrary systemd service file located in a temporary directory and starts it with root privileges.

systemctl link /tmp/malicious.service && systemctl start malicious

SIEM & EDR Detection Rules

Production telemetry rules configured for Microsoft Defender, Sigma, and Splunk.

Telemetry & SIEM Detection Suite (systemctl)

Validated against MITRE T1543.002
systemctl Microsoft Defender Querykql
1DeviceProcessEvents | where FileName =~ "systemctl" | where ProcessCommandLine has_any ("link", "enable") and ProcessCommandLine has_any ("/tmp/", "/dev/shm/", "/home/") | project Timestamp, DeviceName, AccountName, ProcessCommandLine

Mitigation, Hardening & Prevention

Recommended defensive controls to block or constrain systemctl abuse.

Application Whitelisting

Audit and remove unnecessary SUID / SGID bits (`chmod u-s /path/to/$systemctl`) and restrict sudoers NOPASSWD execution grants.

Attack Surface Reduction

Implement AppArmor or SELinux profiles restricting systemctl network socket creation and read access to sensitive user directories.

Behavioral Alerting

Deploy the KQL, Sigma, and Splunk detection queries below. Alert on anomalous child processes, web requests to unrated external IPs, or encoded payload strings.

Frequently Asked Questions (FAQ) • systemctl

Key operational questions and defensive answers about systemctl LOLBin tradecraft.

What is systemctl and why is it classified as a LOLBin?

systemctl is a legitimate, pre-installed or trusted utility on Linux. It is classified as a Living-off-the-Land Binary (LOLBin) because adversaries abuse its built-in functionality to perform malicious operations—such as Persistence—without dropping custom malware binaries on disk.

How do threat actors abuse systemctl in cyber intrusions?

Adversaries leverage systemctl to execute stealthy actions while evading signature-based security controls. For example, attackers execute commands like "systemctl link /tmp/malicious.service && systemctl start malicious" to achieve Persistence, masquerading behind legitimate system process lineage.

How can SOC analysts detect suspicious systemctl activity?

Detection engineers monitor process creation events (Windows Event ID 4688 or Sysmon Event ID 1; Linux auditd EXECVE; macOS Endpoint Security) inspecting anomalous command line arguments, unusual parent-child process relationships (e.g. Office apps or web servers spawning systemctl), and unexpected network connections.

What MITRE ATT&CK techniques does systemctl map to?

systemctl maps to MITRE ATT&CK technique(s): T1543.002. These techniques cover adversary actions across tactics such as Defense Evasion, Execution, Persistence, and Command and Control.

How can organizations mitigate and restrict systemctl?

Mitigation strategies include implementing Application Control policies (AppLocker or Windows Defender Application Control - WDAC), enforcing Attack Surface Reduction (ASR) rules, configuring strict privilege separation (disallowing standard users from running sensitive switches), and alerting on execution from non-standard directories.

Sharon Ben Moshe
Curated & Verified by
Sharon Ben Moshe
Cybersecurity Researcher & Detection EngineerCheck Point