Adversaries may use scripts automatically executed at boot or logon initialization to establish persistence.[1][2] 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. Depending on the access configuration of the logon scripts, either local credentials or an administrator account may be necessary.
An adversary may also be able to escalate their privileges since some boot or logon initialization scripts run with higher privileges.
ID | Name | Description |
---|---|---|
G0016 | APT29 |
APT29 has hijacked legitimate application-specific startup scripts to enable malware to execute on system startup.[1] |
G0096 | APT41 |
APT41 used a hidden shell script in |
G0106 | Rocke |
Rocke has installed an "init.d" startup script to maintain persistence.[2] |
S1078 | RotaJakiro |
Depending on the Linux distribution and when executing with root permissions, RotaJakiro may install persistence using a |
ID | Mitigation | Description |
---|---|---|
M1022 | Restrict File and Directory Permissions |
Restrict write access to logon scripts to specific administrators. |
M1024 | 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. |
ID | Data Source | Data Component | Detects |
---|---|---|---|
DS0026 | Active Directory | Active Directory Object Modification |
Monitor for changes made in the Active Directory that may use scripts automatically executed at boot or logon initialization to establish persistence. |
DS0017 | Command | Command Execution |
Monitor executed commands and arguments that may consist of logon scripts for unusual access by abnormal users or at abnormal times. |
DS0022 | File | File Creation |
Monitor for newly constructed files that may use scripts automatically executed at boot or logon initialization to establish persistence. |
File Modification |
Monitor for changes made to files that are modified by unusual accounts outside of normal administration duties. |
||
DS0009 | Process | Process Creation |
Monitor for newly executed processes that may use scripts automatically executed at boot or logon initialization to establish persistence. Adversaries may schedule software to run whenever a user logs into the system; this is done to establish persistence and sometimes for lateral movement. This trigger is established through the registry key Analytic 1 - Boot or Logon Initialization Scripts
|
DS0024 | Windows Registry | Windows Registry Key Creation |
Monitor for newly constructed windows registry keys that may use scripts automatically executed at boot or logon initialization to establish persistence. |