Analysis
-
max time kernel
118s -
max time network
132s -
platform
windows7_x64 -
resource
win7-20231215-en -
resource tags
arch:x64arch:x86image:win7-20231215-enlocale:en-usos:windows7-x64system -
submitted
09/01/2024, 06:47
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-01-08_bfbe024bd0c1ee641c6828b91570572f_virlock.exe
Resource
win7-20231215-en
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-01-08_bfbe024bd0c1ee641c6828b91570572f_virlock.exe
Resource
win10v2004-20231215-en
1 signatures
150 seconds
General
-
Target
2024-01-08_bfbe024bd0c1ee641c6828b91570572f_virlock.exe
-
Size
110KB
-
MD5
bfbe024bd0c1ee641c6828b91570572f
-
SHA1
ef0e8b910bc1b031dc4a0ea4e58ea78577886a24
-
SHA256
2f0615e0d21be5027ead34510c2e6ed6aabe23cd0ed3f8361f0a876b38a2faaa
-
SHA512
7ac98a1515a300f6be4873ee804a7e36851f876e45fc4ddd8b00535260d569b2768280dbc0fa8ca8c2197a63d537a2be69eb2a5c66000504f541a69a9155d49e
-
SSDEEP
3072:EenNJJcC1KsHwpIj89DzaOADp4KFx0qJyg:fNJJVZHAj9aFD7bW
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2516 2180 WerFault.exe 16 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2180 wrote to memory of 2516 2180 2024-01-08_bfbe024bd0c1ee641c6828b91570572f_virlock.exe 17 PID 2180 wrote to memory of 2516 2180 2024-01-08_bfbe024bd0c1ee641c6828b91570572f_virlock.exe 17 PID 2180 wrote to memory of 2516 2180 2024-01-08_bfbe024bd0c1ee641c6828b91570572f_virlock.exe 17 PID 2180 wrote to memory of 2516 2180 2024-01-08_bfbe024bd0c1ee641c6828b91570572f_virlock.exe 17
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-01-08_bfbe024bd0c1ee641c6828b91570572f_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-01-08_bfbe024bd0c1ee641c6828b91570572f_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2180 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2180 -s 362⤵
- Program crash
PID:2516
-