Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
84s -
max time network
124s -
platform
windows10-2004_x64 -
resource
win10v2004-20220901-en -
resource tags
arch:x64arch:x86image:win10v2004-20220901-enlocale:en-usos:windows10-2004-x64system -
submitted
29/11/2022, 14:31
Static task
static1
Behavioral task
behavioral1
Sample
cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe
Resource
win10v2004-20220901-en
General
-
Target
cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe
-
Size
152KB
-
MD5
f4723d0ca2f1b5c9be01437d1eb4d835
-
SHA1
bce452892d0152589a89299afa2a75696e8c9b03
-
SHA256
cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6
-
SHA512
4e76c51d4fe86c03fe309aaa02f6785045b32abdce25d47d7904cee4d5c5041f8ea46b71b8ef977c2e0d24d413bbab916af7de587e9053ef5b557963011a550c
-
SSDEEP
3072:5OF1e11TFWpNohYkQr0jeLwJr95bJoBFx/63P:oUYQqLwhHbWLxC3
Malware Config
Signatures
-
Adds policy Run key to start application 2 TTPs 2 IoCs
description ioc Process Key created \REGISTRY\USER\S-1-5-21-929662420-1054238289-2961194603-1000\Software\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run svchost.exe Set value (str) \REGISTRY\USER\S-1-5-21-929662420-1054238289-2961194603-1000\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Explorer\Run\Mozilla = "C:\\Users\\Admin\\AppData\\Roaming\\6CA84E.exe" svchost.exe -
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\disk\Enum\0 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe -
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 5064 set thread context of 540 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 76 -
Suspicious behavior: MapViewOfSection 2 IoCs
pid Process 540 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 540 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe -
Suspicious use of WriteProcessMemory 11 IoCs
description pid Process procid_target PID 5064 wrote to memory of 540 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 76 PID 5064 wrote to memory of 540 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 76 PID 5064 wrote to memory of 540 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 76 PID 5064 wrote to memory of 540 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 76 PID 5064 wrote to memory of 540 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 76 PID 5064 wrote to memory of 540 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 76 PID 5064 wrote to memory of 540 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 76 PID 5064 wrote to memory of 540 5064 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 76 PID 540 wrote to memory of 4980 540 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 83 PID 540 wrote to memory of 4980 540 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 83 PID 540 wrote to memory of 4980 540 cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe 83
Processes
-
C:\Users\Admin\AppData\Local\Temp\cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe"C:\Users\Admin\AppData\Local\Temp\cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:5064 -
C:\Users\Admin\AppData\Local\Temp\cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe"C:\Users\Admin\AppData\Local\Temp\cb8c6531b448174dabbeeb639399c4ff5c48c4c1fbddb85f114958467e19eca6.exe"2⤵
- Maps connected drives based on registry
- Suspicious behavior: MapViewOfSection
- Suspicious use of WriteProcessMemory
PID:540 -
C:\Windows\SysWOW64\svchost.exesvchost.exe3⤵
- Adds policy Run key to start application
PID:4980
-
-