Article
GRU targeting of logistics firms: advisory AA25-141A
CISA, NSA, FBI and partners describe a GRU campaign against Western logistics and technology firms: targets, phases, CVEs and the fixes they list.
Quick links
Press Enter to search, Esc to close
Attack technique
Boot or logon autostart execution is when an attacker sets up a computer so that their program starts by itself when the system boots or a user logs on.
In short
Boot or logon autostart execution is when an attacker sets up a computer so that their program starts by itself when the system boots or a user logs on. This lets the attacker stay on the system after a restart. Some of these startup items run with higher privileges, so it can also help the attacker gain more control.
Operating systems have built-in ways to run programs automatically at boot or logon. Some use special folders. Others use settings stored in configuration databases, such as the Windows Registry.
An attacker who has access to a system can add their own program to one of these places. The program then starts again every time the system boots or the user logs on, even after a restart.
An attacker can also change or extend parts of the operating system kernel to get the same result. Because some startup programs run with higher privileges, this can also be used to gain higher-level access.
The technique covers Windows, macOS, Linux and network devices. MITRE lists 14 sub-techniques that cover the different mechanisms.
MITRE lists 14 sub-techniques: T1547.001 Registry Run Keys / Startup Folder; T1547.002 Authentication Package; T1547.003 Time Providers; T1547.004 Winlogon Helper DLL; T1547.005 Security Support Provider; T1547.006 Kernel Modules and Extensions; T1547.007 Re-opened Applications; T1547.008 LSASS Driver; T1547.009 Shortcut Modification; T1547.010 Port Monitors; T1547.012 Print Processors; T1547.013 XDG Autostart Entries; T1547.014 Active Setup; T1547.015 Login Items.
Procedure examples listed by MITRE ATT&CK:
Look for new or changed entries in the places that start programs at boot or logon, such as Windows Registry autostart settings. Compare them with abnormal parent and child process patterns at logon or startup.
Look for new or changed service definition files and boot scripts, and for unusual process behavior during boot.
Look for new or changed launch agent and launch daemon configuration files, followed by unusual programs running after a user logs on.
DET0274, Boot or Logon Autostart Execution Detection Strategy.
MITRE notes this technique is hard to stop with preventive controls, because it abuses normal system features.
Because blocking is hard, monitor autostart locations and startup behavior so unexpected changes are noticed quickly.
It is a technique where an attacker sets up a computer so their program starts by itself when the system boots or a user logs on. It lets the attacker stay on the system after a restart, and some startup items run with higher privileges.
MITRE says it covers Windows, macOS, Linux and network devices. It lists 14 sub-techniques that cover the different mechanisms, including special folders and settings stored in configuration databases such as the Windows Registry.
Look for new or changed entries in the places that start programs at boot or logon, such as Windows Registry autostart settings. On Linux watch service definition files and boot scripts, and on macOS watch launch agent and launch daemon configuration files.
Only to a limited degree. MITRE notes this technique is hard to stop with preventive controls because it abuses normal system features. Because blocking is hard, monitor autostart locations and startup behavior so unexpected changes are noticed quickly.
Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.