Analysis
-
max time kernel
44s -
max time network
22s -
platform
windows10-2004_x64 -
resource
win10v2004-20220812-en -
resource tags
arch:x64arch:x86image:win10v2004-20220812-enlocale:en-usos:windows10-2004-x64system -
submitted
28-10-2022 21:57
Behavioral task
behavioral1
Sample
e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe
Resource
win7-20220812-en
windows7-x64
5 signatures
150 seconds
Behavioral task
behavioral2
Sample
e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe
Resource
win10v2004-20220812-en
windows10-2004-x64
5 signatures
150 seconds
General
-
Target
e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe
-
Size
240KB
-
MD5
0abe74ad896f43d5a5872506c63bf81f
-
SHA1
6bd0301981b42f509ca40f7aa341227e1f389902
-
SHA256
e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744
-
SHA512
89bbaa565a05a94b18959cbb6de4b3b160ef2cda280715dd5ffaab3e147e4e0e096dab5d487f9f868b764ccfde782a5c23efd8a5d15b0bcf5d25d32fdac4de1f
-
SSDEEP
6144:0RL7V/sBI2xqlMutSbkCpguZuqThPcV4JDkKIDeHg1CgpmE8eP:0RLR/sBI2xqlabkCgukqFPcVgAtSHg1D
Score
8/10
Malware Config
Signatures
-
resource yara_rule behavioral2/memory/5012-132-0x0000000000400000-0x0000000000451000-memory.dmp upx behavioral2/memory/5012-135-0x0000000000400000-0x0000000000451000-memory.dmp upx -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5012 set thread context of 4916 5012 e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe 84 -
Program crash 1 IoCs
pid pid_target Process procid_target 1304 4916 WerFault.exe 84 -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 4916 e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe -
Suspicious use of WriteProcessMemory 7 IoCs
description pid Process procid_target PID 5012 wrote to memory of 4916 5012 e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe 84 PID 5012 wrote to memory of 4916 5012 e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe 84 PID 5012 wrote to memory of 4916 5012 e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe 84 PID 5012 wrote to memory of 4916 5012 e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe 84 PID 5012 wrote to memory of 4916 5012 e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe 84 PID 5012 wrote to memory of 4916 5012 e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe 84 PID 5012 wrote to memory of 4916 5012 e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe 84
Processes
-
C:\Users\Admin\AppData\Local\Temp\e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe"C:\Users\Admin\AppData\Local\Temp\e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:5012 -
C:\Users\Admin\AppData\Local\Temp\e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exeC:\Users\Admin\AppData\Local\Temp\e158c4a3c9a4ab5b71890a431a7ff9af52c047fe6183f2873690666cf487c744.exe2⤵
- Suspicious use of SetWindowsHookEx
PID:4916 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4916 -s 6163⤵
- Program crash
PID:1304
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -pss -s 428 -p 4916 -ip 49161⤵PID:4024