Analysis
-
max time kernel
117s -
max time network
138s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
13-10-2023 01:36
Static task
static1
Behavioral task
behavioral1
Sample
c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe
Resource
win10v2004-20230915-en
General
-
Target
c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe
-
Size
1.4MB
-
MD5
a48a91f54de1bb6bf5d3818bbed03835
-
SHA1
388c9cb332166028709212d452264a3b3e7b3e21
-
SHA256
c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff
-
SHA512
05f522e878c90cd35d0c2761ad068e37f167122326908d7b3f3519377a26c24a3cce5160246fa82d0f8c5bc791aa2fa72f381b47e60e1d653496aca5033ad027
-
SSDEEP
24576:UZtAcY5bzEJjKmQM8TxjXFwJ3YO1VUOO1t6xqd+LL042Zigg2LSOEbhZ:UZtAcY5bzEJjKmQ3xjVMmOMUqd+042h4
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2416 set thread context of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 -
Program crash 1 IoCs
pid pid_target Process procid_target 1652 2592 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2416 wrote to memory of 2592 2416 c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe 29 PID 2592 wrote to memory of 1652 2592 AppLaunch.exe 30 PID 2592 wrote to memory of 1652 2592 AppLaunch.exe 30 PID 2592 wrote to memory of 1652 2592 AppLaunch.exe 30 PID 2592 wrote to memory of 1652 2592 AppLaunch.exe 30 PID 2592 wrote to memory of 1652 2592 AppLaunch.exe 30 PID 2592 wrote to memory of 1652 2592 AppLaunch.exe 30 PID 2592 wrote to memory of 1652 2592 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe"C:\Users\Admin\AppData\Local\Temp\c41f68cb4927a4050751e023ec4a7f3d927f30dbb23fe81394be7c855694d8ff.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2416 -
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:2592 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2592 -s 2003⤵
- Program crash
PID:1652
-
-