Analysis
-
max time kernel
121s -
max time network
131s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12/10/2023, 11:12
Static task
static1
Behavioral task
behavioral1
Sample
2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe
Resource
win10v2004-20230915-en
General
-
Target
2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe
-
Size
2.6MB
-
MD5
e5f03ee89948f6832598772214e69d29
-
SHA1
774fb006e8c5e7b9fc5b45c5c712186d1354fcd9
-
SHA256
2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b
-
SHA512
687419c9e6ff0cd6e622292b09d2493cc317ee06166ce7bd726159133a5fef91b1f7ad09f0f6aaaeb38c9c589435395d2633196a43ba16f4a7e56791f97de6e8
-
SSDEEP
49152:g99i4ytXaxgEAWU0BS4AodHlhm9dsSfY25k2ggCn8IVN:9I1U0jHa9dlYok20nn3
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2860 set thread context of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2604 2860 WerFault.exe 19 2824 2740 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2740 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 29 PID 2860 wrote to memory of 2604 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 31 PID 2860 wrote to memory of 2604 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 31 PID 2860 wrote to memory of 2604 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 31 PID 2860 wrote to memory of 2604 2860 2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe 31 PID 2740 wrote to memory of 2824 2740 AppLaunch.exe 32 PID 2740 wrote to memory of 2824 2740 AppLaunch.exe 32 PID 2740 wrote to memory of 2824 2740 AppLaunch.exe 32 PID 2740 wrote to memory of 2824 2740 AppLaunch.exe 32 PID 2740 wrote to memory of 2824 2740 AppLaunch.exe 32 PID 2740 wrote to memory of 2824 2740 AppLaunch.exe 32 PID 2740 wrote to memory of 2824 2740 AppLaunch.exe 32
Processes
-
C:\Users\Admin\AppData\Local\Temp\2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe"C:\Users\Admin\AppData\Local\Temp\2bd0c042c142e703a2da72f213e5d645ac908c38b5dee7e0a3bed547994b689b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2860 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵
- Suspicious use of WriteProcessMemory
PID:2740 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2740 -s 2003⤵
- Program crash
PID:2824
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2860 -s 922⤵
- Program crash
PID:2604
-