Analysis
-
max time kernel
175s -
max time network
186s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
23-11-2022 18:34
Behavioral task
behavioral1
Sample
3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe
Resource
win7-20220812-en
Behavioral task
behavioral2
Sample
3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe
Resource
win10v2004-20220812-en
General
-
Target
3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe
-
Size
169KB
-
MD5
2fb5f03adcff452f9bfc899025c43277
-
SHA1
2ef46737c4d610e18d1a6ccd32d4e87ee92a3441
-
SHA256
3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0
-
SHA512
9404db1936455d854f9d7646daca472c423ffdcd6511b2e05b7ef255e4f245fa4f04dd97f3a8ac5cedc181e80982598e7bdfbb55966d922d67c514e9c6b6726d
-
SSDEEP
3072:BcA34s6VxyQYySD2tnSW5SPHOZo1fiqEqxS5oLHUdUohQ/8HFD:yAofVxTSD2muZopiqEq85ogdph
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exedescription pid process PID 5056 set thread context of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exepid process 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe -
Suspicious use of WriteProcessMemory 10 IoCs
Processes:
3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exedescription pid process PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe PID 5056 wrote to memory of 0 5056 3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe"C:\Users\Admin\AppData\Local\Temp\3d41032a06847ed27b1e4a85085330f84ad6249ce39d3b4358de9006db40dab0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5056