Analysis
-
max time kernel
171s -
max time network
222s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
04-12-2022 02:28
Static task
static1
Behavioral task
behavioral1
Sample
f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe
Resource
win10v2004-20221111-en
General
-
Target
f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe
-
Size
125KB
-
MD5
7d23338c286e01e10bfae7e253edd043
-
SHA1
3187595fdda6172f962000c1ee2d8e3caa961561
-
SHA256
f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930
-
SHA512
a3be806b2cbf9327e1017a3dce327fd6de9c314a2b25f94e02852cd242a1a37c0ad37d989456cd08f4c764d6576c762f1ca1d0daf77b920be2ce69fefca748e3
-
SSDEEP
3072:HExnQVo6RxSITNCzXfQg/trv0CyS8kfEk694R:HE+Vo6kzXfQatrcSD69G
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/600-135-0x0000000000400000-0x000000000043C000-memory.dmp upx behavioral2/memory/600-137-0x0000000000400000-0x000000000043C000-memory.dmp upx behavioral2/memory/600-138-0x0000000000400000-0x000000000043C000-memory.dmp upx behavioral2/memory/600-141-0x0000000000400000-0x000000000043C000-memory.dmp upx behavioral2/memory/600-146-0x0000000000400000-0x000000000043C000-memory.dmp upx -
Suspicious use of SetThreadContext 3 IoCs
description pid Process procid_target PID 880 set thread context of 600 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 82 PID 600 set thread context of 3640 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 83 PID 600 set thread context of 0 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 3640 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 3640 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 3640 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 3640 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe -
Suspicious use of WriteProcessMemory 23 IoCs
description pid Process procid_target PID 880 wrote to memory of 600 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 82 PID 880 wrote to memory of 600 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 82 PID 880 wrote to memory of 600 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 82 PID 880 wrote to memory of 600 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 82 PID 880 wrote to memory of 600 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 82 PID 880 wrote to memory of 600 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 82 PID 880 wrote to memory of 600 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 82 PID 880 wrote to memory of 600 880 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 82 PID 600 wrote to memory of 3640 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 83 PID 600 wrote to memory of 3640 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 83 PID 600 wrote to memory of 3640 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 83 PID 600 wrote to memory of 3640 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 83 PID 600 wrote to memory of 3640 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 83 PID 600 wrote to memory of 3640 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 83 PID 600 wrote to memory of 3640 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 83 PID 600 wrote to memory of 0 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe PID 600 wrote to memory of 0 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe PID 600 wrote to memory of 0 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe PID 600 wrote to memory of 0 600 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe PID 3640 wrote to memory of 1036 3640 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 28 PID 3640 wrote to memory of 1036 3640 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 28 PID 3640 wrote to memory of 1036 3640 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 28 PID 3640 wrote to memory of 1036 3640 f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe 28
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1036
-
C:\Users\Admin\AppData\Local\Temp\f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe"C:\Users\Admin\AppData\Local\Temp\f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:880 -
C:\Users\Admin\AppData\Local\Temp\f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exeC:\Users\Admin\AppData\Local\Temp\f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe3⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:600 -
C:\Users\Admin\AppData\Local\Temp\f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe"C:\Users\Admin\AppData\Local\Temp\f62803909949f5b7fb5423ae9d13eca36d4dd697266e89d9ee316a5b43432930.exe"4⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:3640
-
-
-