Analysis
-
max time kernel
121s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20240221-en -
resource tags
arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system -
submitted
30-04-2024 11:37
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
2024-04-30_ce6b40568637fe08bd3b109d80e3c960_virlock.exe
Resource
win7-20240221-en
windows7-x64
2 signatures
150 seconds
Behavioral task
behavioral2
Sample
2024-04-30_ce6b40568637fe08bd3b109d80e3c960_virlock.exe
Resource
win10v2004-20240419-en
windows10-2004-x64
1 signatures
150 seconds
General
-
Target
2024-04-30_ce6b40568637fe08bd3b109d80e3c960_virlock.exe
-
Size
109KB
-
MD5
ce6b40568637fe08bd3b109d80e3c960
-
SHA1
7af25ad8d9f723d56025a834dd6706bca5190e6f
-
SHA256
850f7566cebb364b3e8a555fbf5fbab3626a4991e0fdd319c4f0815ead29f543
-
SHA512
1ce04f3c0c382dde4619ba0cc8f73e70e9e99107bcfed4aca9229d2c8294a421992c632aeb6765753846f0f298f370bd768e3fc175843e157f30c4f61f97725e
-
SSDEEP
1536:FoJ8e+szO8IoQ5JMVwLcuA0oD/er0K9jPYH96X79xPWhcdoHMi5Vj8GXfh+5xlTb:y+qIoCJGYuSrFdnTu98GXK
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2080 2240 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2240 wrote to memory of 2080 2240 2024-04-30_ce6b40568637fe08bd3b109d80e3c960_virlock.exe 28 PID 2240 wrote to memory of 2080 2240 2024-04-30_ce6b40568637fe08bd3b109d80e3c960_virlock.exe 28 PID 2240 wrote to memory of 2080 2240 2024-04-30_ce6b40568637fe08bd3b109d80e3c960_virlock.exe 28 PID 2240 wrote to memory of 2080 2240 2024-04-30_ce6b40568637fe08bd3b109d80e3c960_virlock.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\2024-04-30_ce6b40568637fe08bd3b109d80e3c960_virlock.exe"C:\Users\Admin\AppData\Local\Temp\2024-04-30_ce6b40568637fe08bd3b109d80e3c960_virlock.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2240 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2240 -s 362⤵
- Program crash
PID:2080
-