Applied Cybernetics Group
T1547 Boot or Logon Autostart Execution
- Technique
T1547- Tactics
- Persistence, Privilege Escalation
- Research, 90 days
- 1
- KEV CVEs mapped
- 1
- SigmaHQ rules
- 7
- Elastic, Splunk
- 57
- thrunt rules
- 0
- Upstream
- https://attack.mitre.org/techniques/T1547
MITRE description
Adversaries may configure system settings to automatically execute a program during system boot or logon to maintain persistence or gain higher-level privileges on compromised systems. Operating systems may have mechanisms for automatically running a program on system boot or account logon.(Citation: Microsoft Run Key)(Citation: MSDN Authentication Packages)(Citation: Microsoft TimeProvider)(Citation: Cylance Reg Persistence Sept 2013)(Citation: Linux Kernel Programming) These mechanisms may include automatically executing programs that are placed in specially designated directories or are referenced by repositories that store configuration information, such as the Windows Registry. An adversary may achieve the same goal by modifying or extending features of the kernel. Since some boot or logon autostart programs run with higher privileges, an adversary may leverage these to elevate privileges.
KEV CVEs mapped to this technique
MITRE CTID maps these KEV CVEs to this technique by hand. They are the actively exploited vulnerabilities behind this technique's KEV signal.
Research citing this technique
Reports and advisories from the last 90 days that cite this technique.
-
2026-08-13Recorded Future Insikt: Malware Crypting Services and the Threat Actors Who Sell Them
Detection coverage
SigmaHQ community rules
- Startup/Logon Script Added to Group Policy Object (core)
- Potential RipZip Attack on Startup Folder (core)
- Suspicious Driver Install by pnputil.exe (core)
- Suspicious GrpConv Execution (core)
- Registry Persistence Mechanisms in Recycle Bin (core)
- WINEKEY Registry Modification (core)
- Atbroker Registry Change (core)
Elastic and Splunk rules
- Potential Persistence via File Modification (elastic)
- Persistence via a Hidden Plist Filename via macOS Security Events (elastic)
- Kernel Module Removal (elastic)
- Pod or Container Creation with Suspicious Command-Line (elastic)
- Suspicious Usage of bpf_probe_write_user Helper (elastic)
- BPF Program or Map Load via bpftool (elastic)
- Kernel Module Load via Built-in Utility (elastic)
- KDE AutoStart Script or Desktop File Creation (elastic)
- Kernel Driver Load (elastic)
- Kernel Driver Load by non-root User (elastic)
- Kernel Module Load from Unusual Location (elastic)
- Kernel Object File Creation (elastic)
- Suspicious File Creation via Kworker (elastic)
- Loadable Kernel Module Configuration File Creation (elastic)
- Executable Bit Set for Potential Persistence Script (elastic)
- Tainted Kernel Module Load (elastic)
- Kernel Module Loaded with Tainting Flags (elastic)
- Tainted Out-Of-Tree Kernel Module Load (elastic)
- Network Connections Initiated Through XDG Autostart Entry (elastic)
- Kernel Load or Unload via Kexec Detected (elastic)
- Attempt to Unload Elastic Endpoint Security Kernel Extension (elastic)
- Creation of Hidden Login Item via Apple Script (elastic)
- Authorization Plugin Modification (elastic)
- Persistence via DirectoryService Plugin Modification (elastic)
- Persistence via Docker Shortcut Modification (elastic)
Showing 25 of 57.