Scheduled task persistence
Named by 10 kept items in this workspace.
Search every workspace for Scheduled task persistence. It matches the name as written, so it can find other things that share it.
The items that name it 10
RadminComponentRuntime runs FamItrfc.exe --runtimechk every three hours; \NitroRuntime runs NitroPromotion.exe via PowerShell
The \Maiden scheduled task runs every five minutes to maintain persistence
Scheduled task sharing the same name as the Run key, re-created if deleted, both launching the sideloaded application.
Multiple scheduled tasks with randomized names (e.g., Nonweighise\Cancellationizing\Illuminateers) created to achieve persistence and enable further attack stages
Scheduled tasks created for persistence: EdgeCore_AutoUpdate (UNK_LateNight ShadowPad), MicrosoftEdgeUpdatesTaskMachine and Avpcheckup (UNK_DoubleCheck), GeForceService (UNK_QuietRacket).
Creating deceptive scheduled tasks named 'Google Chrome Start' to run malware with highest privileges at logon
Creates five scheduled tasks running as SYSTEM, including a boot task retained permanently, referencing WMILoad directories and ClockRemoval scripts
Windows Scheduled Task created via C:\WINDOWS\system32\sc.exe to start the GoTo Resolve service for persistence
Boot-triggered Scheduled Task named ClockLauncher (\ClockLauncher) running as SYSTEM (S-1-5-18) with HighestAvailable run level, executing run-clock.bat
Malware creates scheduled tasks for periodic execution; traced via Security.evtx (4698-4702) and TaskScheduler operational log (140, 141)
All techniques in this workspace.