Analysis
-
max time kernel
121s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20231215-en -
resource tags
arch:x64arch:x86image:win7-20231215-enlocale:en-usos:windows7-x64system -
submitted
25-12-2023 04:25
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
050b9d3a56e7344f36b7e2a29e1ed90b.exe
Resource
win7-20231215-en
windows7-x64
3 signatures
150 seconds
Behavioral task
behavioral2
Sample
050b9d3a56e7344f36b7e2a29e1ed90b.exe
Resource
win10v2004-20231222-en
windows10-2004-x64
2 signatures
150 seconds
General
-
Target
050b9d3a56e7344f36b7e2a29e1ed90b.exe
-
Size
56KB
-
MD5
050b9d3a56e7344f36b7e2a29e1ed90b
-
SHA1
836b7e2f63157d8dbc559e92d22610089e7f62ca
-
SHA256
a5cce370b907e2409b484a99c0a3799346c7b10cbe3cbcfaf12ca71a33a439e3
-
SHA512
230f8b6abd28287c0e00ebde92b3807636978a9f1f903ecfc32c930e0edeb3cbfc765f538b9fb0c18707be87504e5a02f8863d0367552fd8a389572d629ff8b4
-
SSDEEP
1536:pKKQNO/kkpCfkn/7lg8LsvtjDbf8WcbXd:pu4skpCfS/7lZL6jDY5B
Score
3/10
Malware Config
Signatures
-
Program crash 1 IoCs
pid pid_target Process procid_target 2036 1668 WerFault.exe 16 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 1668 050b9d3a56e7344f36b7e2a29e1ed90b.exe -
Suspicious use of WriteProcessMemory 4 IoCs
description pid Process procid_target PID 1668 wrote to memory of 2036 1668 050b9d3a56e7344f36b7e2a29e1ed90b.exe 28 PID 1668 wrote to memory of 2036 1668 050b9d3a56e7344f36b7e2a29e1ed90b.exe 28 PID 1668 wrote to memory of 2036 1668 050b9d3a56e7344f36b7e2a29e1ed90b.exe 28 PID 1668 wrote to memory of 2036 1668 050b9d3a56e7344f36b7e2a29e1ed90b.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\050b9d3a56e7344f36b7e2a29e1ed90b.exe"C:\Users\Admin\AppData\Local\Temp\050b9d3a56e7344f36b7e2a29e1ed90b.exe"1⤵
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1668 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1668 -s 1882⤵
- Program crash
PID:2036
-