Analysis
-
max time kernel
184s -
max time network
204s -
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 10:09
Static task
static1
Behavioral task
behavioral1
Sample
c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe
Resource
win7-20220901-en
windows7-x64
4 signatures
150 seconds
Behavioral task
behavioral2
Sample
c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe
Resource
win10v2004-20221111-en
windows10-2004-x64
4 signatures
150 seconds
General
-
Target
c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe
-
Size
358KB
-
MD5
a8bb2107d489d3541570028a935bab85
-
SHA1
2b6e661e14d039128a4af22a4c8f4073826d3d17
-
SHA256
c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62
-
SHA512
966d1459c294b7f88e18230ac524e57486655cefa27dfd9e55257663a4fb0618a3dd73c9aac7963b0ee18aa25200611353fc27d9cf61e7d52905df22b8a47f59
-
SSDEEP
3072:9kU7OYG1wgZfY4gZfYvwxnWEGPHQpwZwj:/796ZwzZw4xLywmZk
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3880 set thread context of 4068 3880 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 81 -
Suspicious behavior: EnumeratesProcesses 4 IoCs
pid Process 4068 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 4068 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 4068 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 4068 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 3880 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 3880 wrote to memory of 4068 3880 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 81 PID 3880 wrote to memory of 4068 3880 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 81 PID 3880 wrote to memory of 4068 3880 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 81 PID 3880 wrote to memory of 4068 3880 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 81 PID 3880 wrote to memory of 4068 3880 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 81 PID 3880 wrote to memory of 4068 3880 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 81 PID 3880 wrote to memory of 4068 3880 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 81 PID 4068 wrote to memory of 1192 4068 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 46 PID 4068 wrote to memory of 1192 4068 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 46 PID 4068 wrote to memory of 1192 4068 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 46 PID 4068 wrote to memory of 1192 4068 c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe 46
Processes
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1192
-
C:\Users\Admin\AppData\Local\Temp\c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe"C:\Users\Admin\AppData\Local\Temp\c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:3880 -
C:\Users\Admin\AppData\Local\Temp\c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exeC:\Users\Admin\AppData\Local\Temp\c6ec9b816ab6394fa4a53be91dbae011238eda8c5ed4c74c3c802ae543791f62.exe3⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of WriteProcessMemory
PID:4068
-
-