KJChen/tech2proc · Datasets at Hugging Face

prompt stringclasses 508 values	procedure stringlengths 20 478
Create or Modify System Process:Windows Service	RDAT has created a service when it is installed on the victim machine.
Create or Modify System Process:Windows Service	Reaver installs itself as a new service.
Create or Modify System Process:Windows Service	Some Sakula samples install themselves as services for persistence by calling WinExec with the net start argument.
Create or Modify System Process:Windows Service	Seasalt is capable of installing itself as a service.
Create or Modify System Process:Windows Service	Shamoon creates a new service named "ntssrv" to execute the payload. Newer versions create the "MaintenaceSrv" and "hdv_725x" services.
Create or Modify System Process:Windows Service	ShimRat has installed a Windows service to maintain persistence on victim machines.
Create or Modify System Process:Windows Service	SILENTTRINITY can establish persistence by creating a new service.
Create or Modify System Process:Windows Service	SLOTHFULMEDIA has created a service on victim machines named "TaskFrame" to establish persistence.
Create or Modify System Process:Windows Service	STARWHALE has the ability to create the following Windows service to establish persistence on an infected host: sc create Windowscarpstss binpath= "cmd.exe /c cscript.exe c:\\windows\\system32\\w7_1.wsf humpback_whale" start= "auto" obj= "LocalSystem".
Create or Modify System Process:Windows Service	StreamEx establishes persistence by installing a new service pointing to its DLL and setting the service to auto-start.
Create or Modify System Process:Windows Service	StrongPity has created new services and modified existing services for persistence.
Create or Modify System Process:Windows Service	Stuxnet uses a driver registered as a boot start service as the main load-point.
Create or Modify System Process:Windows Service	SUGARUSH has created a service named Service1 for persistence.
Create or Modify System Process:Windows Service	SysUpdate can create a service to establish persistence.
Create or Modify System Process:Windows Service	If running as administrator, TDTESS installs itself as a new service named bmwappushservice to establish persistence.
Create or Modify System Process:Windows Service	It has used malware that adds cryptocurrency miners as a service.
Create or Modify System Process:Windows Service	TEARDROP ran as a Windows service from the c:\windows\syswow64 folder.
Create or Modify System Process:Windows Service	It's malware can create a new service, sometimes naming it after the config information, to gain persistence.
Create or Modify System Process:Windows Service	ThreatNeedle can run in memory and register its payload as a Windows service.
Create or Modify System Process:Windows Service	TinyZBot can install as a Windows service for persistence.
Create or Modify System Process:Windows Service	TrickBot establishes persistence by creating an autostart service that allows it to run whenever the machine boots.
Create or Modify System Process:Windows Service	It has installed a service pointing to a malicious DLL dropped to disk.
Create or Modify System Process:Windows Service	TYPEFRAME variants can add malicious DLL modules as new services.TYPEFRAME can also delete services from the victim’s machine.
Create or Modify System Process:Windows Service	Uroburos has registered a service, typically named WerFaultSvc, to decrypt and find a kernel driver and kernel driver loader to maintain persistence.
Create or Modify System Process:Windows Service	Ursnif has registered itself as a system service in the Registry for automatic execution at system startup.
Create or Modify System Process:Windows Service	Volgmer installs a copy of itself in a randomly selected service, then overwrites the ServiceDLL entry in the service's Registry entry. Some Volgmer variants also install .dll files as services with names generated by a list of hard-coded strings.
Create or Modify System Process:Windows Service	WannaCry creates the service "mssecsvc2.0" with the display name "Microsoft Security Center (2.0) Service."
Create or Modify System Process:Windows Service	WastedLocker created and established a service that runs until the encryption process is complete.
Create or Modify System Process:Windows Service	Wiarp creates a backdoor through which remote attackers can create a service.
Create or Modify System Process:Windows Service	Wingbird uses services.exe to register a new autostart service named "Audit Service" using a copy of the local lsass.exe file.
Create or Modify System Process:Windows Service	Winnti for Windows sets its DLL file as a new service in the Registry to establish persistence.
Create or Modify System Process:Windows Service	It has installed TrickBot as a service named ControlServiceA in order to establish persistence.
Create or Modify System Process:Windows Service	ZeroT can add a new service to ensure PlugX persists on the system when delivered as another payload onto the system.
Create or Modify System Process:Windows Service	ZLib creates Registry keys to allow itself to run as various services.
Create or Modify System Process:Windows Service	zwShell has established persistence by adding itself as a new service.
Create or Modify System Process:Windows Service	ZxShell can create a new service using the service parser function ProcessScCommand.
Create or Modify System Process:Launch Daemon	AppleJeus has placed a plist file within the LaunchDaemons folder and launched it manually.
Create or Modify System Process:Launch Daemon	Bundlore can persist via a LaunchDaemon.
Create or Modify System Process:Launch Daemon	Dacls can establish persistence via a Launch Daemon.
Create or Modify System Process:Launch Daemon	Green Lambert can add a plist file in the Library/LaunchDaemons to establish persistence.
Create or Modify System Process:Launch Daemon	LoudMiner adds plist files with the naming format com.[random_name].plist in the /Library/LaunchDaemons folder with the RunAtLoad and KeepAlive keys set to true.
Create or Modify System Process:Launch Daemon	If running with root permissions, OSX_OCEANLOTUS.D can create a persistence file in the folder /Library/LaunchDaemons.
Create or Modify System Process:Launch Daemon	When running with root privileges after a Launch Agent is installed, ThiefQuest installs a plist file to the /Library/LaunchDaemons/ folder with the RunAtLoad key set to true establishing persistence as a Launch Daemon.
Create or Modify System Process:Launch Daemon	XCSSET uses the ssh launchdaemon to elevate privileges, bypass system controls, and enable remote access to the victim.
Event Triggered Execution	Pacu can set up S3 bucket notifications to trigger a malicious Lambda function when a CloudFormation template is uploaded to the bucket. It can also create Lambda functions that trigger upon the creation of users, roles, and groups.
Event Triggered Execution:Change Default File Association	It has a HWP document stealer module which changes the default program association in the registry to open HWP documents.
Event Triggered Execution:Change Default File Association	SILENTTRINITY can conduct an image hijack of an .msc file extension as part of its UAC bypass process.
Event Triggered Execution:Screensaver	Gazer can establish persistence through the system screensaver by configuring it to execute the malware.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	adbupd can use a WMI script to achieve persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	It has used WMI event subscriptions for persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	It has attempted to use WMI event subscriptions to establish persistence on compromised hosts.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	BADHATCH can use WMI event subscriptions for persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	It has used mofcomp.exe to establish WMI Event Subscription persistence mechanisms configured from a *.mof file.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	It has used WMI event subscriptions for persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	It has used WMI for persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	It has established persistence through the use of a WMI event subscription combined with unusual living-off-the-land binaries such as cdb.exe.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	metaMain registered a WMI event subscription consumer called "hard_disk_stat" to establish persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	It's custom ORat tool uses a WMI event consumer to maintain persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	During Operation Ghost, It used WMI event subscriptions to establish persistence for malware.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	PoshC2 has the ability to persist on a system using WMI events.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	POSHSPY uses a WMI event subscription to establish persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	POWERTON can use WMI for persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	RegDuke can persist using a WMI consumer that is launched every time a process named WINWORD.EXE is started.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	Sardonic can use a WMI event filter to invoke a command-line event consumer to gain persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	SeaDuke uses an event filter in WMI code to execute a previously dropped executable shortly after system startup.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	SILENTTRINITY can create a WMI Event to execute a payload for persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	During the SolarWinds Compromise, It used a WMI event filter to invoke a command-line event consumer at system boot time to launch a backdoor with rundll32.exe.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	TrailBlazer has the ability to use WMI for persistence.
Event Triggered Execution:Windows Management Instrumentation Event Subscription	It has used WMI event filters and consumers to establish persistence.
Event Triggered Execution:Unix Shell Configuration Modification	Green Lambert can establish persistence on a compromised host through modifying the profile, login, and run command (rc) files associated with the bash, csh, and tcsh shells.
Event Triggered Execution:Unix Shell Configuration Modification	Linux Rabbit maintains persistence on an infected machine through rc.local and .bashrc files.
Event Triggered Execution:Unix Shell Configuration Modification	When executing with non-root level permissions, RotaJakiro can install persistence by adding a command to the .bashrc file that executes a binary in the ${HOME}/.gvfsd/.profile/ folder.
Event Triggered Execution:Netsh Helper DLL	netsh can be used as a persistence proxy technique to execute a helper DLL when netsh.exe is executed.
Event Triggered Execution:Accessibility Features	It used sticky-keys to obtain unauthenticated, privileged console access.
Event Triggered Execution:Accessibility Features	It replaces the Sticky Keys binary C:\Windows\System32\sethc.exe for persistence.
Event Triggered Execution:Accessibility Features	It leveraged sticky keys to establish persistence.
Event Triggered Execution:Accessibility Features	It actors have been known to use the Sticky Keys replacement within RDP sessions to obtain persistence.
Event Triggered Execution:Accessibility Features	It has used the sticky-keys technique to bypass the RDP login screen on remote systems during intrusions.
Event Triggered Execution:Accessibility Features	Empire can leverage WMI debugging to remotely replace binaries like sethc.exe, Utilman.exe, and Magnify.exe with cmd.exe.
Event Triggered Execution:Accessibility Features	It has used sticky keys to launch a command prompt.
Event Triggered Execution:AppCert DLLs	PUNCHBUGGY can establish using a AppCertDLLs Registry key.
Event Triggered Execution:AppInit DLLs	It has used malware to set LoadAppInit_DLLs in the Registry key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows in order to establish persistence.
Event Triggered Execution:AppInit DLLs	Some variants of Cherry Picker use AppInit_DLLs to achieve persistence by creating the following Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows "AppInit_DLLs"="pserver32.dll"
Event Triggered Execution:AppInit DLLs	Ramsay can insert itself into the address space of other applications using the AppInit DLL Registry key.
Event Triggered Execution:AppInit DLLs	If a victim meets certain criteria, T9000 uses the AppInit_DLL functionality to achieve persistence by ensuring that every user mode process that is spawned will load its malicious DLL, ResN32.dll. It does this by creating the following Registry keys: HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs – %APPDATA%\Intel\ResN32.dll and HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows\LoadAppInit_DLLs – 0x1.
Event Triggered Execution:Application Shimming	It has used application shim databases for persistence.
Event Triggered Execution:Application Shimming	Pillowmint has used a malicious shim database to maintain persistence.
Event Triggered Execution:Application Shimming	SDBbot has the ability to use application shimming for persistence if it detects it is running as admin on Windows XP or 7, by creating a shim database to patch services.exe.
Event Triggered Execution:Application Shimming	ShimRat has installed shim databases in the AppPatch folder.
Event Triggered Execution:Image File Execution Options Injection	SDBbot has the ability to use image file execution options for persistence if it detects it is running with admin privileges on a Windows version newer than Windows 7.
Event Triggered Execution:Image File Execution Options Injection	SUNBURST created an Image File Execution Options (IFEO) Debugger registry value for the process dllhost.exe to trigger the installation of Cobalt Strike.
Event Triggered Execution:Image File Execution Options Injection	It has modified and added entries within HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options to maintain persistence.
Event Triggered Execution:PowerShell Profile	It has used PowerShell profiles to maintain persistence on an infected machine.
Event Triggered Execution:Component Object Model Hijacking	Some variants of ADVSTORESHELL achieve persistence by registering the payload as a Shell Icon Overlay handler COM object.
Event Triggered Execution:Component Object Model Hijacking	It has used COM hijacking for persistence by replacing the legitimate MMDeviceEnumerator object with a payload.
Event Triggered Execution:Component Object Model Hijacking	BBSRAT has been seen persisting via COM hijacking through replacement of the COM object for MruPidlList {42aedc87-2188-41fd-b9a3-0c966feabec1} or Microsoft WBEM New Event Subsystem {F3130CDB-AA52-4C3A-AB32-85FFC23AF9C1} depending on the system's CPU architecture.
Event Triggered Execution:Component Object Model Hijacking	ComRAT samples have been seen which hijack COM objects for persistence by replacing the path to shell32.dll in registry location HKCU\Software\Classes\CLSID{42aedc87-2188-41fd-b9a3-0c966feabec1}\InprocServer32.
Event Triggered Execution:Component Object Model Hijacking	Ferocious can use COM hijacking to establish persistence.
Event Triggered Execution:Component Object Model Hijacking	JHUHUGIT has used COM hijacking to establish persistence by hijacking a class named MMDeviceEnumerator and also by registering the payload as a Shell Icon Overlay handler COM object ({3543619C-D563-43f7-95EA-4DA7E1CC396A}).
Event Triggered Execution:Component Object Model Hijacking	KONNI has modified ComSysApp service to load the malicious DLL payload.

Create or Modify System Process:Windows Service

RDAT has created a service when it is installed on the victim machine.

Create or Modify System Process:Windows Service

Reaver installs itself as a new service.

Create or Modify System Process:Windows Service

Some Sakula samples install themselves as services for persistence by calling WinExec with the net start argument.

Create or Modify System Process:Windows Service

Seasalt is capable of installing itself as a service.

Create or Modify System Process:Windows Service

Shamoon creates a new service named "ntssrv" to execute the payload. Newer versions create the "MaintenaceSrv" and "hdv_725x" services.

Create or Modify System Process:Windows Service

ShimRat has installed a Windows service to maintain persistence on victim machines.

Create or Modify System Process:Windows Service

SILENTTRINITY can establish persistence by creating a new service.

Create or Modify System Process:Windows Service

SLOTHFULMEDIA has created a service on victim machines named "TaskFrame" to establish persistence.

Create or Modify System Process:Windows Service

STARWHALE has the ability to create the following Windows service to establish persistence on an infected host: sc create Windowscarpstss binpath= "cmd.exe /c cscript.exe c:\\windows\\system32\\w7_1.wsf humpback_whale" start= "auto" obj= "LocalSystem".

Create or Modify System Process:Windows Service

StreamEx establishes persistence by installing a new service pointing to its DLL and setting the service to auto-start.

Create or Modify System Process:Windows Service

StrongPity has created new services and modified existing services for persistence.

Create or Modify System Process:Windows Service

Stuxnet uses a driver registered as a boot start service as the main load-point.

Create or Modify System Process:Windows Service

SUGARUSH has created a service named Service1 for persistence.

Create or Modify System Process:Windows Service

SysUpdate can create a service to establish persistence.

Create or Modify System Process:Windows Service

If running as administrator, TDTESS installs itself as a new service named bmwappushservice to establish persistence.

Create or Modify System Process:Windows Service

It has used malware that adds cryptocurrency miners as a service.

Create or Modify System Process:Windows Service

TEARDROP ran as a Windows service from the c:\windows\syswow64 folder.

Create or Modify System Process:Windows Service

It's malware can create a new service, sometimes naming it after the config information, to gain persistence.

Create or Modify System Process:Windows Service

ThreatNeedle can run in memory and register its payload as a Windows service.

Create or Modify System Process:Windows Service

TinyZBot can install as a Windows service for persistence.

Create or Modify System Process:Windows Service

TrickBot establishes persistence by creating an autostart service that allows it to run whenever the machine boots.

Create or Modify System Process:Windows Service

It has installed a service pointing to a malicious DLL dropped to disk.

Create or Modify System Process:Windows Service

TYPEFRAME variants can add malicious DLL modules as new services.TYPEFRAME can also delete services from the victim’s machine.

Create or Modify System Process:Windows Service

Uroburos has registered a service, typically named WerFaultSvc, to decrypt and find a kernel driver and kernel driver loader to maintain persistence.

Create or Modify System Process:Windows Service

Ursnif has registered itself as a system service in the Registry for automatic execution at system startup.

Create or Modify System Process:Windows Service

Volgmer installs a copy of itself in a randomly selected service, then overwrites the ServiceDLL entry in the service's Registry entry. Some Volgmer variants also install .dll files as services with names generated by a list of hard-coded strings.

Create or Modify System Process:Windows Service

WannaCry creates the service "mssecsvc2.0" with the display name "Microsoft Security Center (2.0) Service."

Create or Modify System Process:Windows Service

WastedLocker created and established a service that runs until the encryption process is complete.

Create or Modify System Process:Windows Service

Wiarp creates a backdoor through which remote attackers can create a service.

Create or Modify System Process:Windows Service

Wingbird uses services.exe to register a new autostart service named "Audit Service" using a copy of the local lsass.exe file.

Create or Modify System Process:Windows Service

Winnti for Windows sets its DLL file as a new service in the Registry to establish persistence.

Create or Modify System Process:Windows Service

It has installed TrickBot as a service named ControlServiceA in order to establish persistence.

Create or Modify System Process:Windows Service

ZeroT can add a new service to ensure PlugX persists on the system when delivered as another payload onto the system.

Create or Modify System Process:Windows Service

ZLib creates Registry keys to allow itself to run as various services.

Create or Modify System Process:Windows Service

zwShell has established persistence by adding itself as a new service.

Create or Modify System Process:Windows Service

ZxShell can create a new service using the service parser function ProcessScCommand.

Create or Modify System Process:Launch Daemon

AppleJeus has placed a plist file within the LaunchDaemons folder and launched it manually.

Create or Modify System Process:Launch Daemon

Bundlore can persist via a LaunchDaemon.

Create or Modify System Process:Launch Daemon

Dacls can establish persistence via a Launch Daemon.

Create or Modify System Process:Launch Daemon

Green Lambert can add a plist file in the Library/LaunchDaemons to establish persistence.

Create or Modify System Process:Launch Daemon

LoudMiner adds plist files with the naming format com.[random_name].plist in the /Library/LaunchDaemons folder with the RunAtLoad and KeepAlive keys set to true.

Create or Modify System Process:Launch Daemon

If running with root permissions, OSX_OCEANLOTUS.D can create a persistence file in the folder /Library/LaunchDaemons.

Create or Modify System Process:Launch Daemon

When running with root privileges after a Launch Agent is installed, ThiefQuest installs a plist file to the /Library/LaunchDaemons/ folder with the RunAtLoad key set to true establishing persistence as a Launch Daemon.

Create or Modify System Process:Launch Daemon

XCSSET uses the ssh launchdaemon to elevate privileges, bypass system controls, and enable remote access to the victim.

Event Triggered Execution

Pacu can set up S3 bucket notifications to trigger a malicious Lambda function when a CloudFormation template is uploaded to the bucket. It can also create Lambda functions that trigger upon the creation of users, roles, and groups.

Event Triggered Execution:Change Default File Association

It has a HWP document stealer module which changes the default program association in the registry to open HWP documents.

Event Triggered Execution:Change Default File Association

SILENTTRINITY can conduct an image hijack of an .msc file extension as part of its UAC bypass process.

Event Triggered Execution:Screensaver

Gazer can establish persistence through the system screensaver by configuring it to execute the malware.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

adbupd can use a WMI script to achieve persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

It has used WMI event subscriptions for persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

It has attempted to use WMI event subscriptions to establish persistence on compromised hosts.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

BADHATCH can use WMI event subscriptions for persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

It has used mofcomp.exe to establish WMI Event Subscription persistence mechanisms configured from a *.mof file.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

It has used WMI event subscriptions for persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

It has used WMI for persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

It has established persistence through the use of a WMI event subscription combined with unusual living-off-the-land binaries such as cdb.exe.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

metaMain registered a WMI event subscription consumer called "hard_disk_stat" to establish persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

It's custom ORat tool uses a WMI event consumer to maintain persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

During Operation Ghost, It used WMI event subscriptions to establish persistence for malware.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

PoshC2 has the ability to persist on a system using WMI events.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

POSHSPY uses a WMI event subscription to establish persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

POWERTON can use WMI for persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

RegDuke can persist using a WMI consumer that is launched every time a process named WINWORD.EXE is started.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

Sardonic can use a WMI event filter to invoke a command-line event consumer to gain persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

SeaDuke uses an event filter in WMI code to execute a previously dropped executable shortly after system startup.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

SILENTTRINITY can create a WMI Event to execute a payload for persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

During the SolarWinds Compromise, It used a WMI event filter to invoke a command-line event consumer at system boot time to launch a backdoor with rundll32.exe.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

TrailBlazer has the ability to use WMI for persistence.

Event Triggered Execution:Windows Management Instrumentation Event Subscription

It has used WMI event filters and consumers to establish persistence.

Event Triggered Execution:Unix Shell Configuration Modification

Green Lambert can establish persistence on a compromised host through modifying the profile, login, and run command (rc) files associated with the bash, csh, and tcsh shells.

Event Triggered Execution:Unix Shell Configuration Modification

Linux Rabbit maintains persistence on an infected machine through rc.local and .bashrc files.

Event Triggered Execution:Unix Shell Configuration Modification

When executing with non-root level permissions, RotaJakiro can install persistence by adding a command to the .bashrc file that executes a binary in the ${HOME}/.gvfsd/.profile/ folder.

Event Triggered Execution:Netsh Helper DLL

netsh can be used as a persistence proxy technique to execute a helper DLL when netsh.exe is executed.

Event Triggered Execution:Accessibility Features

It used sticky-keys to obtain unauthenticated, privileged console access.

Event Triggered Execution:Accessibility Features

It replaces the Sticky Keys binary C:\Windows\System32\sethc.exe for persistence.

Event Triggered Execution:Accessibility Features

It leveraged sticky keys to establish persistence.

Event Triggered Execution:Accessibility Features

It actors have been known to use the Sticky Keys replacement within RDP sessions to obtain persistence.

Event Triggered Execution:Accessibility Features

It has used the sticky-keys technique to bypass the RDP login screen on remote systems during intrusions.

Event Triggered Execution:Accessibility Features

Empire can leverage WMI debugging to remotely replace binaries like sethc.exe, Utilman.exe, and Magnify.exe with cmd.exe.

Event Triggered Execution:Accessibility Features

It has used sticky keys to launch a command prompt.

Event Triggered Execution:AppCert DLLs

PUNCHBUGGY can establish using a AppCertDLLs Registry key.

Event Triggered Execution:AppInit DLLs

It has used malware to set LoadAppInit_DLLs in the Registry key SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows in order to establish persistence.

Event Triggered Execution:AppInit DLLs

Some variants of Cherry Picker use AppInit_DLLs to achieve persistence by creating the following Registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows "AppInit_DLLs"="pserver32.dll"

Event Triggered Execution:AppInit DLLs

Ramsay can insert itself into the address space of other applications using the AppInit DLL Registry key.

Event Triggered Execution:AppInit DLLs

If a victim meets certain criteria, T9000 uses the AppInit_DLL functionality to achieve persistence by ensuring that every user mode process that is spawned will load its malicious DLL, ResN32.dll. It does this by creating the following Registry keys: HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows\AppInit_DLLs – %APPDATA%\Intel\ResN32.dll and HKLM\Software\Microsoft\Windows NT\CurrentVersion\Windows\LoadAppInit_DLLs – 0x1.

Event Triggered Execution:Application Shimming

It has used application shim databases for persistence.

Event Triggered Execution:Application Shimming

Pillowmint has used a malicious shim database to maintain persistence.

Event Triggered Execution:Application Shimming

SDBbot has the ability to use application shimming for persistence if it detects it is running as admin on Windows XP or 7, by creating a shim database to patch services.exe.

Event Triggered Execution:Application Shimming

ShimRat has installed shim databases in the AppPatch folder.

Event Triggered Execution:Image File Execution Options Injection

SDBbot has the ability to use image file execution options for persistence if it detects it is running with admin privileges on a Windows version newer than Windows 7.

Event Triggered Execution:Image File Execution Options Injection

SUNBURST created an Image File Execution Options (IFEO) Debugger registry value for the process dllhost.exe to trigger the installation of Cobalt Strike.

Event Triggered Execution:Image File Execution Options Injection

It has modified and added entries within HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Image File Execution Options to maintain persistence.

Event Triggered Execution:PowerShell Profile

It has used PowerShell profiles to maintain persistence on an infected machine.

Event Triggered Execution:Component Object Model Hijacking

Some variants of ADVSTORESHELL achieve persistence by registering the payload as a Shell Icon Overlay handler COM object.

Event Triggered Execution:Component Object Model Hijacking

It has used COM hijacking for persistence by replacing the legitimate MMDeviceEnumerator object with a payload.

Event Triggered Execution:Component Object Model Hijacking

BBSRAT has been seen persisting via COM hijacking through replacement of the COM object for MruPidlList {42aedc87-2188-41fd-b9a3-0c966feabec1} or Microsoft WBEM New Event Subsystem {F3130CDB-AA52-4C3A-AB32-85FFC23AF9C1} depending on the system's CPU architecture.

Event Triggered Execution:Component Object Model Hijacking

ComRAT samples have been seen which hijack COM objects for persistence by replacing the path to shell32.dll in registry location HKCU\Software\Classes\CLSID{42aedc87-2188-41fd-b9a3-0c966feabec1}\InprocServer32.

Event Triggered Execution:Component Object Model Hijacking

Ferocious can use COM hijacking to establish persistence.

Event Triggered Execution:Component Object Model Hijacking

JHUHUGIT has used COM hijacking to establish persistence by hijacking a class named MMDeviceEnumerator and also by registering the payload as a Shell Icon Overlay handler COM object ({3543619C-D563-43f7-95EA-4DA7E1CC396A}).

Event Triggered Execution:Component Object Model Hijacking

KONNI has modified ComSysApp service to load the malicious DLL payload.