Analysis
-
max time kernel
128s -
max time network
133s -
platform
windows10-1703_x64 -
resource
win10-20230915-en -
resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system -
submitted
19-09-2023 12:39
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe
Resource
win10-20230915-en
windows10-1703-x64
3 signatures
150 seconds
General
-
Target
995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe
-
Size
395KB
-
MD5
02fef18404d5c0478db4d6f214693a6a
-
SHA1
41cc85f6d4c75bcfa0d189c1469447425b461ca6
-
SHA256
995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7
-
SHA512
21dec4e48fefb70d4a1a5bebcf6da26e6e00939c8efc4d9d324898d3e86525aafd8073b837a44ffaa0382271017215f2c80ff261862f1914ad846a30181faf50
-
SSDEEP
6144:8syTmInU3SPmZbHh3Y/feAOT4uepvJWoO3mrumdQc7MR/1+t/KfYyUi9:8saU3SPJ/2xepfBru4Q5R/1+diYyUi
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2300 set thread context of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 -
Program crash 1 IoCs
pid pid_target Process procid_target 984 2300 WerFault.exe 69 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71 PID 2300 wrote to memory of 2692 2300 995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe 71
Processes
-
C:\Users\Admin\AppData\Local\Temp\995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe"C:\Users\Admin\AppData\Local\Temp\995af841b80b71478d524932e24a8ec7c95f84deb807ab461e1f58c4dc75ebe7.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2300 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2692
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2300 -s 1402⤵
- Program crash
PID:984
-