Analysis
-
max time kernel
148s -
max time network
152s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
09-05-2024 06:47
Behavioral task
behavioral1
Sample
fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc.exe
Resource
win7-20240508-en
General
-
Target
fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc.exe
-
Size
1.0MB
-
MD5
88a66b7e4142e224d442891a03f907ac
-
SHA1
016d11c1d8fc7d6346cb47ea0b0688878938aebf
-
SHA256
fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc
-
SHA512
597031b5c581416ab57229972e1c0889113daabaf1ed6c28aac4ac73e10d77799a9b5a343606ffa779839e5d16c2fbe38a62be003439a22b2be3d7e6c62cd179
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQ0+wCIygDsAUkhmZ9skbv:E5aIwC+Agr6SNbt
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x000800000002325f-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/2132-17-0x0000000002C30000-0x0000000002C59000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe Token: SeTcbPrivilege 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 2132 fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc.exe 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 2132 wrote to memory of 2044 2132 fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc.exe 93 PID 2132 wrote to memory of 2044 2132 fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc.exe 93 PID 2132 wrote to memory of 2044 2132 fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc.exe 93 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 2044 wrote to memory of 2036 2044 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 94 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3672 wrote to memory of 4416 3672 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 105 PID 3884 wrote to memory of 3140 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 107 PID 3884 wrote to memory of 3140 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 107 PID 3884 wrote to memory of 3140 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 107 PID 3884 wrote to memory of 3140 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 107 PID 3884 wrote to memory of 3140 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 107 PID 3884 wrote to memory of 3140 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 107 PID 3884 wrote to memory of 3140 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 107 PID 3884 wrote to memory of 3140 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 107 PID 3884 wrote to memory of 3140 3884 fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe 107 -
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\fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc.exe"C:\Users\Admin\AppData\Local\Temp\fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2132 -
C:\Users\Admin\AppData\Roaming\WinSocket\fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exeC:\Users\Admin\AppData\Roaming\WinSocket\fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2044 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:2036
-
-
-
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=808 --field-trial-handle=2676,i,447940133669489189,1353734109898858672,262144 --variations-seed-version /prefetch:81⤵PID:2496
-
C:\Users\Admin\AppData\Roaming\WinSocket\fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exeC:\Users\Admin\AppData\Roaming\WinSocket\fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3672 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4416
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exeC:\Users\Admin\AppData\Roaming\WinSocket\fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3884 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:3140
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
C:\Users\Admin\AppData\Roaming\WinSocket\fe01dcffe7a7f99e13bd28cbfeec60ba0477884deb21b619dce6e91ed3b90ddc.exe
Filesize1.0MB
MD588a66b7e4142e224d442891a03f907ac
SHA1016d11c1d8fc7d6346cb47ea0b0688878938aebf
SHA256fe01dcffe6a6f98e13bd27cbfeec50ba0466774deb21b518dce5e91ed3b80ddc
SHA512597031b5c581416ab57229972e1c0889113daabaf1ed6c28aac4ac73e10d77799a9b5a343606ffa779839e5d16c2fbe38a62be003439a22b2be3d7e6c62cd179
-
Filesize
31KB
MD5a56c1aa6e73efa9710409b26a0876927
SHA116e604dd6043fb401e35c8121d5b30985e60446f
SHA2560b8ed360abc8ca848167bc93e55c64dd1be4f60ae368b5d040af3b9979452d16
SHA512496819b6b47b3fc0ab9658406aca8a53c7035e5c86730b09a8fd4ee34228f0822d349236a5146eca4340839b74fff38da80dbf305f7bfd8669211d0f827e3ea5