Analysis
-
max time kernel
120s -
max time network
127s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
28-03-2024 11:31
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-03-28_2702acd4e4bae8418378fe0a190763eb_virlock.exe
Resource
win7-20240221-en
windows7-x64
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-03-28_2702acd4e4bae8418378fe0a190763eb_virlock.exe
Resource
win10v2004-20240226-en
windows10-2004-x64
1 signatures
150 seconds
General
-
Target
2024-03-28_2702acd4e4bae8418378fe0a190763eb_virlock.exe
-
Size
180KB
-
MD5
2702acd4e4bae8418378fe0a190763eb
-
SHA1
85322b2e4fadaec7922dffc4497fc399b55f407f
-
SHA256
9955fe015c58a242c7bd471796dd3d1119daf8f77738406e25a74d568c2b2343
-
SHA512
b574714395e002ba84e37d83b4c951ba889c5a01deb1b8a504eb5d3d4e8173b02937d1899d6d4a64dcf72c973efc717ca6eaf2daa99afc81830575b8176d53bc
-
SSDEEP
3072:if0J8lowzCWJViM40d0/KiOgYg6zlmXnRM1nry5FC:i2jXaVPCSiOgSxmXRM1nO
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2036 2360 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2360 wrote to memory of 2036 2360 2024-03-28_2702acd4e4bae8418378fe0a190763eb_virlock.exe 28 PID 2360 wrote to memory of 2036 2360 2024-03-28_2702acd4e4bae8418378fe0a190763eb_virlock.exe 28 PID 2360 wrote to memory of 2036 2360 2024-03-28_2702acd4e4bae8418378fe0a190763eb_virlock.exe 28 PID 2360 wrote to memory of 2036 2360 2024-03-28_2702acd4e4bae8418378fe0a190763eb_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-03-28_2702acd4e4bae8418378fe0a190763eb_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-03-28_2702acd4e4bae8418378fe0a190763eb_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2360 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2360 -s 362⤵
- Program crash
PID:2036
-