Analysis
-
max time kernel
148s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240704-en -
resource tags
arch:x64arch:x86image:win10v2004-20240704-enlocale:en-usos:windows10-2004-x64system -
submitted
04-07-2024 19:13
Behavioral task
behavioral1
Sample
186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0.exe
Resource
win7-20240220-en
General
-
Target
186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0.exe
-
Size
1.3MB
-
MD5
0359f4837e843248e96a967edde37779
-
SHA1
e1dcb3d426b9284f78990b8d56627447bad1480a
-
SHA256
186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0
-
SHA512
5be6597570844df99d1ab43151ffdaa3793519fd8dde811aff211254421bdb2486f880110d8ed0ebe3df80b60717603821fa42f8568da98fdc1a0541d19d525a
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQtjmssdqex1hl+dZNNVpr:E5aIwC+Agr6StYCNV
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x0008000000023420-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/968-15-0x0000000002200000-0x0000000002229000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe Token: SeTcbPrivilege 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 968 186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0.exe 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 968 wrote to memory of 368 968 186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0.exe 78 PID 968 wrote to memory of 368 968 186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0.exe 78 PID 968 wrote to memory of 368 968 186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0.exe 78 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 368 wrote to memory of 1492 368 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 79 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 628 wrote to memory of 2636 628 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 81 PID 1760 wrote to memory of 1564 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 83 PID 1760 wrote to memory of 1564 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 83 PID 1760 wrote to memory of 1564 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 83 PID 1760 wrote to memory of 1564 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 83 PID 1760 wrote to memory of 1564 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 83 PID 1760 wrote to memory of 1564 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 83 PID 1760 wrote to memory of 1564 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 83 PID 1760 wrote to memory of 1564 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 83 PID 1760 wrote to memory of 1564 1760 197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe 83 -
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\186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0.exe"C:\Users\Admin\AppData\Local\Temp\186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:968 -
C:\Users\Admin\AppData\Roaming\WinSocket\197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exeC:\Users\Admin\AppData\Roaming\WinSocket\197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:368 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1492
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exeC:\Users\Admin\AppData\Roaming\WinSocket\197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:628 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2636
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exeC:\Users\Admin\AppData\Roaming\WinSocket\197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1760 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:1564
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\197bde94e02917a477db3bb188c8e222dd46ff79aae1a9f0097023fd02d61af0.exe
Filesize1.3MB
MD50359f4837e843248e96a967edde37779
SHA1e1dcb3d426b9284f78990b8d56627447bad1480a
SHA256186bde84e02816a466db3bb177c7e222dd45ff68aae1a8f0096023fd02d51af0
SHA5125be6597570844df99d1ab43151ffdaa3793519fd8dde811aff211254421bdb2486f880110d8ed0ebe3df80b60717603821fa42f8568da98fdc1a0541d19d525a
-
Filesize
67KB
MD57122edaa15a9bdafb9dfed28fe7d0ccb
SHA1a6850f5002fde894772ab146b5e1b1b66eb90d69
SHA256f51b36ed5dd55a6f3ecd2cca6be85410bae1c5198affbc69b69b722502d34ca4
SHA512579dd75aabe35ea518e0aeef3d90cc2b831e1c484c7216814a02c4ebe224f037f42297837113a57626540ba0c8ebc5f72e539094bd4ba2fcd9d53ea2a8772553