T1037: Boot or Logon Initialization Scripts
Tactics: Persistence, Privilege Escalation. Platforms: ESXi, Linux, macOS, Network Devices, Windows.
Adversaries may use scripts automatically executed at boot or logon initialization to establish persistence.
MITRE's description
Adversaries may use scripts automatically executed at boot or logon initialization to establish persistence. Initialization scripts can be used to perform administrative functions, which may often execute other programs or send information to an internal logging server. These scripts can vary based on operating system and whether applied locally or remotely. Adversaries may use these scripts to maintain persistence on a single system.
Telemetry that detects it
- File Access
- File Metadata
- File Modification
- Process Creation
- Scheduled Job Creation
- Script Execution
- Service Metadata
- Windows Registry Key Modification
Mitigations
- Restrict File and Directory Permissions
- Restrict write access to logon scripts to specific administrators.
- Restrict Registry Permissions
- Ensure proper permissions are set for Registry hives to prevent users from modifying keys for logon scripts that may lead to persistence.
Groups documented using it
Procedure examples
- APT29 has hijacked legitimate application-specific startup scripts to enable malware to execute on system startup.
- APT41 used a hidden shell script in /etc/rc.d/init.d to leverage the ADORE.XSECbackdoor and Adore-NG rootkit.
- ArcaneDoor used malicious boot scripts to install the Line Runner backdoor on victim devices.
- Rocke has installed an "init.d" startup script to maintain persistence.
8 documented uses in all. These are a sample.
MITRE ATT&CK Enterprise 19.2. © 2026 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.