Analysis
-
max time kernel
121s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20240220-en -
resource tags
arch:x64arch:x86image:win7-20240220-enlocale:en-usos:windows7-x64system -
submitted
09-03-2024 08:03
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-03-09_2b5bd870a754e4f9aa7f01a8278147b2_virlock.exe
Resource
win7-20240220-en
windows7-x64
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-03-09_2b5bd870a754e4f9aa7f01a8278147b2_virlock.exe
Resource
win10v2004-20240226-en
windows10-2004-x64
1 signatures
150 seconds
General
-
Target
2024-03-09_2b5bd870a754e4f9aa7f01a8278147b2_virlock.exe
-
Size
109KB
-
MD5
2b5bd870a754e4f9aa7f01a8278147b2
-
SHA1
ec175fd43edb5b0451ab9bf9a92aa6e7eb047fa9
-
SHA256
0519df9f3aaca5d100e7d4f237fb6bc168f9df9ea839a43b3a177367392c789b
-
SHA512
e410f9e30813fad52a2c10d5e3ccb198cdc08429a4eb53813fba8405055bd35a5ff53a3bc3ec17b4f03c3cd2409642eeac815c7a9dd0e094cf431ba59d2bec6e
-
SSDEEP
3072:6fYbRRSP0hjE2pMpeQxvFV18OyvPLU7mK:gC0cgQiNQOUIv
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2228 3028 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 3028 wrote to memory of 2228 3028 2024-03-09_2b5bd870a754e4f9aa7f01a8278147b2_virlock.exe 28 PID 3028 wrote to memory of 2228 3028 2024-03-09_2b5bd870a754e4f9aa7f01a8278147b2_virlock.exe 28 PID 3028 wrote to memory of 2228 3028 2024-03-09_2b5bd870a754e4f9aa7f01a8278147b2_virlock.exe 28 PID 3028 wrote to memory of 2228 3028 2024-03-09_2b5bd870a754e4f9aa7f01a8278147b2_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-03-09_2b5bd870a754e4f9aa7f01a8278147b2_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-03-09_2b5bd870a754e4f9aa7f01a8278147b2_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:3028 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3028 -s 362⤵
- Program crash
PID:2228
-