Analysis
-
max time kernel
120s -
max time network
120s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
08/03/2024, 10:58
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-03-08_c2b0a7b2202122128ba7ea98216bc7b4_virlock.exe
Resource
win7-20240221-en
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-03-08_c2b0a7b2202122128ba7ea98216bc7b4_virlock.exe
Resource
win10v2004-20240226-en
1 signatures
150 seconds
General
-
Target
2024-03-08_c2b0a7b2202122128ba7ea98216bc7b4_virlock.exe
-
Size
110KB
-
MD5
c2b0a7b2202122128ba7ea98216bc7b4
-
SHA1
bf9e5d4c51d3d3486d9bb7f48bbf798ec0d68863
-
SHA256
aede16124c56fe606904a6b89b50e4811f2101aba2ddb084a44715073c047b89
-
SHA512
1ccbb03a1a7d8432b23b8e52a221b9d96005bba444f71679bd6ed9d164595da2f527de1a91561457802c9bd28bc5bc36f40f2596634126fe2b70c02022dd0c75
-
SSDEEP
3072:cIfwz9SrTUzFooK1xISXrRAubjxfbd1jXbFWy49EP5:cIjrwSt1q4rR5blfjbS9U
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 1952 2924 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2924 wrote to memory of 1952 2924 2024-03-08_c2b0a7b2202122128ba7ea98216bc7b4_virlock.exe 28 PID 2924 wrote to memory of 1952 2924 2024-03-08_c2b0a7b2202122128ba7ea98216bc7b4_virlock.exe 28 PID 2924 wrote to memory of 1952 2924 2024-03-08_c2b0a7b2202122128ba7ea98216bc7b4_virlock.exe 28 PID 2924 wrote to memory of 1952 2924 2024-03-08_c2b0a7b2202122128ba7ea98216bc7b4_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-03-08_c2b0a7b2202122128ba7ea98216bc7b4_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-03-08_c2b0a7b2202122128ba7ea98216bc7b4_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2924 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2924 -s 362⤵
- Program crash
PID:1952
-