Analysis
-
max time kernel
145s -
max time network
152s -
platform
windows7_x64 -
resource
win7-20220718-en -
resource tags
arch:x64arch:x86image:win7-20220718-enlocale:en-usos:windows7-x64system -
submitted
25-07-2022 03:27
Static task
static1
Behavioral task
behavioral1
Sample
566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe
Resource
win7-20220718-en
Behavioral task
behavioral2
Sample
566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe
Resource
win10v2004-20220721-en
General
-
Target
566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe
-
Size
80KB
-
MD5
18da837214548fa02d79daf0b0f0b169
-
SHA1
16eee90a7cf6987f31fe2ec7235f7623db5b2c83
-
SHA256
566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2
-
SHA512
aa28f748cda74d8b7fc9b82b02eb8f66a1479242cd75cb39b621b8955a3aad2a0734c6709055e1b736fa7cf8a6ab8d417a97a8e35c7744181546e944fbb9c4da
Malware Config
Signatures
-
suricata: ET MALWARE Possible Kelihos.F EXE Download Common Structure
suricata: ET MALWARE Possible Kelihos.F EXE Download Common Structure
-
Processes:
resource yara_rule behavioral1/memory/1096-58-0x0000000000400000-0x0000000002728000-memory.dmp upx behavioral1/memory/1096-60-0x0000000000400000-0x0000000002728000-memory.dmp upx behavioral1/memory/1096-62-0x0000000000400000-0x0000000002728000-memory.dmp upx behavioral1/memory/1096-67-0x0000000000400000-0x0000000000409000-memory.dmp upx behavioral1/memory/1096-68-0x0000000000400000-0x0000000002728000-memory.dmp upx behavioral1/memory/1096-69-0x0000000000400000-0x0000000002728000-memory.dmp upx behavioral1/memory/1096-70-0x0000000000400000-0x0000000000409000-memory.dmp upx behavioral1/memory/1096-71-0x0000000000400000-0x0000000000409000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
Processes:
566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exedescription pid process target process PID 640 set thread context of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe -
Suspicious behavior: EnumeratesProcesses 1 IoCs
Processes:
566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exepid process 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
Processes:
566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exepid process 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe -
Suspicious use of WriteProcessMemory 9 IoCs
Processes:
566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exedescription pid process target process PID 640 wrote to memory of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe PID 640 wrote to memory of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe PID 640 wrote to memory of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe PID 640 wrote to memory of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe PID 640 wrote to memory of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe PID 640 wrote to memory of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe PID 640 wrote to memory of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe PID 640 wrote to memory of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe PID 640 wrote to memory of 1096 640 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe 566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe"C:\Users\Admin\AppData\Local\Temp\566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
-
C:\Users\Admin\AppData\Local\Temp\566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe"C:\Users\Admin\AppData\Local\Temp\566b27b2e37ebeeb1daa5cfef58a5504964738380c364a46c4fa27adbbd2d3c2.exe"2⤵
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/640-61-0x0000000000400000-0x0000000000408000-memory.dmpFilesize
32KB
-
memory/640-64-0x00000000003E0000-0x00000000003E8000-memory.dmpFilesize
32KB
-
memory/640-63-0x00000000002D0000-0x00000000002D4000-memory.dmpFilesize
16KB
-
memory/640-54-0x0000000076921000-0x0000000076923000-memory.dmpFilesize
8KB
-
memory/1096-58-0x0000000000400000-0x0000000002728000-memory.dmpFilesize
35.2MB
-
memory/1096-57-0x0000000000400000-0x0000000002728000-memory.dmpFilesize
35.2MB
-
memory/1096-55-0x00000000001B0000-0x00000000002AA000-memory.dmpFilesize
1000KB
-
memory/1096-60-0x0000000000400000-0x0000000002728000-memory.dmpFilesize
35.2MB
-
memory/1096-65-0x00000000004076B0-mapping.dmp
-
memory/1096-62-0x0000000000400000-0x0000000002728000-memory.dmpFilesize
35.2MB
-
memory/1096-67-0x0000000000400000-0x0000000000409000-memory.dmpFilesize
36KB
-
memory/1096-68-0x0000000000400000-0x0000000002728000-memory.dmpFilesize
35.2MB
-
memory/1096-69-0x0000000000400000-0x0000000002728000-memory.dmpFilesize
35.2MB
-
memory/1096-70-0x0000000000400000-0x0000000000409000-memory.dmpFilesize
36KB
-
memory/1096-71-0x0000000000400000-0x0000000000409000-memory.dmpFilesize
36KB