Analysis
- max time kernel
152s - max time network
163s - platform
windows10-2004_x64 - resource
win10v2004-20240226-en - resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system - submitted
05/05/2024, 23:19
Behavioral task
behavioral1
Sample
72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113.exe
Resource
win7-20240221-en
14 signatures
150 seconds
General
- Target 72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113.exe
- Size 1.2MB
- Sample240505-3bb5gshd2w
- SHA256 72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113
- MD5 b4f2ff2967566e64477a3ace749fa9ca
- SHA1 9269f351e8c3fef3470ca0812a11feafb9ead066
- SHA512 883237af4297473b59f0f9b0b9ea5bdfe7c7fc40425d7217ccfee58dd7f2af417d3950518f0c896f53f25557ed6d133de9f6cdfab1e64987d6d236355add6faa
- SSDEEP 24576:zQ5aILMCfmAUjzX6gfU1pjwjbsXhmvZssrD+nRgnf4NvlOSxw:E5aIwC+Agr6g81p1vsrNixw
- MD5 SHA1 SHA512 SSDEEP
Malware Config
Signatures
- KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x000800000002325b-21.dat family_kpot - Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/824-16-0x00000000023A0000-0x00000000023C9000-memory.dmp trickbot_loader32 - Executes dropped EXE 3 IoCs
pid Process 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe - Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe Token: SeTcbPrivilege 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe - Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 824 72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113.exe 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe - Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 824 wrote to memory of 488 824 72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113.exe 90 PID 824 wrote to memory of 488 824 72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113.exe 90 PID 824 wrote to memory of 488 824 72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113.exe 90 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 488 wrote to memory of 4900 488 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 91 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 4368 wrote to memory of 1164 4368 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 102 PID 2028 wrote to memory of 2220 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 104 PID 2028 wrote to memory of 2220 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 104 PID 2028 wrote to memory of 2220 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 104 PID 2028 wrote to memory of 2220 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 104 PID 2028 wrote to memory of 2220 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 104 PID 2028 wrote to memory of 2220 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 104 PID 2028 wrote to memory of 2220 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 104 PID 2028 wrote to memory of 2220 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 104 PID 2028 wrote to memory of 2220 2028 82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe 104 - 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\72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113.exe"C:\Users\Admin\AppData\Local\Temp\72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:824 -
C:\Users\Admin\AppData\Roaming\WinSocket\82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exeC:\Users\Admin\AppData\Roaming\WinSocket\82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:488 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:4900
-
-
-
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 --mojo-platform-channel-handle=3804 --field-trial-handle=2280,i,11703952675008463361,17436195144517971517,262144 --variations-seed-version /prefetch:81⤵PID:3208
-
C:\Users\Admin\AppData\Roaming\WinSocket\82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exeC:\Users\Admin\AppData\Roaming\WinSocket\82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4368 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:1164
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exeC:\Users\Admin\AppData\Roaming\WinSocket\82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2028 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:2220
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
- Path C:\Users\Admin\AppData\Roaming\WinSocket\82f8966101d02ecdb221a4d4da3434f2b47cad2449f906efcea347338a09f113.exe
- Size 1.2MB
- SHA256 72f7955101d02ecdb221a4d4da3434f2b46cad2449f805efcea346337a09f113
- MD5 b4f2ff2967566e64477a3ace749fa9ca
- SHA1 9269f351e8c3fef3470ca0812a11feafb9ead066
- SHA512 883237af4297473b59f0f9b0b9ea5bdfe7c7fc40425d7217ccfee58dd7f2af417d3950518f0c896f53f25557ed6d133de9f6cdfab1e64987d6d236355add6faa
- SSDEEP 24576:zQ5aILMCfmAUjzX6gfU1pjwjbsXhmvZssrD+nRgnf4NvlOSxw:E5aIwC+Agr6g81p1vsrNixw
- MD5 SHA1 SHA512 SSDEEP