Analysis
-
max time kernel
190s -
max time network
195s -
platform
windows10-2004_x64 -
resource
win10v2004-20221111-en -
resource tags
arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 14:27
Static task
static1
Behavioral task
behavioral1
Sample
46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe
Resource
win10v2004-20221111-en
General
-
Target
46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe
-
Size
92KB
-
MD5
e84604d5f3128fcaa235f038f209eccc
-
SHA1
bfa65bfd8d23e19dba118fe14fc5148ad007283e
-
SHA256
46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408
-
SHA512
ddab129a70e5fd5d017f0abc87baea11f3fd20ba0aac71444892d229badcfa41065946afabea647d023e1d47b9cce7d73696c35b35abba76a34395dccab26ba9
-
SSDEEP
1536:W633EYF75iNmMwn+PUc9u8YMjzVxhl1GBTIF66gXPUeCLlhZy4/D:bHEYF72mMwnfc9u8YMxlMBTOgXPDChhr
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exedescription pid process target process PID 4368 set thread context of 3304 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
Processes:
46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exepid process 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe -
Suspicious use of WriteProcessMemory 8 IoCs
Processes:
46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exedescription pid process target process PID 4368 wrote to memory of 3304 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe PID 4368 wrote to memory of 3304 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe PID 4368 wrote to memory of 3304 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe PID 4368 wrote to memory of 3304 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe PID 4368 wrote to memory of 3304 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe PID 4368 wrote to memory of 3304 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe PID 4368 wrote to memory of 3304 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe PID 4368 wrote to memory of 3304 4368 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe 46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe"C:\Users\Admin\AppData\Local\Temp\46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:4368 -
C:\Users\Admin\AppData\Local\Temp\46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exeC:\Users\Admin\AppData\Local\Temp\46af311fdcb5a5d3ef7fbb6709ea6cf461ab90b42c119809406d56a80a66c408.exe2⤵PID:3304