Analysis
-
max time kernel
118s -
max time network
122s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
12-10-2023 07:13
Static task
static1
Behavioral task
behavioral1
Sample
1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe
Resource
win7-20230831-en
windows7-x64
3 signatures
150 seconds
General
-
Target
1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe
-
Size
700KB
-
MD5
97a62ecc228570f1ac28416be27a66d3
-
SHA1
5b1421e88a8707affbd0b9c3ed11ff4635a39959
-
SHA256
1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448
-
SHA512
f7ca4691953540862b72037854c5e790f1132cf770f5aa674fbf6cd2a82ff47216fd61b6e0971a58fee641a7b621ead016fc0d8d8fda280476ab2a6e75102273
-
SSDEEP
6144:76vGALXgBEIy8wluzNcq/PVucQpHVzsPCvaeztC4HTByQ3xpvfr:2HXgFysVucQp1zs6S6tpHVyAjr
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1692 set thread context of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 -
Program crash 2 IoCs
pid pid_target Process procid_target 2756 1692 WerFault.exe 27 2644 2060 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 25 IoCs
description pid Process procid_target PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2060 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 29 PID 1692 wrote to memory of 2756 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 30 PID 1692 wrote to memory of 2756 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 30 PID 1692 wrote to memory of 2756 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 30 PID 1692 wrote to memory of 2756 1692 1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe 30 PID 2060 wrote to memory of 2644 2060 AppLaunch.exe 31 PID 2060 wrote to memory of 2644 2060 AppLaunch.exe 31 PID 2060 wrote to memory of 2644 2060 AppLaunch.exe 31 PID 2060 wrote to memory of 2644 2060 AppLaunch.exe 31 PID 2060 wrote to memory of 2644 2060 AppLaunch.exe 31 PID 2060 wrote to memory of 2644 2060 AppLaunch.exe 31 PID 2060 wrote to memory of 2644 2060 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe"C:\Users\Admin\AppData\Local\Temp\1c514166857aea831845a6edf6907feb5558da017adbd85b8d4e94e4723ca448.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1692 -
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:2060 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2060 -s 1963⤵
- Program crash
PID:2644
-
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 1692 -s 922⤵
- Program crash
PID:2756
-