Analysis
-
max time kernel
122s -
max time network
128s -
platform
windows7_x64 -
resource
win7-20231023-en -
resource tags
arch:x64arch:x86image:win7-20231023-enlocale:en-usos:windows7-x64system -
submitted
30/10/2023, 03:47
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe
Resource
win7-20231023-en
3 signatures
300 seconds
Behavioral task
behavioral2
Sample
e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe
Resource
win10-20231020-en
3 signatures
300 seconds
General
-
Target
e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe
-
Size
1.1MB
-
MD5
ad5f3ea46f25bd70cc72ec0bfbf27734
-
SHA1
ba254d6e172a3a93ba0fda90747919e19fec8afb
-
SHA256
e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964
-
SHA512
041c82add9294dbedf3f6b6a14ea0e4a8d0e9f472077d665716a176514eb2a17687717c7c6f4bf16be7bab0840579a2ddd47119138bcbca515ef2d3e031e88bb
-
SSDEEP
24576:+Sh+1HWdgAw/26p6XytGbSaOcKtBkemTI9:+sbw/26p6ira+81T
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2920 set thread context of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 -
Program crash 2 IoCs
pid pid_target Process procid_target 2896 2920 WerFault.exe 27 2916 3024 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 3024 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 28 PID 2920 wrote to memory of 2896 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 29 PID 2920 wrote to memory of 2896 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 29 PID 2920 wrote to memory of 2896 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 29 PID 2920 wrote to memory of 2896 2920 e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe 29 PID 3024 wrote to memory of 2916 3024 AppLaunch.exe 30 PID 3024 wrote to memory of 2916 3024 AppLaunch.exe 30 PID 3024 wrote to memory of 2916 3024 AppLaunch.exe 30 PID 3024 wrote to memory of 2916 3024 AppLaunch.exe 30 PID 3024 wrote to memory of 2916 3024 AppLaunch.exe 30 PID 3024 wrote to memory of 2916 3024 AppLaunch.exe 30 PID 3024 wrote to memory of 2916 3024 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe"C:\Users\Admin\AppData\Local\Temp\e02bf299f5c2bbd3f18477016d7cc08465cab046518851f521cb5844f89f0964.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2920 -
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:3024 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 3024 -s 1963⤵
- Program crash
PID:2916
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2920 -s 922⤵
- Program crash
PID:2896
-