Analysis
-
max time kernel
127s -
max time network
130s -
platform
windows10-1703_x64 -
resource
win10-20230915-en -
resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system -
submitted
23-09-2023 08:15
Static task
static1
General
-
Target
e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe
-
Size
365KB
-
MD5
7c99117bfdb06ea7835833655b40f9f3
-
SHA1
4309c9f4b23075de9c388cd101e1fc0393998b67
-
SHA256
e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38
-
SHA512
3c73a383fef1c72c170b82eb1a382a3a3190066f5810a97dabacbbbc660a71d52144b0ee0f9c9805496b5d1d1e05b0605d024432a8b84002a8cf99bbf09cbe20
-
SSDEEP
6144:qz5frpxdonyq4zaG2u5AOXeKp17/kiuQReL8RzQEk3TIpUquqp:qNrp0/9u51eodu2UQk3T9quqp
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 3112 set thread context of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 -
Program crash 1 IoCs
pid pid_target Process procid_target 4152 3112 WerFault.exe 69 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 3112 wrote to memory of 2592 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 70 PID 3112 wrote to memory of 2592 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 70 PID 3112 wrote to memory of 2592 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 70 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71 PID 3112 wrote to memory of 1208 3112 e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe 71
Processes
-
C:\Users\Admin\AppData\Local\Temp\e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe"C:\Users\Admin\AppData\Local\Temp\e527d7cd7e96ef5625b0b05f6ac600cbed0b101ba28a2250655037a966e5ca38.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:3112 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2592
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1208
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3112 -s 2482⤵
- Program crash
PID:4152
-