779d38078919bf534a3185cffb3121ac2af325c5fa4ede2fd0603300e1cbe034

Analysis

max time kernel
122s
max time network
137s
platform
windows7_x64
resource
win7-20240221-en
resource tags

arch:x64arch:x86image:win7-20240221-enlocale:en-usos:windows7-x64system
submitted
28-02-2024 21:25

Target

2024-02-28_2fb1ff25d12554c3c10dbd0a176e3f28_virlock.exe
Size

110KB
MD5

2fb1ff25d12554c3c10dbd0a176e3f28
SHA1

61c94fa94678ebb305bc5477f947aea5e6d7b55e
SHA256

779d38078919bf534a3185cffb3121ac2af325c5fa4ede2fd0603300e1cbe034
SHA512

f3bb1403a3ff60ee94761a515bbd3cd8bc84f5a382a8aea7553a289f572ad08d12de081082717789074b14da6fe76bba1f398702c7f7316848025cdb84280a56
SSDEEP

3072:Xd6O4LOEo56beRj6N3mzlRXQqCdgZ6eQmz1lldgBXAv:t3r6bWj1jzg5

Score

3^/10

Program crash 1 IoCs

pid	pid_target	Process	procid_target
2276	1352	WerFault.exe	27

Suspicious use of WriteProcessMemory 4 IoCs

description	pid	Process	procid_target
PID 1352 wrote to memory of 2276	1352	2024-02-28_2fb1ff25d12554c3c10dbd0a176e3f28_virlock.exe	28
PID 1352 wrote to memory of 2276	1352	2024-02-28_2fb1ff25d12554c3c10dbd0a176e3f28_virlock.exe	28
PID 1352 wrote to memory of 2276	1352	2024-02-28_2fb1ff25d12554c3c10dbd0a176e3f28_virlock.exe	28
PID 1352 wrote to memory of 2276	1352	2024-02-28_2fb1ff25d12554c3c10dbd0a176e3f28_virlock.exe	28

C:\Users\Admin\AppData\Local\Temp\2024-02-28_2fb1ff25d12554c3c10dbd0a176e3f28_virlock.exe
"C:\Users\Admin\AppData\Local\Temp\2024-02-28_2fb1ff25d12554c3c10dbd0a176e3f28_virlock.exe"
1⤵
- Suspicious use of WriteProcessMemory
PID:1352
- C:\Windows\SysWOW64\WerFault.exe
  C:\Windows\SysWOW64\WerFault.exe -u -p 1352 -s 36
  2⤵
  - Program crash
  PID:2276

memory/1352-0-0x0000000000400000-0x000000000041D000-memory.dmp

Filesize
116KB

Download