Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
110s -
max time network
115s -
platform
windows10-1703_x64 -
resource
win10-20230915-en -
resource tags
arch:x64arch:x86image:win10-20230915-enlocale:en-usos:windows10-1703-x64system -
submitted
03/10/2023, 07:08
Static task
static1
1 signatures
General
-
Target
ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe
-
Size
285KB
-
MD5
ce59db077087ca30bea085b3ae745d92
-
SHA1
34d709f58158dc2feb4531a365612225b23bdeda
-
SHA256
ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da
-
SHA512
9908582e2e3abd0cf62b3b85d397390abfdeefd6d5a8a0bc8333b0d37ed70813a9026f8dd0b83d5e62be3fda2723f0a5e0eee830618e87906d437d4befc26863
-
SSDEEP
6144:BMU+Elo4WGFw16Hciac/XxxvKEsmCVM8QdqQnnnfFCzSox:qU+ElodKHciac/Xx/s1QJFCvx
Malware Config
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 4952 set thread context of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 -
Program crash 1 IoCs
pid pid_target Process procid_target 2736 4952 WerFault.exe 68 -
Suspicious use of WriteProcessMemory 13 IoCs
description pid Process procid_target PID 4952 wrote to memory of 2176 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 70 PID 4952 wrote to memory of 2176 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 70 PID 4952 wrote to memory of 2176 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 70 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71 PID 4952 wrote to memory of 2496 4952 ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe 71
Processes
-
C:\Users\Admin\AppData\Local\Temp\ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe"C:\Users\Admin\AppData\Local\Temp\ccf6729d16e8226d16da452eef685a60a60e175be7d66e0bf469b53ee1bf85da.exe"1⤵
- Suspicious use of SetThreadContext
- Suspicious use of WriteProcessMemory
PID:4952 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2176
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\AppLaunch.exe"2⤵PID:2496
-
-
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 4952 -s 3722⤵
- Program crash
PID:2736
-