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
Windows can start programs on its own when a user logs in.
In short
Windows can start programs on its own when a user logs in. Attackers add their own program to the places that control this, the Registry run keys or the Startup folder. The program then starts again after every restart or logon.
Windows has set places where it looks for programs to launch at logon. These include certain Registry run keys and the Startup folders.
An attacker adds an entry to one of these places that points to their own program. When the user next logs in, Windows starts it with that user’s permission level.
This is a normal operating system feature, so the attacker does not need any special tool to use it. MITRE places it under persistence and privilege escalation, as part of the wider group of boot or logon autostart methods.
Monitor the creation and change of Registry entries in the Run and startup locations.
Pay extra attention when a new entry points to an odd file location or to a script instead of a normal installed program.
Link the change to the process that follows. Programs started from non-standard folders, or with strange parent and child relationships, deserve a closer look.
File Creation, Process Creation, Windows Registry Key Modification
MITRE states that this technique cannot be easily stopped with preventive controls, because it abuses normal system features.
Since blocking is hard, the practical defense is to watch the startup locations and review new entries, as described above.
They are set places where Windows looks for programs to launch at logon. Attackers add an entry that points to their own program, which then starts when the user next logs in.
It is a normal operating system feature, so the attacker needs no special tool. The program starts again after every restart or logon with that user's permission level.
Monitor creation and change of Registry entries in the Run and startup locations. Pay extra attention to entries pointing to odd file locations or scripts, and link the change to the process that follows.
MITRE states it cannot be easily stopped with preventive controls because it abuses normal system features. The practical defense is to watch the startup locations and review new entries.
Take control of your digital security with an exclusive demo of our AI-driven threat intelligence platform.