Analysis
-
max time kernel
119s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20231020-en -
resource tags
arch:x64arch:x86image:win7-20231020-enlocale:en-usos:windows7-x64system -
submitted
29/10/2023, 22:17
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe
Resource
win7-20231020-en
3 signatures
300 seconds
Behavioral task
behavioral2
Sample
143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe
Resource
win10-20231020-en
2 signatures
300 seconds
General
-
Target
143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe
-
Size
1.1MB
-
MD5
705f18ec1261e9fdcca77128b7c28a93
-
SHA1
c2deb231ab49e09e457bcbfba582d73dad648264
-
SHA256
143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c
-
SHA512
79d59107cd382af5048e2dde102ceb403f459e6a05f147729ec0ae89066d55a504609e799fda3855dc5a1293c14a8697c63ec4c20516d383622aec4f5da7d929
-
SSDEEP
24576:JtOAl29Ad87kHCADReQuSC2FdHI3b1OQ:Jo887kHCNQ2oHI3b
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 860 set thread context of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 -
Program crash 1 IoCs
pid pid_target Process procid_target 2672 2512 WerFault.exe 28 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 860 wrote to memory of 2512 860 143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe 28 PID 2512 wrote to memory of 2672 2512 AppLaunch.exe 29 PID 2512 wrote to memory of 2672 2512 AppLaunch.exe 29 PID 2512 wrote to memory of 2672 2512 AppLaunch.exe 29 PID 2512 wrote to memory of 2672 2512 AppLaunch.exe 29 PID 2512 wrote to memory of 2672 2512 AppLaunch.exe 29 PID 2512 wrote to memory of 2672 2512 AppLaunch.exe 29 PID 2512 wrote to memory of 2672 2512 AppLaunch.exe 29
Processes
-
C:\Users\Admin\AppData\Local\Temp\143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe"C:\Users\Admin\AppData\Local\Temp\143ef51a270318b9e0ecbd31891b6190ee62658aef4391ac1e9b64d3340c4d4c.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:860 -
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:2512 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2512 -s 1963⤵
- Program crash
PID:2672
-
-