T1547.001 Registry Run Keys / Startup Folder — ATT&CK Technique
Adversaries may achieve persistence by adding a program to a startup folder or referencing it with a Registry run key. Adding an entry to the "run keys" in the Registry or startup folder will cause the program referenced to be executed when a user logs in. These programs will be executed under the context of the user and will have the account's associated permissions level. The following run keys are created by default on Windows systems: * HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run * HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunOnce * HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run * HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnce Run keys may exist under multiple hives. The HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunOnceEx is also available but is not created by default on Windows Vista and newer. Registry run key entries can reference programs directly or list them as a dependency. For example, it is possible to load a DLL at logon using a "Depend" key with RunOnceEx: reg add HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\RunOnceEx\0001\Depend /v 1 /d "C:\temp\evil[.]dll" Placing a program within a startup folder will also cause that program to execute when a user logs in. There is a startup folder location for individual user accounts as well as a system-wide startup folder that will be checked regardless of which user account logs in. The startup folder path for the current user is C:\Users\\[Username]\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup. The startup folder path for all users is C:\ProgramData\Microsoft\Windows\Start Menu\Programs\StartUp. The following Registry keys can be used to set startup folder items for persistence: * HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders * HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders * HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders * HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders The following Registry keys can control automatic startup of services during boot: * HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce * HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunServicesOnce * HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices * HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\RunServices Using policy settings to specify startup programs creates corresponding values in either of two Registry keys: * HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run * HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run Programs listed in the load value of the registry key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\Windows run automatically for the currently logged-on user. By default, the multistring BootExecute value of the registry key HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager is set to autocheck autochk *. This value causes Windows, at startup, to check the file-system integrity of the hard disks if the system has been shut down abnormally. Adversaries can add other programs or processes to this registry value which will automatically launch at boot. Adversaries can use these configuration locations to execute malware, such as remote access tools, to maintain persistence through
Detection coverage (45)
- Kapeka Backdoor Autorun Persistence high
- Potential KamiKakaBot Activity - Winlogon Shell Persistence high
- Forest Blizzard APT - Custom Protocol Handler Creation high
- Forest Blizzard APT - Custom Protocol Handler DLL Registry Set high
- Registry Set With Crypto-Classes From The "Cryptography" PowerShell Namespace medium
- Potential Persistence Attempt Via Run Keys Using Reg.EXE medium
- Direct Autorun Keys Modification medium
- File Creation In Suspicious Directory By Msdt.EXE high
- Startup Folder File Write medium
- Potential Startup Shortcut Persistence Via PowerShell.EXE high
- Suspicious Startup Folder Persistence high
- WinRAR Creating Files in Startup Locations high
- Suspicious Autorun Registry Modified via WMI high
- Potential Suspicious Activity Using SeCEdit medium
- User Shell Folders Registry Modification via CommandLine high
- Narrator's Feedback-Hub Persistence high
- Suspicious Run Key from Download high
- Classes Autorun Keys Modification medium
- CurrentControlSet Autorun Keys Modification medium
- Session Manager Autorun Keys Modification medium
- Common Autorun Keys Modification medium
- Office Autorun Keys Modification medium
- CurrentVersion NT Autorun Keys Modification medium
- WinSock2 Autorun Keys Modification medium
- CurrentVersion Autorun Keys Modification medium
- System Scripts Autorun Keys Modification medium
- Internet Explorer Autorun Keys Modification medium
- Wow6432Node CurrentVersion Autorun Keys Modification medium
- Wow6432Node Classes Autorun Keys Modification medium
- Wow6432Node Windows NT CurrentVersion Autorun Keys Modification medium
- Windows Event Log Access Tampering Via Registry high
- Suspicious PowerShell In Registry Run Keys medium
- Registry Persistence via Explorer Run Key high
- VBScript Payload Stored in Registry high
- New RUN Key Pointing to Suspicious Folder high
- Modify User Shell Folders Startup Value high
- Registry Keys Used For Persistence
- Windows Boot or Logon Autostart Execution In Startup Folder
- Windows NorthStar C2 Agent Execution
- Windows PowerShell MSIX Package Installation
- Windows Registry BootExecute Modification
- Windows Registry Modification for Safe Mode Persistence
- Potential Ryuk Ransomware Activity high
- Leviathan Registry Key Activity critical
- Suspicious VBScript UN2452 Pattern high
Malware using this technique
- TrickBot
- PowerDuke
- RCSession
- GRIFFON
- Amadey
- NOKKI
- Backdoor.Oldrea
- MagicRAT
- TINYTYPHON
- AvosLocker
- Chinoxy
- SharpStage
- Smoke Loader
- Emissary
- HeartCrypt
- Ursnif
- ThreatNeedle
- RansomHub
- RedLeaves
- POWERSOURCE
- Tsundere Botnet
- Zeus Panda
- ShimRat
- ObliqueRAT
- Matryoshka
- InvisibleFerret
- StrongPity
- PLAINTEE
- Nebulae
- TONESHELL
- Kasidet
- AppleSeed
- NETWIRE
- EvilGrab
- SslMM
- Aria-body
- Emotet
- SNUGRIDE
- Crimson
- Turian
- Machete
- Clambling
- Prikormka
- PUBLOAD
- Gootloader
- AuTo Stealer
- FLASHFLOOD
- FlawedAmmyy
- Snip3
- Rifdoor
Threat actors using this technique
- APT3
- Inception
- Void Manticore
- PROMETHIUM
- APT35
- BlackByte
- Kimsuky
- Patchwork
- APT41
- Dragonfly
- Gorgon Group
- APT32
- MuddyWater
- Naikon
- FIN6
- Gamaredon Group
- Storm-1811
- TeamTNT
- FIN7
- APT18
- Sidewinder
- Mustang Panda
- ZIRCONIUM
- Rocke
- APT39
- Contagious Interview
- TA2541
- APT37
- Higaisa
- APT27
- Tropic Trooper
- Putter Panda
- APT15
- Confucius
- APT40
- Turla
- RedCurl
- APT29
- Dark Caracal
- BRONZE BUTLER
- APT33
- FIN10
- Darkhotel
- LazyScripter
- Windshift
- LuminousMoth
- APT28
- RTM
- Lazarus Group
- Silence