Analysis
-
max time kernel
177s -
max time network
202s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
03-10-2022 15:05
Static task
static1
Behavioral task
behavioral1
Sample
1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe
Resource
win10v2004-20220812-en
General
-
Target
1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe
-
Size
67KB
-
MD5
50a671577d6b3c123687da53e5dfb8f1
-
SHA1
2b76917d5bcf6373ddef998a4aa8ad1ddf696f38
-
SHA256
1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4
-
SHA512
5fb0e650c85fef3d3bded5faf43f4cfac5520cbaa22091466cd4ef2469fc33bd37b544c880de5dce1886d12109548164c742cfb48736357ea630dcec0274c745
-
SSDEEP
768:ZNOQUX458LFnbQRn3wcbLiquEWJTsxAUgbdYeSBpyu2/lYnhTUtnRlfGkM1PvSf:2hLpvQiSWJTsxubdtk8/ATCRhGPvU
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4676 set thread context of 4760 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 82 -
Suspicious use of SetWindowsHookEx 4 IoCs
pid Process 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe -
Suspicious use of WriteProcessMemory 8 IoCs
description pid Process procid_target PID 4676 wrote to memory of 4760 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 82 PID 4676 wrote to memory of 4760 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 82 PID 4676 wrote to memory of 4760 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 82 PID 4676 wrote to memory of 4760 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 82 PID 4676 wrote to memory of 4760 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 82 PID 4676 wrote to memory of 4760 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 82 PID 4676 wrote to memory of 4760 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 82 PID 4676 wrote to memory of 4760 4676 1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe 82
Processes
-
C:\Users\Admin\AppData\Local\Temp\1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe"C:\Users\Admin\AppData\Local\Temp\1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4676 -
C:\Users\Admin\AppData\Local\Temp\1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exeC:\Users\Admin\AppData\Local\Temp\1da46153b0849de695bacb3741d6186f2dc102b0d27f6b40c20cef95aef054b4.exe2⤵PID:4760
-