Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
128s -
max time network
136s -
platform
windows10-1703_x64 -
resource
win10-20230915-en -
resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system -
submitted
18/09/2023, 22:16
Static task
static1
1 signatures
Behavioral task
behavioral1
Sample
47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe
Resource
win10-20230915-en
2 signatures
150 seconds
General
-
Target
47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe
-
Size
393KB
-
MD5
8b4d09825af297cf5768840a7983ffb5
-
SHA1
e5d5334c52dbd215ed9fe536e6f217e5b253aa6b
-
SHA256
47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0
-
SHA512
fcab444eccf12d8e9e78b2f81a44cf2b19c6159f0de9498a42aea17735c8bc5b997bbffb8e7ac90e77a2d3e30bc13d9b588256c95eb01f9b753cde883e60100d
-
SSDEEP
6144:TPMjEL2jicP5iOo2T8VrSd/sUAO1klvbjsdGL9bQDsluyyYOBbEJVBsK1Sa:TPMKqiG59oubkNbCGBQDslVVn1Sa
Score
5/10
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 672 set thread context of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 -
Suspicious use of WriteProcessMemory 10 IoCs
description pid Process procid_target PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70 PID 672 wrote to memory of 4368 672 47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe 70
Processes
-
C:\Users\Admin\AppData\Local\Temp\47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe"C:\Users\Admin\AppData\Local\Temp\47596e60edb37e0fc0a3affcb80df246a585d653d8253fe82531f351873c70f0.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:672 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:4368
-