Analysis
-
max time kernel
140s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
14-05-2024 10:36
Behavioral task
behavioral1
Sample
c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exe
Resource
win7-20240221-en
General
-
Target
c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exe
-
Size
921KB
-
MD5
c32b3b514199c230727a6671d394d9f0
-
SHA1
41a4d0753e5949395cdf0e6743bd6441f5637ce5
-
SHA256
f6cf48fd583b56af9e05f3a0301fa5643be49cdc4f188392de3e7ba2d7578802
-
SHA512
98e8c252d96ea83a1ffc6da9e10f14bc90d415dd364102acde859d5210b2542dff02108d3c8a08609ee8e094247a926900af29b693f4b35cba6703571574bc00
-
SSDEEP
24576:zQ5aILMCfmAUjzX6xQt+4EnpZgkJOSSkgh:E5aIwC+Agr6StVEn0ksLh
Malware Config
Signatures
-
KPOT Core Executable 1 IoCs
Processes:
resource yara_rule C:\Users\Admin\AppData\Roaming\WinSocket\c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe family_kpot -
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
Processes:
resource yara_rule behavioral2/memory/3128-15-0x0000000002930000-0x0000000002959000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
Processes:
c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exec32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exec32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exepid process 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exec32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exedescription pid process Token: SeTcbPrivilege 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe Token: SeTcbPrivilege 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exec32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exec32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exec32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exepid process 3128 c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exe 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exec32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exec32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exec32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exedescription pid process target process PID 3128 wrote to memory of 4676 3128 c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exe c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe PID 3128 wrote to memory of 4676 3128 c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exe c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe PID 3128 wrote to memory of 4676 3128 c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exe c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 4676 wrote to memory of 516 4676 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 232 wrote to memory of 4392 232 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 1696 wrote to memory of 5096 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 1696 wrote to memory of 5096 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 1696 wrote to memory of 5096 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 1696 wrote to memory of 5096 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 1696 wrote to memory of 5096 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 1696 wrote to memory of 5096 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 1696 wrote to memory of 5096 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 1696 wrote to memory of 5096 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe PID 1696 wrote to memory of 5096 1696 c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe svchost.exe -
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\c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exe"C:\Users\Admin\AppData\Local\Temp\c32b3b514199c230727a6671d394d9f0_NeikiAnalytics.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3128 -
C:\Users\Admin\AppData\Roaming\WinSocket\c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exeC:\Users\Admin\AppData\Roaming\WinSocket\c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4676 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:516
-
-
-
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=4212,i,14486271492189381216,15799931579469722648,262144 --variations-seed-version --mojo-platform-channel-handle=4308 /prefetch:81⤵PID:2708
-
C:\Users\Admin\AppData\Roaming\WinSocket\c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exeC:\Users\Admin\AppData\Roaming\WinSocket\c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:232 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4392
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exeC:\Users\Admin\AppData\Roaming\WinSocket\c32b3b614199c230828a7781d394d9f0_NeikiAnalytict.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1696 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:5096
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
921KB
MD5c32b3b514199c230727a6671d394d9f0
SHA141a4d0753e5949395cdf0e6743bd6441f5637ce5
SHA256f6cf48fd583b56af9e05f3a0301fa5643be49cdc4f188392de3e7ba2d7578802
SHA51298e8c252d96ea83a1ffc6da9e10f14bc90d415dd364102acde859d5210b2542dff02108d3c8a08609ee8e094247a926900af29b693f4b35cba6703571574bc00
-
Filesize
31KB
MD5a1b88738be0995d07a2349f5708a996e
SHA1164c47123e90b210276864bda7e8f9e95f6fda8d
SHA256a1166314cece4f38a12ad6e629a6b2219431876d1196cb0bfc8c17411b44c0e5
SHA51226227f481989cff6ca319dfeac642308de9e4b599b3da1ad8550b7d5552bd8711e722e1ed01525fe3fc217e70b233c97b66a046639d856e592557eb6cb488a62