Analysis
-
max time kernel
149s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240508-en -
resource tags
arch:x64arch:x86image:win10v2004-20240508-enlocale:en-usos:windows10-2004-x64system -
submitted
17-05-2024 21:52
Static task
static1
Behavioral task
behavioral1
Sample
3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe
Resource
win7-20240508-en
General
-
Target
3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe
-
Size
1.0MB
-
MD5
3d5674bd44f36a5d8ffbec8ea0d39c80
-
SHA1
40448b4ce64377f0898cec5d694b9dde69971c34
-
SHA256
c6bcd9175bfa3c5deab49216a11fb6e3246462705eff509a07ac2c4237c81288
-
SHA512
c67375f866df2840faa1a7a3fc219d8248a314a83d28e7dfc6cc8442b4e198ec5329c88d58572180808893ac1c6c51cbabfa853268a7a7595eb64075235eac88
-
SSDEEP
24576:zQ5aILMCfmAUhrSO1YNWdvCzMPqdUD6dNXfptllb5:E5aIwC+AUBsWsXRl
Malware Config
Signatures
-
Trickbot x86 loader 1 IoCs
Detected Trickbot's x86 loader that unpacks the x86 payload.
Processes:
resource yara_rule behavioral2/memory/3280-15-0x0000000002470000-0x0000000002499000-memory.dmp trickbot_loader32 -
Executes dropped EXE 3 IoCs
Processes:
3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exepid process 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe -
Suspicious use of AdjustPrivilegeToken 2 IoCs
Processes:
3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exedescription pid process Token: SeTcbPrivilege 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe Token: SeTcbPrivilege 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe -
Suspicious use of SetWindowsHookEx 4 IoCs
Processes:
3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exepid process 3280 3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exedescription pid process target process PID 3280 wrote to memory of 4768 3280 3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe PID 3280 wrote to memory of 4768 3280 3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe PID 3280 wrote to memory of 4768 3280 3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 4768 wrote to memory of 3612 4768 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 672 wrote to memory of 4760 672 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 404 wrote to memory of 3176 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 404 wrote to memory of 3176 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 404 wrote to memory of 3176 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 404 wrote to memory of 3176 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 404 wrote to memory of 3176 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 404 wrote to memory of 3176 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 404 wrote to memory of 3176 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 404 wrote to memory of 3176 404 3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe svchost.exe PID 404 wrote to memory of 3176 404 3d6784bd44f37a6d9ffbec9ea0d39c90_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\3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe"C:\Users\Admin\AppData\Local\Temp\3d5674bd44f36a5d8ffbec8ea0d39c80_NeikiAnalytics.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3280 -
C:\Users\Admin\AppData\Roaming\WinSocket\3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exeC:\Users\Admin\AppData\Roaming\WinSocket\3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe2⤵
- Executes dropped EXE
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4768 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe3⤵PID:3612
-
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exeC:\Users\Admin\AppData\Roaming\WinSocket\3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:672 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:4760
-
-
C:\Users\Admin\AppData\Roaming\WinSocket\3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exeC:\Users\Admin\AppData\Roaming\WinSocket\3d6784bd44f37a6d9ffbec9ea0d39c90_NeikiAnalytict.exe1⤵
- Executes dropped EXE
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:404 -
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe2⤵PID:3176
-
Network
MITRE ATT&CK Enterprise v15
Replay Monitor
Loading Replay Monitor...
Downloads
-
Filesize
1.0MB
MD53d5674bd44f36a5d8ffbec8ea0d39c80
SHA140448b4ce64377f0898cec5d694b9dde69971c34
SHA256c6bcd9175bfa3c5deab49216a11fb6e3246462705eff509a07ac2c4237c81288
SHA512c67375f866df2840faa1a7a3fc219d8248a314a83d28e7dfc6cc8442b4e198ec5329c88d58572180808893ac1c6c51cbabfa853268a7a7595eb64075235eac88
-
Filesize
58KB
MD5527105402e97aa98f7bafcc94cf05881
SHA100074a3affdb9f4af98d41671c2d9a01f78acea8
SHA256206cb5c2b6100905a674bee41afda807b18ebc246a4d417e33fe9deab4e58cba
SHA5123f716ccaade98fbf95e64330108168ede25442231e0437ce916b9b3ee7d0b0bdc49c004b11b1df646944a4fc296ae47e02f5875be6dc3fb21b27363c96f6b7e2