Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
136s -
max time network
153s -
platform
windows7_x64 -
resource
win7-20220901-en -
resource tags
arch:x64arch:x86image:win7-20220901-enlocale:en-usos:windows7-x64system -
submitted
27/11/2022, 14:01
Static task
static1
Behavioral task
behavioral1
Sample
cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe
Resource
win10v2004-20221111-en
General
-
Target
cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe
-
Size
11.3MB
-
MD5
d9ab08c2d38084d6fdb428637e00b85a
-
SHA1
b5a77b2106b880d065719d286625a1040e489efb
-
SHA256
cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b
-
SHA512
4e1bea8043b78caf03e89b09b36fe5b7711932eae4b0e512659524140772b68131a9e3f8faf233b070b70eccb9160e72244fa024193c7c8b0ddee0ba7b653df4
-
SSDEEP
196608:AtrD5vWG4ov+Tbo16rHtPPf3znaXioTjSzT4SSGExCe2k:AtxF8hNPPvzaXZTjqToGKak
Malware Config
Signatures
-
Suspicious use of SetThreadContext 2 IoCs
description pid Process procid_target PID 1696 set thread context of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1680 set thread context of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 -
Enumerates physical storage devices 1 TTPs
Attempts to interact with connected storage/optical drive(s). Likely ransomware behaviour.
-
Suspicious use of WriteProcessMemory 45 IoCs
description pid Process procid_target PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1696 wrote to memory of 1680 1696 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 27 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28 PID 1680 wrote to memory of 1768 1680 cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe 28
Processes
-
C:\Users\Admin\AppData\Local\Temp\cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe"C:\Users\Admin\AppData\Local\Temp\cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1696 -
C:\Users\Admin\AppData\Local\Temp\cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe"C:\Users\Admin\AppData\Local\Temp\cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe"2⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:1680 -
C:\Users\Admin\AppData\Local\Temp\cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe"C:\Users\Admin\AppData\Local\Temp\cec0c44b64c327fe017f65e381e4c2d0e937f2c47cfbf6a31aed9ca024e32a5b.exe"3⤵PID:1768
-
-