Analysis
-
max time kernel
42s -
max time network
34s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
24-11-2022 01:23
Behavioral task
behavioral1
Sample
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe
Resource
win10v2004-20221111-en
General
-
Target
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe
-
Size
83KB
-
MD5
3665e65c0248e4102425db89c37ae2a4
-
SHA1
4bed1461233c3e2611432dfd55ad5c8f0be3b8d5
-
SHA256
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf
-
SHA512
e0abddbb5aacb2f567aea09400056f69cca65600ffb21088d993bc8385bcbda01ba18aa3fcbd5b060e406174258583afa9d0c521f28b7d5adcb66d942eda734a
-
SSDEEP
1536:KLJ3LvzanlrQfLSrDzjpGdTG/Dbhgk1Gzp7B7X63eABoakkbv2Fb65R:uJ3LvkruinEwDSqGX7YeABROb65R
Malware Config
Signatures
-
Modifies firewall policy service 2 TTPs 1 IoCs
Processes:
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exedescription ioc process Set value (int) \REGISTRY\MACHINE\SYSTEM\ControlSet001\services\SharedAccess\Parameters\FirewallPolicy\StandardProfile\EnableFirewall = "0" fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe -
Processes:
resource yara_rule behavioral1/memory/2040-54-0x0000000000400000-0x0000000000494000-memory.dmp upx behavioral1/memory/2040-56-0x0000000000400000-0x0000000000494000-memory.dmp upx behavioral1/memory/2040-57-0x0000000000400000-0x0000000000494000-memory.dmp upx behavioral1/memory/2040-58-0x0000000000400000-0x0000000000494000-memory.dmp upx -
Drops startup file 1 IoCs
Processes:
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exedescription ioc process File created C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\mousedriver.exe fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe -
Adds Run key to start application 2 TTPs 2 IoCs
Processes:
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exedescription ioc process Key created \REGISTRY\USER\S-1-5-21-3406023954-474543476-3319432036-1000\Software\Microsoft\Windows\CurrentVersion\Run fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe Set value (str) \REGISTRY\USER\S-1-5-21-3406023954-474543476-3319432036-1000\Software\Microsoft\Windows\CurrentVersion\Run\engel = "C:\\Users\\Admin\\AppData\\Roaming\\updates\\updates.exe" fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe -
Drops file in System32 directory 1 IoCs
Processes:
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exedescription ioc process File opened for modification C:\WINDOWS\SysWOW64\NETSH.EXE fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious behavior: EnumeratesProcesses 1 IoCs
Processes:
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exepid process 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe -
Suspicious behavior: MapViewOfSection 22 IoCs
Processes:
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exepid process 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe -
Suspicious use of AdjustPrivilegeToken 5 IoCs
Processes:
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exedescription pid process Token: SeDebugPrivilege 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe Token: SeTakeOwnershipPrivilege 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe Token: SeRestorePrivilege 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe Token: SeBackupPrivilege 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe Token: SeChangeNotifyPrivilege 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exedescription pid process target process PID 2040 wrote to memory of 368 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe wininit.exe PID 2040 wrote to memory of 368 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe wininit.exe PID 2040 wrote to memory of 368 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe wininit.exe PID 2040 wrote to memory of 368 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe wininit.exe PID 2040 wrote to memory of 368 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe wininit.exe PID 2040 wrote to memory of 368 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe wininit.exe PID 2040 wrote to memory of 368 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe wininit.exe PID 2040 wrote to memory of 380 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe csrss.exe PID 2040 wrote to memory of 380 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe csrss.exe PID 2040 wrote to memory of 380 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe csrss.exe PID 2040 wrote to memory of 380 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe csrss.exe PID 2040 wrote to memory of 380 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe csrss.exe PID 2040 wrote to memory of 380 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe csrss.exe PID 2040 wrote to memory of 380 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe csrss.exe PID 2040 wrote to memory of 416 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe winlogon.exe PID 2040 wrote to memory of 416 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe winlogon.exe PID 2040 wrote to memory of 416 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe winlogon.exe PID 2040 wrote to memory of 416 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe winlogon.exe PID 2040 wrote to memory of 416 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe winlogon.exe PID 2040 wrote to memory of 416 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe winlogon.exe PID 2040 wrote to memory of 416 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe winlogon.exe PID 2040 wrote to memory of 460 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe services.exe PID 2040 wrote to memory of 460 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe services.exe PID 2040 wrote to memory of 460 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe services.exe PID 2040 wrote to memory of 460 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe services.exe PID 2040 wrote to memory of 460 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe services.exe PID 2040 wrote to memory of 460 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe services.exe PID 2040 wrote to memory of 460 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe services.exe PID 2040 wrote to memory of 476 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsass.exe PID 2040 wrote to memory of 476 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsass.exe PID 2040 wrote to memory of 476 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsass.exe PID 2040 wrote to memory of 476 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsass.exe PID 2040 wrote to memory of 476 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsass.exe PID 2040 wrote to memory of 476 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsass.exe PID 2040 wrote to memory of 476 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsass.exe PID 2040 wrote to memory of 484 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsm.exe PID 2040 wrote to memory of 484 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsm.exe PID 2040 wrote to memory of 484 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsm.exe PID 2040 wrote to memory of 484 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsm.exe PID 2040 wrote to memory of 484 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsm.exe PID 2040 wrote to memory of 484 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsm.exe PID 2040 wrote to memory of 484 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe lsm.exe PID 2040 wrote to memory of 600 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 600 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 600 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 600 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 600 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 600 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 600 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 680 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 680 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 680 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 680 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 680 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 680 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 680 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 764 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 764 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 764 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 764 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 764 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 764 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 764 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe PID 2040 wrote to memory of 804 2040 fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe svchost.exe
Processes
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe1⤵PID:476
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe1⤵PID:460
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork2⤵PID:1060
-
C:\Windows\system32\sppsvc.exeC:\Windows\system32\sppsvc.exe2⤵PID:1096
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation2⤵PID:1768
-
C:\Windows\system32\taskhost.exe"taskhost.exe"2⤵PID:1176
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe2⤵PID:108
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService2⤵PID:296
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k netsvcs2⤵PID:876
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalService2⤵PID:852
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted2⤵PID:804
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted2⤵PID:764
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k RPCSS2⤵PID:680
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch2⤵PID:600
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵PID:416
-
C:\Windows\system32\csrss.exe%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=161⤵PID:380
-
C:\Windows\system32\wininit.exewininit.exe1⤵PID:368
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵PID:484
-
C:\Windows\system32\wbem\wmiprvse.exeC:\Windows\system32\wbem\wmiprvse.exe1⤵PID:1912
-
\\?\C:\Windows\system32\wbem\WMIADAP.EXEwmiadap.exe /F /T /R1⤵PID:1992
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1312
-
C:\Users\Admin\AppData\Local\Temp\fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe"C:\Users\Admin\AppData\Local\Temp\fa5cf7c1c4387f043c8e56eed7e5d7edfedc562d68a6f9d7c3d74aaf4d63bedf.exe"2⤵
- Modifies firewall policy service
- Drops startup file
- Adds Run key to start application
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:2040
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"1⤵PID:1276