Analysis
-
max time kernel
122s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
01/06/2024, 20:07
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-06-01_8ab9a157e6ff6d563889e52cb56048bf_virlock.exe
Resource
win7-20240221-en
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-06-01_8ab9a157e6ff6d563889e52cb56048bf_virlock.exe
Resource
win10v2004-20240226-en
1 signatures
150 seconds
General
-
Target
2024-06-01_8ab9a157e6ff6d563889e52cb56048bf_virlock.exe
-
Size
110KB
-
MD5
8ab9a157e6ff6d563889e52cb56048bf
-
SHA1
dc33539bcb4cbf1fa02df1712446d4695470820d
-
SHA256
534c3694ee65a38ff4a810f004624df24d321016bd33f06ae8e789332d9fcc47
-
SHA512
02c6e50ee99e0a83b33168537512a6f6403ae9a4921224611629133490a9687a755b223649bfaf0b237a3c67574a40a3b6807c550281ef3563c7d9022419df80
-
SSDEEP
3072:Rgp7hOhl6wrjkz8GwelBOsHgcnOcjN8KnAiSDLS:R2Ohl6wvkhZBvgcOcBNA
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2008 2972 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2972 wrote to memory of 2008 2972 2024-06-01_8ab9a157e6ff6d563889e52cb56048bf_virlock.exe 28 PID 2972 wrote to memory of 2008 2972 2024-06-01_8ab9a157e6ff6d563889e52cb56048bf_virlock.exe 28 PID 2972 wrote to memory of 2008 2972 2024-06-01_8ab9a157e6ff6d563889e52cb56048bf_virlock.exe 28 PID 2972 wrote to memory of 2008 2972 2024-06-01_8ab9a157e6ff6d563889e52cb56048bf_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-06-01_8ab9a157e6ff6d563889e52cb56048bf_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-06-01_8ab9a157e6ff6d563889e52cb56048bf_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2972 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2972 -s 362⤵
- Program crash
PID:2008
-