Analysis
-
max time kernel
122s -
max time network
126s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
26-03-2024 03:35
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-03-26_3bbb3f17304b26e17617ad10ff5560b5_virlock.exe
Resource
win7-20240221-en
windows7-x64
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-03-26_3bbb3f17304b26e17617ad10ff5560b5_virlock.exe
Resource
win10v2004-20240226-en
windows10-2004-x64
1 signatures
150 seconds
General
-
Target
2024-03-26_3bbb3f17304b26e17617ad10ff5560b5_virlock.exe
-
Size
108KB
-
MD5
3bbb3f17304b26e17617ad10ff5560b5
-
SHA1
9a049769e4223827937ca43f4cf6e9a8eeaf7e76
-
SHA256
27e414de6ff5443b0f464dbc179ee45e3ab5a942fc3788c642494d71a2d10714
-
SHA512
64c3a7a9b3ee37e7ff05b7f356bd6155da20ea600d52fc75fe4f2e10d969f4fadfeae6664f19e3166bbc2d0b86f8110b26c00145da5154801bab95bea3fb2957
-
SSDEEP
3072:srM5AsjCICPifFcGfbq8zxKlcAKthROmoD64l:sYcIrdlfbq8zx5AKthwD6
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 1940 2492 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2492 wrote to memory of 1940 2492 2024-03-26_3bbb3f17304b26e17617ad10ff5560b5_virlock.exe 28 PID 2492 wrote to memory of 1940 2492 2024-03-26_3bbb3f17304b26e17617ad10ff5560b5_virlock.exe 28 PID 2492 wrote to memory of 1940 2492 2024-03-26_3bbb3f17304b26e17617ad10ff5560b5_virlock.exe 28 PID 2492 wrote to memory of 1940 2492 2024-03-26_3bbb3f17304b26e17617ad10ff5560b5_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-03-26_3bbb3f17304b26e17617ad10ff5560b5_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-03-26_3bbb3f17304b26e17617ad10ff5560b5_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2492 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2492 -s 362⤵
- Program crash
PID:1940
-