Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
120s -
max time network
123s -
platform
windows7_x64 -
resource
win7-20230831-en -
resource tags
arch:x64arch:x86image:win7-20230831-enlocale:en-usos:windows7-x64system -
submitted
13/10/2023, 12:32
Static task
static1
Behavioral task
behavioral1
Sample
ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe
Resource
win7-20230831-en
Behavioral task
behavioral2
Sample
ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe
Resource
win10v2004-20230915-en
General
-
Target
ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe
-
Size
1.1MB
-
MD5
247b6285959829b0b9372c3390a8b848
-
SHA1
6f3ed4465930e71f377097601a1691fe8ab0ef28
-
SHA256
ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939
-
SHA512
86dd9c92be69ce719aedf93d7adb25786bab560a0bc62fd47c8b8cafa62cd359368f9c8c34d1722aad30e793c2c1fb37eaac6637d10e6b806d251dde356346cf
-
SSDEEP
24576:24LyjCokJEojUZ/45iSaSzkxPV6ex9TB5EY:2qokJEojk/132kxNTL5n
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2472 set thread context of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 -
Program crash 1 IoCs
pid pid_target Process procid_target 1620 2472 WerFault.exe 27 -
Suspicious use of WriteProcessMemory 18 IoCs
description pid Process procid_target PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 2584 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 29 PID 2472 wrote to memory of 1620 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 30 PID 2472 wrote to memory of 1620 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 30 PID 2472 wrote to memory of 1620 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 30 PID 2472 wrote to memory of 1620 2472 ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe 30
Processes
-
C:\Users\Admin\AppData\Local\Temp\ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe"C:\Users\Admin\AppData\Local\Temp\ca017a9bff57d4ca8ab82d249acc9b429ed71c3501f787c4c5cecd190f5e5939.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:2472 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2584
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2472 -s 522⤵
- Program crash
PID:1620
-