Analysis
-
max time kernel
122s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20240508-en -
resource tags
arch:x64arch:x86image:win7-20240508-enlocale:en-usos:windows7-x64system -
submitted
16/06/2024, 14:21
Static task
static1
Behavioral task
behavioral1
Sample
1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320.exe
Resource
win7-20240508-en
Behavioral task
behavioral2
Sample
1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320.exe
Resource
win10v2004-20240508-en
General
-
Target
1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320.exe
-
Size
3.2MB
-
MD5
39cc7b8e46e444970db3924b3ff5050b
-
SHA1
745de332f6fbe8fc7b9d3ec9a9d3243d442e28b4
-
SHA256
1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320
-
SHA512
40d07e6d74eff4f8f738d4adbe6734bd4fadb00ed1dd6762304ff30e673d0348db4fe0c2378d155e4760231f03a6d857c5de9aa3766a5c1b6a2fbe01ffab627c
-
SSDEEP
98304:FqcHd9dChDBdG26666666666666666666666666666666x666666666666666fw6:FqcHZChfGcwMmlqH
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2084 2052 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 2052 wrote to memory of 2084 2052 1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320.exe 28 PID 2052 wrote to memory of 2084 2052 1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320.exe 28 PID 2052 wrote to memory of 2084 2052 1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320.exe 28 PID 2052 wrote to memory of 2084 2052 1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320.exe"C:\Users\Admin\AppData\Local\Temp\1c030d52c901e98fa8636c4fbcb5d70527576165ef3d9e64cff06bae8b08f320.exe"1⤵
- Suspicious use of WriteProcessMemory
PID:2052 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2052 -s 1842⤵
- Program crash
PID:2084
-