Analysis
-
max time kernel
119s -
max time network
124s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
13-10-2023 03:59
Static task
static1
Behavioral task
behavioral1
Sample
5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe
Resource
win10v2004-20230915-en
General
-
Target
5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe
-
Size
1.2MB
-
MD5
c05705864c85e54836ae624d3aebd98b
-
SHA1
0e08b69da37dfe83204af568480d18e81a19b0a1
-
SHA256
5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39
-
SHA512
dd33a64ad11619502909aaaa92b0bcf2331a5d25ab11c770e115931daef1bd85d3c064703610858158309e04b1a66a29ee2cc77fa8d3d7296f07f3bc0154e4bc
-
SSDEEP
24576:H74crM7gaMCFQLilokdKHcVuAhbgplActivoQQJlwN56EuQ2DzKesCn42ZG:b4crytMCFQYkTgqlActyoryZFue92ZG
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 1668 set thread context of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 -
Program crash 1 IoCs
pid pid_target Process procid_target 2672 2700 WerFault.exe 29 -
Suspicious use of WriteProcessMemory 21 IoCs
description pid Process procid_target PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 1668 wrote to memory of 2700 1668 5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe 29 PID 2700 wrote to memory of 2672 2700 AppLaunch.exe 30 PID 2700 wrote to memory of 2672 2700 AppLaunch.exe 30 PID 2700 wrote to memory of 2672 2700 AppLaunch.exe 30 PID 2700 wrote to memory of 2672 2700 AppLaunch.exe 30 PID 2700 wrote to memory of 2672 2700 AppLaunch.exe 30 PID 2700 wrote to memory of 2672 2700 AppLaunch.exe 30 PID 2700 wrote to memory of 2672 2700 AppLaunch.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe"C:\Users\Admin\AppData\Local\Temp\5af9665965bf8689a2908e3dd0392ef128d78a2b6130fd989223b54f69c06e39.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1668 -
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:2700 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2700 -s 2003⤵
- Program crash
PID:2672
-
-