Analysis
-
max time kernel
117s -
max time network
120s -
platform
windows7_x64 -
resource
win7-20231215-en -
resource tags
arch:x64arch:x86image:win7-20231215-enlocale:en-usos:windows7-x64system -
submitted
20-02-2024 20:24
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-02-20_da0e6298fbf40a603485661e87fe6459_virlock.exe
Resource
win7-20231215-en
windows7-x64
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-02-20_da0e6298fbf40a603485661e87fe6459_virlock.exe
Resource
win10v2004-20240220-en
windows10-2004-x64
1 signatures
150 seconds
General
-
Target
2024-02-20_da0e6298fbf40a603485661e87fe6459_virlock.exe
-
Size
196KB
-
MD5
da0e6298fbf40a603485661e87fe6459
-
SHA1
3aa102d8c5f922b3d3f19097b6dd5faaed32c300
-
SHA256
2c69a5aa02af14813432d2d6ce10f0590ad1be2ff01284b37817f855b417806f
-
SHA512
122d06eaa6d57ad7ff7fb4d184874fd3b34807453bbe202b238bf75b5abad5def9796fc7bd7c098818e08a36806b5b021724cf75def136f4a9ca2102ab765cb6
-
SSDEEP
6144:vufu14EUVVVlgZmrEnWF3RtXo30GPyVdYuYZ:G2Ki4JoElVdy
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2520 1220 WerFault.exe 19 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 1220 wrote to memory of 2520 1220 2024-02-20_da0e6298fbf40a603485661e87fe6459_virlock.exe 28 PID 1220 wrote to memory of 2520 1220 2024-02-20_da0e6298fbf40a603485661e87fe6459_virlock.exe 28 PID 1220 wrote to memory of 2520 1220 2024-02-20_da0e6298fbf40a603485661e87fe6459_virlock.exe 28 PID 1220 wrote to memory of 2520 1220 2024-02-20_da0e6298fbf40a603485661e87fe6459_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-02-20_da0e6298fbf40a603485661e87fe6459_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-02-20_da0e6298fbf40a603485661e87fe6459_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:1220 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1220 -s 362⤵
- Program crash
PID:2520
-