Analysis
-
max time kernel
148s -
max time network
149s -
platform
windows10-2004_x64 -
resource
win10v2004-20240226-en -
resource tags
arch:x64arch:x86image:win10v2004-20240226-enlocale:en-usos:windows10-2004-x64system -
submitted
10-04-2024 11:00
Static task
static1
Behavioral task
behavioral1
Sample
545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe
Resource
win7-20240220-en
windows7-x64
8 signatures
150 seconds
Behavioral task
behavioral2
Sample
545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe
Resource
win10v2004-20240226-en
windows10-2004-x64
6 signatures
150 seconds
General
-
Target
545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe
-
Size
183KB
-
MD5
ead29687b7c4e76c59269e76a85341b7
-
SHA1
e4358328f8547d837e42fe5f9a516cba1b00c2ee
-
SHA256
545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0
-
SHA512
ba57dbb371e40f792f9e69d37bb54a74858890de72e4a5e01ccfb1f83053cb15e71de5fa25c8df748e299247ab34a3aed97acbc6153c01de7f5f348e5f043b5c
-
SSDEEP
3072:2PDMqqDLy/QmY2hDO1woouAq1cBGpH+H97k0n3i/Us3mPrONNKTdZdvj:ZqqDLuxv8VzA6cO23GUsWUNSn
Score
7/10
Malware Config
Signatures
-
Drops startup file 1 IoCs
description ioc Process File created C:\Users\Admin\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Startup\vinek.lnk 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s).
-
Program crash 1 IoCs
pid pid_target Process procid_target 3376 4196 WerFault.exe 97 -
Suspicious behavior: EnumeratesProcesses 8 IoCs
pid Process 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe -
Suspicious behavior: RenamesItself 1 IoCs
pid Process 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97 PID 5068 wrote to memory of 4196 5068 545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe 97
Processes
-
C:\Users\Admin\AppData\Local\Temp\545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe"C:\Users\Admin\AppData\Local\Temp\545031fa5e8492908a4e9b61fdd6516e1ff4de7d7cbcf8d4a8347dfd8de466b0.exe"1⤵
- Drops startup file
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: RenamesItself
- Suspicious use of WriteProcessMemory
PID:5068 -
C:\Windows\SysWOW64\explorer.exeexplorer.exe2⤵PID:4196
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4196 -s 123⤵
- Program crash
PID:3376
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 420 -p 4196 -ip 41961⤵PID:3928