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.[1][2][3][4][5] 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.
Threat groups45th percentile · 55% of ATT&CK techniques have more threat groups attributed.
0
CampaignsNone recorded
CampaignsNone recorded · 54% of ATT&CK techniques have none either.
5
Tools & malware66th pct
Tools & malware66th percentile · 63% of ATT&CK techniques have fewer tools implementing them.
12
Detection rulesTop 21%
Detection rules79th percentile · 77% of ATT&CK techniques have fewer detection rules written.
Boot or Logon Autostart Execution MITRE reference T1547
45th pctamong all ATT&CK techniques for number of groups
1 group has been recorded using this technique. Newest first; each entry carries MITRE’s procedure text and a link to the group’s full record. Click a name to filter the rules below.
Has modified the Registry to maintain persistence.1
created 2025-01-081 reference
All 1 groups for this technique
5 software entries are documented implementing this technique. MITRE files each as a tool or as malware; newest first, then by how many groups carry them.
Has added persistence via the Registry key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows\load which causes the malware to run each time any user logs in.1
Established persistence by setting the HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows\load registry key to point to its executable.1
Has created registry keys for persistence, including HKCU\Software\bkfouerioyou, HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{6afa8072-b2b1-31a8-b5c1-{Unique Identifier}, and HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{3BF41072-B2B1-31A8-B5C1-{Unique Identifier}.1
Has created registry keys for persistence, including HKCU\Software\dnimtsoleht\StubPath, HKCU\Software\snimtsOleht\StubPath, HKCU\Software\Backtsaleht\StubPath, HKLM\SOFTWARE\Microsoft\Active Setup\Installed. Components\{3bf41072-b2b1-21c8-b5c1-bd56d32fbda7}, and HKLM\SOFTWARE\Microsoft\Active Setup\Installed Components\{3ef41072-a2f1-21c8-c5c1-70c2c3bc7905}.1
created 2017-05-31MALWARE
All 5 software entries for this technique
Offense vs defense T1547
Compare defenses against adversary use. Eight counts, ranking this technique against the entire ATT&CK Enterprise matrix. Attack sits left, defense right.
Range
Technique Campaign use over its cumulative rule count.
Boot or Logon Autostart Execution detection strategy DET0274
MITRE names one behaviour worth catching for this technique and breaks it into 3 analytics, one per platform. Each carries the log sources it needs and the fields you tune per environment.
Boot or Logon Autostart Execution Detection Strategy
Enterprise
3 platforms
AN0764 · Windows
Correlation of registry key modification for Run/RunOnce with abnormal parent-child process relationships and outlier execution at user logon or system startup
Log sources
The data this analytic draws on. You do not need every component — each one you already collect covers part of it. Each links to its ATT&CK record.
MITRE calls these the analytic’s mutable elements: the thresholds and filters you set for your own environment.
Field
What you tune
PlistKey
Organizations may use specific keys or additional payload parameters
TimeWindow
Tunable based on expected delay between plist write and execution
Tests3Executorscommand_prompt 2 · powershell 1Need elevation1 of 3Have prerequisites0Have cleanup1Platformswindows
#
Test
Platform
Executor
Elevation
Prereqs
Cleanup
Ref
01
Add a driver
windows
command_prompt
—
—
—
Install a driver via pnputil.exe lolbin
Inputs
Name
Description
Type
Default Value
driver_inf
A built-in, already installed windows driver inf
path
C:\Windows\INF\usbstor.inf
Attack Commandsrun with command_prompt
pnputil.exe /add-driver "#{driver_inf}"
GUIDcb01b3da-b0e7-4e24-bf6d-de5223526785
02
Driver Installation Using pnputil.exe
windows
powershell
—
—
—
pnputil.exe is a native command-line utility in Windows to install drivers, this can be abused by to install malicious drivers. Ref: https://lolbas-project.github.io/lolbas/Binaries/Pnputil/
Inputs
Name
Description
Type
Default Value
driver_path
Enter the driver file path to install (Default is used built-in windows driver - acpipmi.inf)
path
C:\Windows\INF\acpipmi.inf
Attack Commandsrun with powershell
pnputil.exe -i -a #{driver_path}
GUID5cb0b071-8a5a-412f-839d-116beb2ed9f7
03
Leverage Virtual Channels to execute custom DLL during successful RDP session
windows
command_prompt
Required
—
Yes
Virtual Channels can be leveraged to alter RDP behavior using dedicated Addins.The mechanism is implemented using DLLs which can be executed during RDP session automatically.
The DLLs are loaded in the host system only after successful connection is established with the remote system.
Once the test is run, amsi.dll will be loaded on the host system during successful RDP session.
Blog :https://learn.microsoft.com/en-us/windows/win32/termserv/terminal-services-virtual-channels?redirectedfrom=MSDN
Inputs
Name
Description
Type
Default Value
dll_inf
custom DLL to be executed
Path
C:\Windows\System32\amsi.dll
Subkey_Added
New Sub key added in the registry path
String
Malware
Attack Commandsrun with command_promptelevation required (root or admin)
reg add "HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\Addins\#{Subkey_Added}" /v Name /t REG_SZ /d "#{dll_inf}" /f
Cleanup Commands
reg delete "HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\Addins\#{Subkey_Added}" /f
The following analytic detects potential persistence using a systemd generator on Linux, which involves creating a malicious script or binary that is typically executed during the system's boot process. (...)
The following analytic detects the creation of a .desktop file within XDG autostart directories, including the system-wide /etc/xdg/autostart and user-local ~/.config/autostart paths. (...)