Analysis
-
max time kernel
137s -
max time network
128s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
22-05-2024 13:16
Behavioral task
behavioral1
Sample
30a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11.exe
Resource
win7-20240215-en
General
-
Target
30a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11.exe
-
Size
969KB
-
MD5
1eb537fe9fa3f69e6ab33b6b081f73d0
-
SHA1
d3f207b3e6b889c32b194bd96ba782e371f227eb
-
SHA256
30a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11
-
SHA512
c870646b8060893f613d7ae77ac68635a5561054e06bf1548728b6be4dbfe3ecc997fd2c9d58d377601da6d26a722811e5e972e28cd5e1c92c529b0d2133f4e8
-
SSDEEP
24576:zQ5aILMCfmAUjzX6gfU1pjwjbsmQdmTHeDo:E5aIwC+Agr6g81pb/o
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x000700000002354e-22.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/588-15-0x00000000021F0000-0x0000000002219000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe Token: SeTcbPrivilege 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 588 30a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11.exe 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 588 wrote to memory of 4472 588 30a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11.exe 91 PID 588 wrote to memory of 4472 588 30a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11.exe 91 PID 588 wrote to memory of 4472 588 30a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11.exe 91 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 4472 wrote to memory of 1216 4472 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 92 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 5080 wrote to memory of 968 5080 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 110 PID 3488 wrote to memory of 2004 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 119 PID 3488 wrote to memory of 2004 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 119 PID 3488 wrote to memory of 2004 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 119 PID 3488 wrote to memory of 2004 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 119 PID 3488 wrote to memory of 2004 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 119 PID 3488 wrote to memory of 2004 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 119 PID 3488 wrote to memory of 2004 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 119 PID 3488 wrote to memory of 2004 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 119 PID 3488 wrote to memory of 2004 3488 30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe 119 -
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\30a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11.exe"C:\Users\Admin\AppData\Local\Temp\30a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:588 -
C:\Users\Admin\AppData\Roaming\WinSocket\30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exeC:\Users\Admin\AppData\Roaming\WinSocket\30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4472 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:1216
-
-
-
C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe"C:\Program Files (x86)\Microsoft\Edge\Application\msedge.exe" --type=utility --utility-sub-type=asset_store.mojom.AssetStoreService --lang=en-US --service-sandbox-type=asset_store_service --no-appcompat-clear --field-trial-handle=4356,i,4686244434963378549,11462511444150484980,262144 --variations-seed-version --mojo-platform-channel-handle=1036 /prefetch:81⤵PID:1036
-
C:\Users\Admin\AppData\Roaming\WinSocket\30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exeC:\Users\Admin\AppData\Roaming\WinSocket\30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5080 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:968
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exeC:\Users\Admin\AppData\Roaming\WinSocket\30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3488 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2004
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\30a09e6bf830f47872ce70b98620a1d0e771921e9e89729422c6629bf1fabc11.exe
Filesize969KB
MD51eb537fe9fa3f69e6ab33b6b081f73d0
SHA1d3f207b3e6b889c32b194bd96ba782e371f227eb
SHA25630a09e5bf730f46762ce60b97520a1d0e661921e8e79629422c5528bf1fabc11
SHA512c870646b8060893f613d7ae77ac68635a5561054e06bf1548728b6be4dbfe3ecc997fd2c9d58d377601da6d26a722811e5e972e28cd5e1c92c529b0d2133f4e8
-
Filesize
23KB
MD5c46bbb03cff676289c97909e18a04ad0
SHA1cdb890204456795764fd0e0b00f2b7b6410d0757
SHA256653fbd3ea48ea9e7de0785c3330c9ba3212b866218a0a3e50a460535c08ddb99
SHA512e0f9f71f793850a59fc3779cf5455e33b614bd0183787576e0b26cb712da690140261a66e796e4f8c625ea61955fd78768e845b71509788a2e2d6d4c563aeb43