Analysis
-
max time kernel
141s -
max time network
120s -
platform
windows7_x64 -
resource
win7-20231020-en -
resource tags
arch:x64arch:x86image:win7-20231020-enlocale:en-usos:windows7-x64system -
submitted
13/11/2023, 16:58
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
82c992b793e969ce5a9194956f93d3b6fc10bcca4056e17a35fb56470d63fbf0.exe
Resource
win7-20231020-en
2 signatures
150 seconds
General
-
Target
82c992b793e969ce5a9194956f93d3b6fc10bcca4056e17a35fb56470d63fbf0.exe
-
Size
4.9MB
-
MD5
bc0116e1eb59ba77dee5d0f0cc0d2b41
-
SHA1
3dbd9f0f05989d36e31ce0e53c57c93ce7bfae84
-
SHA256
82c992b793e969ce5a9194956f93d3b6fc10bcca4056e17a35fb56470d63fbf0
-
SHA512
5b43e62bbd8bde4df64f8e80dd40374628d2074600f833f3610e240cc7c625ee7dd1050652ca926071de7bede3b68b3f520590ef6697f599e1aa6f3f4c762306
-
SSDEEP
49152:NolJSAO5fHDRHMDUSlDuZLtSkjGi4+pQ8qIxYvGcBHBTKTLT67siLqe9dhVfq:QPM/LwkqyQruyBTkiLqsh
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2228 2508 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2508 wrote to memory of 2228 2508 82c992b793e969ce5a9194956f93d3b6fc10bcca4056e17a35fb56470d63fbf0.exe 29 PID 2508 wrote to memory of 2228 2508 82c992b793e969ce5a9194956f93d3b6fc10bcca4056e17a35fb56470d63fbf0.exe 29 PID 2508 wrote to memory of 2228 2508 82c992b793e969ce5a9194956f93d3b6fc10bcca4056e17a35fb56470d63fbf0.exe 29 PID 2508 wrote to memory of 2228 2508 82c992b793e969ce5a9194956f93d3b6fc10bcca4056e17a35fb56470d63fbf0.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\82c992b793e969ce5a9194956f93d3b6fc10bcca4056e17a35fb56470d63fbf0.exe"C:\Users\Admin\AppData\Local\Temp\82c992b793e969ce5a9194956f93d3b6fc10bcca4056e17a35fb56470d63fbf0.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2508 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2508 -s 2482⤵
- Program crash
PID:2228
-