Analysis
-
max time kernel
148s -
max time network
151s -
platform
windows10-2004_x64 -
resource
win10v2004-20240426-en -
resource tags
arch:x64arch:x86image:win10v2004-20240426-enlocale:en-usos:windows10-2004-x64system -
submitted
22-05-2024 01:39
Static task
static1
Behavioral task
behavioral1
Sample
5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe
Resource
win7-20240508-en
Behavioral task
behavioral2
Sample
5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe
Resource
win10v2004-20240426-en
General
-
Target
5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe
-
Size
704KB
-
MD5
ad2f2ae2bc107514560edf4a194809b2
-
SHA1
797f218a150eaa1061f162c90a1feb588c2885ba
-
SHA256
5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078
-
SHA512
d19e68977684b7d732dcad1f27c011d94f75b217c71c4773399667a2248d10a938eabdc853416a8073e458d121f9a4fe91bc74197455f5163912c2a28d9c13cb
-
SSDEEP
12288:qXYifT+sc0vd3O2FMyjUVxRX3DntyzFk44+J5DvyIj/ku8bETDkR:qIiCsc013O2FMkUVxRHJyzZdykMDbyW
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
Processes:
5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exedescription pid process target process PID 1920 set thread context of 4248 1920 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe -
Program crash 1 IoCs
Processes:
WerFault.exepid pid_target process target process 5552 4248 WerFault.exe 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
Processes:
5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exepid process 4248 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe 4248 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe -
Suspicious use of WriteProcessMemory 6 IoCs
Processes:
5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exedescription pid process target process PID 1920 wrote to memory of 4248 1920 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe PID 1920 wrote to memory of 4248 1920 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe PID 1920 wrote to memory of 4248 1920 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe PID 1920 wrote to memory of 4248 1920 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe PID 1920 wrote to memory of 4248 1920 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe PID 1920 wrote to memory of 4248 1920 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe 5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe
Processes
-
C:\Users\Admin\AppData\Local\Temp\5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe"C:\Users\Admin\AppData\Local\Temp\5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1920 -
C:\Users\Admin\AppData\Local\Temp\5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe"C:\Users\Admin\AppData\Local\Temp\5a37d37c6e25e6f8f3e181dbc9b6ed6f1e173cb4d7ed4c8bd914e8c7bef14078.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
PID:4248 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4248 -s 1883⤵
- Program crash
PID:5552
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 408 -p 4248 -ip 42481⤵PID:3536