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
13-10-2023 21:26
Static task
static1
Behavioral task
behavioral1
Sample
3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe
Resource
win10v2004-20230915-en
General
-
Target
3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe
-
Size
1.4MB
-
MD5
bc47ed73bb11a685c6856290f56f41ce
-
SHA1
724951786bfc9108498bd7a9c7ca5a9d3e26e01b
-
SHA256
3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31
-
SHA512
5d10a0c40107c425004386516d84ef6d52e81d50f74fa5d8c7d870245212ace770df7e97a286dfcbd85513102012c914475bfd95599186525e8b50744cad4feb
-
SSDEEP
24576:si4SpRZWGb5zqSbVh8EwpOomaISQT0U70oHw5VEPMrP8/ygVqaTWEGfi4:F4SXZWS5Nv8EwpOHJSQg3oYU0P8//qaq
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2332 set thread context of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 -
Program crash 1 IoCs
pid pid_target Process procid_target 2640 2200 WerFault.exe 30 -
Suspicious use of WriteProcessMemory 28 IoCs
description pid Process procid_target PID 2332 wrote to memory of 2876 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 29 PID 2332 wrote to memory of 2876 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 29 PID 2332 wrote to memory of 2876 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 29 PID 2332 wrote to memory of 2876 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 29 PID 2332 wrote to memory of 2876 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 29 PID 2332 wrote to memory of 2876 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 29 PID 2332 wrote to memory of 2876 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 29 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2332 wrote to memory of 2200 2332 3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe 30 PID 2200 wrote to memory of 2640 2200 AppLaunch.exe 31 PID 2200 wrote to memory of 2640 2200 AppLaunch.exe 31 PID 2200 wrote to memory of 2640 2200 AppLaunch.exe 31 PID 2200 wrote to memory of 2640 2200 AppLaunch.exe 31 PID 2200 wrote to memory of 2640 2200 AppLaunch.exe 31 PID 2200 wrote to memory of 2640 2200 AppLaunch.exe 31 PID 2200 wrote to memory of 2640 2200 AppLaunch.exe 31
Processes
-
C:\Users\Admin\AppData\Local\Temp\3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe"C:\Users\Admin\AppData\Local\Temp\3c05d898d51f9556633769b3d1ed89cd17824d9c50f4bc0b9cc59d6947f29b31.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2332 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2876
-
-
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:2200 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2200 -s 2003⤵
- Program crash
PID:2640
-
-