Analysis
-
max time kernel
127s -
max time network
135s -
platform
windows10-1703_x64 -
resource
win10-20230915-en -
resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system -
submitted
01-10-2023 07:54
Static task
static1
1 signatures
General
-
Target
d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe
-
Size
276KB
-
MD5
5d4a3806483a12cc529d1a33dd559610
-
SHA1
3d80f7d747876fdbba259971f86af6d2ea80fcad
-
SHA256
d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642
-
SHA512
ce6d0d2fa6e6ea9a90f99c42e35f750feb51aded74979d0624b15cd0f1a2d963414de0663a6140ca168ecbdadc283cf656b10ad572cac2834d4bf8d213def4bb
-
SSDEEP
6144:WhNhKajWpVP06GVTFA+Cbstz53dQi559+nueVp8Crj:WZKajW+TFA+CbstnJeVp8Ej
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5020 set thread context of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 -
Program crash 1 IoCs
pid pid_target Process procid_target 4852 5020 WerFault.exe 68 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70 PID 5020 wrote to memory of 4864 5020 d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe 70
Processes
-
C:\Users\Admin\AppData\Local\Temp\d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe"C:\Users\Admin\AppData\Local\Temp\d1e379e765a00b07691f4377360c84293962ed15461a31e9d918bff6b671c642.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5020 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4864
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 5020 -s 1482⤵
- Program crash
PID:4852
-