Analysis
-
max time kernel
117s -
max time network
118s -
platform
windows7_x64 -
resource
win7-20240220-en -
resource tags
arch:x64arch:x86image:win7-20240220-enlocale:en-usos:windows7-x64system -
submitted
20/05/2024, 18:57
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-05-20_b8b239de35c2226d8df91f75173f77cf_virlock.exe
Resource
win7-20240220-en
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-05-20_b8b239de35c2226d8df91f75173f77cf_virlock.exe
Resource
win10v2004-20240508-en
1 signatures
150 seconds
General
-
Target
2024-05-20_b8b239de35c2226d8df91f75173f77cf_virlock.exe
-
Size
200KB
-
MD5
b8b239de35c2226d8df91f75173f77cf
-
SHA1
d2d7590cda85dfbbdebd04ec61448bdc620f2a60
-
SHA256
2764affa0ed576823f3fdd76d3775440eb2232afb7053d82dad9fda4b9355efe
-
SHA512
0ff5f8187fa9856be48a48aab0ce800f2ac7088b1e8a1ad5e7dfaf32dcee9472d070a1d23c0e9d2cf05ad98787c7f4a6e67228ae62eed5186fa0163e8a135328
-
SSDEEP
6144:ECywRB/oYwC0qiNKd0gqW9tMV726gCkCj:ECyeBw7FRQtMN1
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2688 2836 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2836 wrote to memory of 2688 2836 2024-05-20_b8b239de35c2226d8df91f75173f77cf_virlock.exe 28 PID 2836 wrote to memory of 2688 2836 2024-05-20_b8b239de35c2226d8df91f75173f77cf_virlock.exe 28 PID 2836 wrote to memory of 2688 2836 2024-05-20_b8b239de35c2226d8df91f75173f77cf_virlock.exe 28 PID 2836 wrote to memory of 2688 2836 2024-05-20_b8b239de35c2226d8df91f75173f77cf_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-20_b8b239de35c2226d8df91f75173f77cf_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-20_b8b239de35c2226d8df91f75173f77cf_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2836 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2836 -s 362⤵
- Program crash
PID:2688
-