Analysis
-
max time kernel
117s -
max time network
121s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12/10/2023, 00:22
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe
Resource
win7-20230831-en
3 signatures
150 seconds
General
-
Target
8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe
-
Size
364KB
-
MD5
36c4eaac755d927f09b9fc807f463dc4
-
SHA1
accd7b2bed923aaeb5999cf16084b2323e5e8a15
-
SHA256
8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce
-
SHA512
c434c372f766305a2ff97dd86cf37e1ef61c73c975ec1ca4caafb0979ebf4d16bf7f5ce8db69a0bb731c0a0adc7ba1bc1c52ec0fade5fe4171d233099e3a95d6
-
SSDEEP
6144:pK46fuYXChoQTjlFgLuCY1dRuAO5LQRNHrWb2UynYghxLsXG2aN1hw8y0:pvYzXChdTbv1buoDLo2pDhx4XNaN1hwX
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2436 set thread context of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 -
Program crash 2 IoCs
pid pid_target Process procid_target 3020 2436 WerFault.exe 27 2304 1680 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 1680 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 28 PID 2436 wrote to memory of 3020 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 29 PID 2436 wrote to memory of 3020 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 29 PID 2436 wrote to memory of 3020 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 29 PID 2436 wrote to memory of 3020 2436 8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe 29 PID 1680 wrote to memory of 2304 1680 AppLaunch.exe 30 PID 1680 wrote to memory of 2304 1680 AppLaunch.exe 30 PID 1680 wrote to memory of 2304 1680 AppLaunch.exe 30 PID 1680 wrote to memory of 2304 1680 AppLaunch.exe 30 PID 1680 wrote to memory of 2304 1680 AppLaunch.exe 30 PID 1680 wrote to memory of 2304 1680 AppLaunch.exe 30 PID 1680 wrote to memory of 2304 1680 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe"C:\Users\Admin\AppData\Local\Temp\8011e74693b5d8a2a1488ef32f1586afd922a91c965142b3ceee8ba9455a64ce.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2436 -
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:1680 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1680 -s 1963⤵
- Program crash
PID:2304
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2436 -s 522⤵
- Program crash
PID:3020
-