Analysis
-
max time kernel
142s -
max time network
157s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
07-06-2024 08:29
Behavioral task
behavioral1
Sample
e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea.exe
Resource
win7-20240221-en
General
-
Target
e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea.exe
-
Size
1.2MB
-
MD5
e73e690ead1546ded59ba3824e02beb2
-
SHA1
71bfaa95c34f0c85f5e614c842a28797fa62d498
-
SHA256
e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea
-
SHA512
7b9fb5e1ba0fa26fd9d4bc219ac449db0d9af73c8c7374ebc84462f00e61ae902f093515ef7ee34080cb5398f0287809606d47926f7feee209d6f0492f78c0e1
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQ0+wCIygDsAUSTsU95QyJ5GdO8bU:E5aIwC+Agr6SNasOJ5T
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x0008000000023278-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/4076-17-0x0000000003130000-0x0000000003159000-memory.dmp trickbot_loader32 -
Executes dropped EXE 2 IoCs
pid Process 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeTcbPrivilege 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe -
Suspicious use of SetWindowsHookEx 3 IoCs
pid Process 4076 e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea.exe 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe -
Suspicious use of WriteProcessMemory 55 IoCs
description pid Process procid_target PID 4076 wrote to memory of 4004 4076 e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea.exe 91 PID 4076 wrote to memory of 4004 4076 e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea.exe 91 PID 4076 wrote to memory of 4004 4076 e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea.exe 91 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 4004 wrote to memory of 32 4004 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 92 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 PID 3824 wrote to memory of 4252 3824 e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe 103 -
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\e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea.exe"C:\Users\Admin\AppData\Local\Temp\e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4076 -
C:\Users\Admin\AppData\Roaming\WinSocket\e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exeC:\Users\Admin\AppData\Roaming\WinSocket\e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4004 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:32
-
-
-
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=4232 --field-trial-handle=2656,i,16940681401824032220,151921362336696246,262144 --variations-seed-version /prefetch:81⤵PID:4152
-
C:\Users\Admin\AppData\Roaming\WinSocket\e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exeC:\Users\Admin\AppData\Roaming\WinSocket\e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3824 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4252
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\e2b9a92c9f4ffe7c0369401d6f07f0299701edfaa27099f87f603fca3236eaea.exe
Filesize1.2MB
MD5e73e690ead1546ded59ba3824e02beb2
SHA171bfaa95c34f0c85f5e614c842a28797fa62d498
SHA256e2b9a92c8f4ffe6c0358401d5f06f0299601edfaa26089f76f503fca3235eaea
SHA5127b9fb5e1ba0fa26fd9d4bc219ac449db0d9af73c8c7374ebc84462f00e61ae902f093515ef7ee34080cb5398f0287809606d47926f7feee209d6f0492f78c0e1