Analysis
-
max time kernel
135s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20231129-en -
resource tags
arch:x64arch:x86image:win7-20231129-enlocale:en-usos:windows7-x64system -
submitted
03-06-2024 21:47
Behavioral task
behavioral1
Sample
574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe
Resource
win7-20231129-en
General
-
Target
574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe
-
Size
1023KB
-
MD5
40919a3391314adde33ab0f1456eaf1f
-
SHA1
23a42184a115b875e2617df2d2bbcff4111d569a
-
SHA256
574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52
-
SHA512
2266e7df9916f8109fa3ec91881e4a7bb7203b0d01b1a23df557a7e5cb26649714907d68e7c11a55bb183db897e8b08d868a1d6c211e17f4c0021805ca50af1e
-
SSDEEP
12288:zJB0lh5aILwtFPCfmAUtFC6NXbv+GEBQqtGSsGa60C+4PMAQBnm46MoCBuu0JphG:zQ5aILMCfmAUjzX6xQtjmssdqcbu
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
Processes:
resource yara_rule \Users\Admin\AppData\Roaming\WinSocket\684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
Processes:
resource yara_rule behavioral1/memory/2188-15-0x00000000002D0000-0x00000000002F9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
Processes:
684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exepid process 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe 1580 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe 1528 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe -
Loads dropped DLL 2 IoCs
Processes:
574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exepid process 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe -
Drops file in System32 directory 1 IoCs
Processes:
powershell.exedescription ioc process File opened for modification C:\Windows\SysWOW64\%ProgramData%\Microsoft\Windows\Start Menu\Programs\Accessories\Windows PowerShell\Windows PowerShell.lnk powershell.exe -
Launches sc.exe 2 IoCs
Sc.exe is a Windows utlilty to control services on the system.
Processes:
sc.exesc.exepid process 2560 sc.exe 2284 sc.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
Processes:
574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exepowershell.exepid process 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe 2816 powershell.exe -
Suspicious use of AdjustPrivilegeToken 3 IoCs
Processes:
powershell.exe684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exedescription pid process Token: SeDebugPrivilege 2816 powershell.exe Token: SeTcbPrivilege 1580 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe Token: SeTcbPrivilege 1528 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exepid process 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe 1580 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe 1528 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.execmd.execmd.execmd.exe684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exetaskeng.exe684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exedescription pid process target process PID 2188 wrote to memory of 1364 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 1364 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 1364 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 1364 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 2928 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 2928 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 2928 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 2928 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 2748 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 2748 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 2748 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 2748 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe cmd.exe PID 2188 wrote to memory of 2664 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe PID 2188 wrote to memory of 2664 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe PID 2188 wrote to memory of 2664 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe PID 2188 wrote to memory of 2664 2188 574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe PID 1364 wrote to memory of 2560 1364 cmd.exe sc.exe PID 1364 wrote to memory of 2560 1364 cmd.exe sc.exe PID 1364 wrote to memory of 2560 1364 cmd.exe sc.exe PID 1364 wrote to memory of 2560 1364 cmd.exe sc.exe PID 2748 wrote to memory of 2816 2748 cmd.exe powershell.exe PID 2748 wrote to memory of 2816 2748 cmd.exe powershell.exe PID 2748 wrote to memory of 2816 2748 cmd.exe powershell.exe PID 2748 wrote to memory of 2816 2748 cmd.exe powershell.exe PID 2928 wrote to memory of 2284 2928 cmd.exe sc.exe PID 2928 wrote to memory of 2284 2928 cmd.exe sc.exe PID 2928 wrote to memory of 2284 2928 cmd.exe sc.exe PID 2928 wrote to memory of 2284 2928 cmd.exe sc.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 2664 wrote to memory of 2508 2664 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 1640 wrote to memory of 1580 1640 taskeng.exe 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe PID 1640 wrote to memory of 1580 1640 taskeng.exe 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe PID 1640 wrote to memory of 1580 1640 taskeng.exe 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe PID 1640 wrote to memory of 1580 1640 taskeng.exe 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe PID 1580 wrote to memory of 2112 1580 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 1580 wrote to memory of 2112 1580 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 1580 wrote to memory of 2112 1580 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe PID 1580 wrote to memory of 2112 1580 684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe svchost.exe -
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\574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe"C:\Users\Admin\AppData\Local\Temp\574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2188 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:1364 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2560 -
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2928 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2284 -
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2748 -
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:2816 -
C:\Users\Admin\AppData\Roaming\WinSocket\684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exeC:\Users\Admin\AppData\Roaming\WinSocket\684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2664 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2508
-
C:\Windows\system32\taskeng.exetaskeng.exe {944D2D63-F9E2-47B9-93C4-EEE697997EF9} S-1-5-18:NT AUTHORITY\System:Service:1⤵
- Suspicious use of WriteProcessMemory
PID:1640 -
C:\Users\Admin\AppData\Roaming\WinSocket\684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exeC:\Users\Admin\AppData\Roaming\WinSocket\684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1580 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2112
-
C:\Users\Admin\AppData\Roaming\WinSocket\684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exeC:\Users\Admin\AppData\Roaming\WinSocket\684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:1528 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:616
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
\Users\Admin\AppData\Roaming\WinSocket\684480cdfff9376420cad6167e3e2b11f93997a7f969fe391927b38e93f33d62.exe
Filesize1023KB
MD540919a3391314adde33ab0f1456eaf1f
SHA123a42184a115b875e2617df2d2bbcff4111d569a
SHA256574470cdfff8365420cad5156e3e2b11f83996a6f959fe391926b37e83f33d52
SHA5122266e7df9916f8109fa3ec91881e4a7bb7203b0d01b1a23df557a7e5cb26649714907d68e7c11a55bb183db897e8b08d868a1d6c211e17f4c0021805ca50af1e