Analysis
-
max time kernel
135s -
max time network
126s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
20-05-2024 01:31
Behavioral task
behavioral1
Sample
acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe
Resource
win7-20240221-en
General
-
Target
acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe
-
Size
1.2MB
-
MD5
48e9485d8d775cff7320240bbbccc228
-
SHA1
9aa8e67956a79db31d8029bf5262a0499f65aea9
-
SHA256
acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5
-
SHA512
7818707bf3b6f30eb965c812ac509d336f62bdc7fdc1839d9405cf2dc0b2b9c6228f6ff613b9c8dfa2c5470d23e6ab142da8d2bfba616768c79edad98306933a
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQt+4En+bcMAOxA5zYlo1c51WnKiN:E5aIwC+Agr6StVEnmcKxY/O10
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral1/files/0x000800000001630b-20.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral1/memory/2728-15-0x0000000000480000-0x00000000004A9000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 2248 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 1920 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe -
Loads dropped DLL 2 IoCs
pid Process 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.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 2424 sc.exe 2648 sc.exe 2616 sc.exe 2752 sc.exe -
Suspicious behavior: EnumeratesProcesses 8 IoCs
pid Process 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 2412 powershell.exe 2636 powershell.exe -
Suspicious use of AdjustPrivilegeToken 4 IoCs
description pid Process Token: SeDebugPrivilege 2412 powershell.exe Token: SeDebugPrivilege 2636 powershell.exe Token: SeTcbPrivilege 2248 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe Token: SeTcbPrivilege 1920 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 2248 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 1920 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2728 wrote to memory of 2668 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 28 PID 2728 wrote to memory of 2668 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 28 PID 2728 wrote to memory of 2668 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 28 PID 2728 wrote to memory of 2668 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 28 PID 2728 wrote to memory of 2696 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 29 PID 2728 wrote to memory of 2696 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 29 PID 2728 wrote to memory of 2696 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 29 PID 2728 wrote to memory of 2696 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 29 PID 2728 wrote to memory of 2552 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 32 PID 2728 wrote to memory of 2552 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 32 PID 2728 wrote to memory of 2552 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 32 PID 2728 wrote to memory of 2552 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 32 PID 2728 wrote to memory of 2560 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 34 PID 2728 wrote to memory of 2560 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 34 PID 2728 wrote to memory of 2560 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 34 PID 2728 wrote to memory of 2560 2728 acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe 34 PID 2696 wrote to memory of 2752 2696 cmd.exe 35 PID 2696 wrote to memory of 2752 2696 cmd.exe 35 PID 2696 wrote to memory of 2752 2696 cmd.exe 35 PID 2696 wrote to memory of 2752 2696 cmd.exe 35 PID 2668 wrote to memory of 2424 2668 cmd.exe 36 PID 2668 wrote to memory of 2424 2668 cmd.exe 36 PID 2668 wrote to memory of 2424 2668 cmd.exe 36 PID 2668 wrote to memory of 2424 2668 cmd.exe 36 PID 2552 wrote to memory of 2412 2552 cmd.exe 37 PID 2552 wrote to memory of 2412 2552 cmd.exe 37 PID 2552 wrote to memory of 2412 2552 cmd.exe 37 PID 2552 wrote to memory of 2412 2552 cmd.exe 37 PID 2560 wrote to memory of 2156 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 38 PID 2560 wrote to memory of 2156 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 38 PID 2560 wrote to memory of 2156 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 38 PID 2560 wrote to memory of 2156 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 38 PID 2560 wrote to memory of 2452 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 39 PID 2560 wrote to memory of 2452 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 39 PID 2560 wrote to memory of 2452 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 39 PID 2560 wrote to memory of 2452 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 39 PID 2560 wrote to memory of 2472 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 40 PID 2560 wrote to memory of 2472 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 40 PID 2560 wrote to memory of 2472 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 40 PID 2560 wrote to memory of 2472 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 40 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 PID 2560 wrote to memory of 2444 2560 acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe 42 -
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\acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe"C:\Users\Admin\AppData\Local\Temp\acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5.exe"1⤵
- Loads dropped DLL
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2728 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2668 -
C:\Windows\SysWOW64\sc.exesc stop WinDefend3⤵
- Launches sc.exe
PID:2424
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend2⤵
- Suspicious use of WriteProcessMemory
PID:2696 -
C:\Windows\SysWOW64\sc.exesc delete WinDefend3⤵
- Launches sc.exe
PID:2752
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true2⤵
- Suspicious use of WriteProcessMemory
PID:2552 -
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:2412
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exeC:\Users\Admin\AppData\Roaming\WinSocket\acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe2⤵
- Executes dropped EXE
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2560 -
C:\Windows\SysWOW64\cmd.exe/c sc stop WinDefend3⤵PID:2156
-
C:\Windows\SysWOW64\sc.exesc stop WinDefend4⤵
- Launches sc.exe
PID:2616
-
-
-
C:\Windows\SysWOW64\cmd.exe/c sc delete WinDefend3⤵PID:2452
-
C:\Windows\SysWOW64\sc.exesc delete WinDefend4⤵
- Launches sc.exe
PID:2648
-
-
-
C:\Windows\SysWOW64\cmd.exe/c powershell Set-MpPreference -DisableRealtimeMonitoring $true3⤵PID:2472
-
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:2636
-
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2444
-
-
-
C:\Windows\system32\taskeng.exetaskeng.exe {23BBA2B3-01CD-4500-BA52-B4F874913011} S-1-5-18:NT AUTHORITY\System:Service:1⤵PID:2936
-
C:\Users\Admin\AppData\Roaming\WinSocket\acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exeC:\Users\Admin\AppData\Roaming\WinSocket\acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:2248 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2352
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exeC:\Users\Admin\AppData\Roaming\WinSocket\acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe2⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
PID:1920 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1980
-
-
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
MD5612cb28e3ae5eeeb2477cc840acdff26
SHA1a79a3c95d283bd2474c10329fbd8d84cc1543d5f
SHA256f813f996c2b78e590caa500f75137dfcd03f6c6f2b686180cb6b749ebe1fc144
SHA5124763d31ac715b58821d5de9c46132bb2936ddbf1843bcbc1be979699c8aba3a9684df7fce39b71e893e9c0174dd17d65a34231a08d9fac88a59378a7d312a40d
-
\Users\Admin\AppData\Roaming\WinSocket\acfcd9da971a90a1a9a9f86f67ee2a440b0c29f821679e0b9bdf80a90799a2c6.exe
Filesize1.2MB
MD548e9485d8d775cff7320240bbbccc228
SHA19aa8e67956a79db31d8029bf5262a0499f65aea9
SHA256acfcd8da961a90a1a8a8f75f56ee2a440b0c28f721569e0b9bdf70a90689a2c5
SHA5127818707bf3b6f30eb965c812ac509d336f62bdc7fdc1839d9405cf2dc0b2b9c6228f6ff613b9c8dfa2c5470d23e6ab142da8d2bfba616768c79edad98306933a