Analysis
-
max time kernel
118s -
max time network
118s -
platform
windows7_x64 -
resource
win7-20231129-en -
resource tags
arch:x64arch:x86image:win7-20231129-enlocale:en-usos:windows7-x64system -
submitted
24/05/2024, 16:04
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-05-24_8f4c721fb2eabbeee82780431462aae4_virlock.exe
Resource
win7-20231129-en
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-05-24_8f4c721fb2eabbeee82780431462aae4_virlock.exe
Resource
win10v2004-20240426-en
1 signatures
150 seconds
General
-
Target
2024-05-24_8f4c721fb2eabbeee82780431462aae4_virlock.exe
-
Size
190KB
-
MD5
8f4c721fb2eabbeee82780431462aae4
-
SHA1
a14bc6396226879f39cb618048bfcd66b9a44eae
-
SHA256
10abc04ef7c4ee5ef7eac278598c44059579a7caaaca87759bd9e68ccb48ac34
-
SHA512
858a65434c0b9747285a349696def48803a8b6e71a62631f4726e026a7dcbd14b273b38fd9607824d9fc270fcff6cccfa0de03b68e876d936ee4eabe4ac4caa7
-
SSDEEP
3072:sHR9zSQ2R19PHl6UZ0MZMPP2RpVjOZVluk9a7H5KPcdGdwP6n52j:qKL3PFKMZM2R3jORuk9U5CcdGWins
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2992 624 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 624 wrote to memory of 2992 624 2024-05-24_8f4c721fb2eabbeee82780431462aae4_virlock.exe 28 PID 624 wrote to memory of 2992 624 2024-05-24_8f4c721fb2eabbeee82780431462aae4_virlock.exe 28 PID 624 wrote to memory of 2992 624 2024-05-24_8f4c721fb2eabbeee82780431462aae4_virlock.exe 28 PID 624 wrote to memory of 2992 624 2024-05-24_8f4c721fb2eabbeee82780431462aae4_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-05-24_8f4c721fb2eabbeee82780431462aae4_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-05-24_8f4c721fb2eabbeee82780431462aae4_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:624 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 624 -s 362⤵
- Program crash
PID:2992
-