Analysis
-
max time kernel
118s -
max time network
126s -
platform
windows7_x64 -
resource
win7-20231129-en -
resource tags
arch:x64arch:x86image:win7-20231129-enlocale:en-usos:windows7-x64system -
submitted
08-06-2024 18:57
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-06-08_3f75009c4afb68ae73ea415622da32cc_virlock.exe
Resource
win7-20231129-en
windows7-x64
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-06-08_3f75009c4afb68ae73ea415622da32cc_virlock.exe
Resource
win10v2004-20240508-en
windows10-2004-x64
1 signatures
150 seconds
General
-
Target
2024-06-08_3f75009c4afb68ae73ea415622da32cc_virlock.exe
-
Size
194KB
-
MD5
3f75009c4afb68ae73ea415622da32cc
-
SHA1
97edc1e20edef440f148a865e5405cdd6b2097ba
-
SHA256
58e37628aa7f383394ce6050bfe43814534ea22bca72cdb3072276ed352ba092
-
SHA512
83c6a2c361c13f5ca0d2e6a81b50bdafcccda065919cba070f28b51522f475a744c92bd7afab68fabb0f223c273121bdb25ce20f125aa0f65ddc3a6bbf6b35f8
-
SSDEEP
3072:nvu6whxCKLvkC0gAXbuVNHyOihpBFBohPzuke:vLwhxCKLvigAX0HyrhxBotzuk
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2972 2548 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2548 wrote to memory of 2972 2548 2024-06-08_3f75009c4afb68ae73ea415622da32cc_virlock.exe 28 PID 2548 wrote to memory of 2972 2548 2024-06-08_3f75009c4afb68ae73ea415622da32cc_virlock.exe 28 PID 2548 wrote to memory of 2972 2548 2024-06-08_3f75009c4afb68ae73ea415622da32cc_virlock.exe 28 PID 2548 wrote to memory of 2972 2548 2024-06-08_3f75009c4afb68ae73ea415622da32cc_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-06-08_3f75009c4afb68ae73ea415622da32cc_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-06-08_3f75009c4afb68ae73ea415622da32cc_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2548 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2548 -s 362⤵
- Program crash
PID:2972
-