Analysis
-
max time kernel
120s -
max time network
125s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
11/10/2023, 22:36
Static task
static1
Behavioral task
behavioral1
Sample
aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe
-
Size
396KB
-
MD5
a973e7669ca3c09f52bf0bfaf650691c
-
SHA1
39c193f1073245037919a743714bca458f6837cc
-
SHA256
aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965
-
SHA512
ec28a63767b66ff677738950a137e90ddaac88552fe4c7f886c683c343fa6b34e8b5441b69ea16becf6f3096f7a88473393765038fd666b1d5914603876cace6
-
SSDEEP
6144:DNNhUOqW5XJ6EDOpvOCm5MNuAOqnbLuNRtuUj71fI34usooVxB5iE8qwh:DNjdqW5sEe2uuocPSIfJd9wh
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1932 set thread context of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2896 1932 WerFault.exe 27 2956 2168 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 32 IoCs
description pid Process procid_target PID 1932 wrote to memory of 1628 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 28 PID 1932 wrote to memory of 1628 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 28 PID 1932 wrote to memory of 1628 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 28 PID 1932 wrote to memory of 1628 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 28 PID 1932 wrote to memory of 1628 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 28 PID 1932 wrote to memory of 1628 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 28 PID 1932 wrote to memory of 1628 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 28 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2168 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 29 PID 1932 wrote to memory of 2896 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 30 PID 1932 wrote to memory of 2896 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 30 PID 1932 wrote to memory of 2896 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 30 PID 1932 wrote to memory of 2896 1932 aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe 30 PID 2168 wrote to memory of 2956 2168 AppLaunch.exe 31 PID 2168 wrote to memory of 2956 2168 AppLaunch.exe 31 PID 2168 wrote to memory of 2956 2168 AppLaunch.exe 31 PID 2168 wrote to memory of 2956 2168 AppLaunch.exe 31 PID 2168 wrote to memory of 2956 2168 AppLaunch.exe 31 PID 2168 wrote to memory of 2956 2168 AppLaunch.exe 31 PID 2168 wrote to memory of 2956 2168 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe"C:\Users\Admin\AppData\Local\Temp\aa12af85ad68c4227847b7e666b949174a3d552ca90ed4bc150e57a8d2de8965.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1932 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:1628
-
-
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:2168 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2168 -s 1963⤵
- Program crash
PID:2956
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1932 -s 602⤵
- Program crash
PID:2896
-