Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
135s -
max time network
119s -
platform
windows7_x64 -
resource
win7-20231129-en -
resource tags
arch:x64arch:x86image:win7-20231129-enlocale:en-usos:windows7-x64system -
submitted
23/05/2024, 01:23
Behavioral task
behavioral1
Sample
a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe
Resource
win7-20231129-en
General
-
Target
a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe
-
Size
1.6MB
-
MD5
0b54440728c218b809c865efde2be968
-
SHA1
620c868da0e65cf15bd0fc9ba1bf5dfe8221a5a8
-
SHA256
a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744
-
SHA512
84108b95a985bd8cddccb121707c02c7d471da0d3cfc02e4b5963e126c40f5d97f8e42258b05d26b3510dd7d1aac91cc0807b6ba4b7079b518d6e8114bd14040
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQE4efQg3zNn+2jsvercPk9N4hVI3/BxL+XKHZjb//8ISgH4:E5aIwC+Agr6SqCPGC6HZkIT/b/U
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral1/files/0x0008000000015d0f-20.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral1/memory/624-15-0x0000000000310000-0x0000000000339000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 1212 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 1164 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe -
Loads dropped DLL 2 IoCs
pid Process 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe -
Drops file in System32 directory 2 IoCs
description ioc Process File opened for modification C:\Windows\SysWOW64\%ProgramData%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk powershell.exe File opened for modification C:\Windows\SysWOW64\%ProgramData%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk powershell.exe -
Launches sc.exe 4 IoCs
Sc.exe is a Windows utlilty to control services on the system.
pid Process 2524 sc.exe 3036 sc.exe 2832 sc.exe 2604 sc.exe -
Suspicious behavior: EnumeratesProcesses 8 IoCs
pid Process 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 2708 powershell.exe 2152 powershell.exe -
Suspicious use of AdjustPrivilegeToken 4 IoCs
description pid Process Token: SeDebugPrivilege 2152 powershell.exe Token: SeDebugPrivilege 2708 powershell.exe Token: SeTcbPrivilege 1212 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe Token: SeTcbPrivilege 1164 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 1212 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 1164 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 624 wrote to memory of 1696 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 28 PID 624 wrote to memory of 1696 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 28 PID 624 wrote to memory of 1696 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 28 PID 624 wrote to memory of 1696 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 28 PID 624 wrote to memory of 1072 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 29 PID 624 wrote to memory of 1072 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 29 PID 624 wrote to memory of 1072 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 29 PID 624 wrote to memory of 1072 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 29 PID 624 wrote to memory of 1680 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 31 PID 624 wrote to memory of 1680 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 31 PID 624 wrote to memory of 1680 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 31 PID 624 wrote to memory of 1680 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 31 PID 624 wrote to memory of 2580 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 34 PID 624 wrote to memory of 2580 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 34 PID 624 wrote to memory of 2580 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 34 PID 624 wrote to memory of 2580 624 a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe 34 PID 1696 wrote to memory of 2832 1696 cmd.exe 36 PID 1696 wrote to memory of 2832 1696 cmd.exe 36 PID 1696 wrote to memory of 2832 1696 cmd.exe 36 PID 1696 wrote to memory of 2832 1696 cmd.exe 36 PID 1680 wrote to memory of 2708 1680 cmd.exe 37 PID 1680 wrote to memory of 2708 1680 cmd.exe 37 PID 1680 wrote to memory of 2708 1680 cmd.exe 37 PID 1680 wrote to memory of 2708 1680 cmd.exe 37 PID 1072 wrote to memory of 2604 1072 cmd.exe 35 PID 1072 wrote to memory of 2604 1072 cmd.exe 35 PID 1072 wrote to memory of 2604 1072 cmd.exe 35 PID 1072 wrote to memory of 2604 1072 cmd.exe 35 PID 2580 wrote to memory of 2476 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 38 PID 2580 wrote to memory of 2476 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 38 PID 2580 wrote to memory of 2476 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 38 PID 2580 wrote to memory of 2476 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 38 PID 2580 wrote to memory of 2812 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 39 PID 2580 wrote to memory of 2812 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 39 PID 2580 wrote to memory of 2812 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 39 PID 2580 wrote to memory of 2812 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 39 PID 2580 wrote to memory of 2624 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 41 PID 2580 wrote to memory of 2624 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 41 PID 2580 wrote to memory of 2624 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 41 PID 2580 wrote to memory of 2624 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 41 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2812 wrote to memory of 2524 2812 cmd.exe 45 PID 2812 wrote to memory of 2524 2812 cmd.exe 45 PID 2812 wrote to memory of 2524 2812 cmd.exe 45 PID 2812 wrote to memory of 2524 2812 cmd.exe 45 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 PID 2580 wrote to memory of 2448 2580 a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe 43 -
Uses Task Scheduler COM API 1 TTPs
The Task Scheduler COM API can be used to schedule applications to run on boot or at set times.
Processes
-
C:\Users\Admin\AppData\Local\Temp\a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe"C:\Users\Admin\AppData\Local\Temp\a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:624 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:1696 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2832
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:1072 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2604
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:1680 -
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exepowershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:2708
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exeC:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe2⤵
- Executes dropped EXE
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2580 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend3⤵PID:2476
-
C:\Windows\SysWOW64\sc.exesc stop WinDefend4⤵
- Launches sc.exe
PID:3036
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend3⤵
- Suspicious use of WriteProcessMemory
PID:2812 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend4⤵
- Launches sc.exe
PID:2524
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵PID:2624
-
C:\Windows\SysWOW64\WindowsPowerShell\v1.0\powershell.exepowershell Set-MpPreference -DisableRealtimeMonitoring $true4⤵
- Drops file in System32 directory
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
PID:2152
-
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2448
-
-
-
C:\Windows\system32\taskeng.exetaskeng.exe {940176C5-5E33-4239-8D8C-7AA4A613AEC9} S-1-5-18:NT AUTHORITY\System:Service:1⤵PID:3064
-
C:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exeC:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:1212 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:380
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exeC:\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:1164 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2856
-
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Recent\CustomDestinations\d93f411851d7c929.customDestinations-ms
Filesize7KB
MD56e2c312d91abc7cc708c946ca4e5edd7
SHA1d738a3e8face5c80c716b729dab47340f05cb2da
SHA2566ff4ce53776868e1067f9fecb4778c3028ee02ca58c4dcde900f47f1eea69c36
SHA512089491a9efdc0e1649c50633f46b851ad30a3e3d85631807d40658347ea956218118882b268ad4c59f56afce342d14a4fba37ae3db0b4e32dcfc4969fd600b52
-
\Users\Admin\AppData\Roaming\WinSocket\a69a892833994073d09ece9fa86c99e8cdfe6d0c1bb0d6a1f4ef203ff6b70844.exe
Filesize1.6MB
MD50b54440728c218b809c865efde2be968
SHA1620c868da0e65cf15bd0fc9ba1bf5dfe8221a5a8
SHA256a58a792733884063d08ece9fa75c99e7cdfe5d0c1bb0d5a1f4ef203ff5b60744
SHA51284108b95a985bd8cddccb121707c02c7d471da0d3cfc02e4b5963e126c40f5d97f8e42258b05d26b3510dd7d1aac91cc0807b6ba4b7079b518d6e8114bd14040