Analysis
-
max time kernel
143s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
08-05-2024 03:10
Behavioral task
behavioral1
Sample
b5405e989aa2de26a5f40d60671e2fc0_NEIKI.exe
Resource
win7-20240220-en
General
-
Target
b5405e989aa2de26a5f40d60671e2fc0_NEIKI.exe
-
Size
1.1MB
-
MD5
b5405e989aa2de26a5f40d60671e2fc0
-
SHA1
586e458daf79bef6ae7ce85da6abf07f7c81622d
-
SHA256
fb8001ca430aa77ad5855c489652b607ebd2f62447f2c381101d48d6d389b229
-
SHA512
fd9a1aee373b645eb15d324247fdc1c8be45840b0967953c13a3fde56b5733e2192067bf2378190933912d2717c76a9407f4f866b3a6124f0295cca432a080a5
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQGCZLFdGm1StE10/ZcnDPc2:E5aIwC+Agr6S/FFC+Lc2
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
resource yara_rule behavioral2/files/0x0008000000023263-21.dat family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
resource yara_rule behavioral2/memory/792-16-0x0000000003110000-0x0000000003139000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
pid Process 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
description pid Process Token: SeTcbPrivilege 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe Token: SeTcbPrivilege 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 792 b5405e989aa2de26a5f40d60671e2fc0_NEIKI.exe 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 792 wrote to memory of 2880 792 b5405e989aa2de26a5f40d60671e2fc0_NEIKI.exe 90 PID 792 wrote to memory of 2880 792 b5405e989aa2de26a5f40d60671e2fc0_NEIKI.exe 90 PID 792 wrote to memory of 2880 792 b5405e989aa2de26a5f40d60671e2fc0_NEIKI.exe 90 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 2880 wrote to memory of 704 2880 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 91 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 4168 wrote to memory of 4552 4168 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 102 PID 1900 wrote to memory of 1148 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 104 PID 1900 wrote to memory of 1148 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 104 PID 1900 wrote to memory of 1148 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 104 PID 1900 wrote to memory of 1148 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 104 PID 1900 wrote to memory of 1148 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 104 PID 1900 wrote to memory of 1148 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 104 PID 1900 wrote to memory of 1148 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 104 PID 1900 wrote to memory of 1148 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe 104 PID 1900 wrote to memory of 1148 1900 b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.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\b5405e989aa2de26a5f40d60671e2fc0_NEIKI.exe"C:\Users\Admin\AppData\Local\Temp\b5405e989aa2de26a5f40d60671e2fc0_NEIKI.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:792 -
C:\Users\Admin\AppData\Roaming\WinSocket\b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exeC:\Users\Admin\AppData\Roaming\WinSocket\b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:2880 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:704
-
-
-
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=3736 --field-trial-handle=3088,i,14310325015283915034,7660943942870463106,262144 --variations-seed-version /prefetch:81⤵PID:1036
-
C:\Users\Admin\AppData\Roaming\WinSocket\b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exeC:\Users\Admin\AppData\Roaming\WinSocket\b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4168 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4552
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exeC:\Users\Admin\AppData\Roaming\WinSocket\b6406e999aa2de27a6f40d70781e2fc0_NFJLJ.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1900 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:1148
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
1.1MB
MD5b5405e989aa2de26a5f40d60671e2fc0
SHA1586e458daf79bef6ae7ce85da6abf07f7c81622d
SHA256fb8001ca430aa77ad5855c489652b607ebd2f62447f2c381101d48d6d389b229
SHA512fd9a1aee373b645eb15d324247fdc1c8be45840b0967953c13a3fde56b5733e2192067bf2378190933912d2717c76a9407f4f866b3a6124f0295cca432a080a5
-
Filesize
27KB
MD568af96c914f19c84fc323d680e4d8869
SHA1a5baf1d4286e7aa44591641f8eb890ca61c21b3a
SHA256a6e93d2b719f7e210c12345fe993af92f9ef5126a91455c907b9adf11fbf3725
SHA51280769e9b87b63d19f39600311213f3967291fddc998c92f27fe5b6b88234da2dfb28261eb9ede3ee3dc2e586ecbe8da8f9cc30db2f89dee1826d595f09d52df6