Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
119s -
max time network
120s -
platform
windows7_x64 -
resource
win7-20240903-en -
resource tags
arch:x64arch:x86image:win7-20240903-enlocale:en-usos:windows7-x64system -
submitted
17/09/2024, 01:10
Static task
static1
Behavioral task
behavioral1
Sample
3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe
Resource
win7-20240903-en
General
-
Target
3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe
-
Size
207KB
-
MD5
c2959894fc8b6dc3059469fed76e49af
-
SHA1
bceaade79890b40a5cc74bd9c25ec50cb45de7d7
-
SHA256
3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7
-
SHA512
c6daa3bfb90f8973c69caeb279ac3ebf06028599a4339d8a120259b70c953ce4e8bbc7325eedff4b6fd74fae35c16d92fb473b4eea381bd939482628ef5a9ff8
-
SSDEEP
3072:Kt1DWAfPaMhSWmxApK0i8JSTfhfsjsV+7qIdRr6VowELW3AKvaEeJYY/dlSJKYzt:KtlWAfPaM3E0iOqM+CEowCwqRJYGOEO
Malware Config
Extracted
stealc
default
http://46.8.231.109
-
url_path
/c4754d4f680ead72.php
Signatures
-
Suspicious use of SetThreadContext 1 IoCs
description pid Process procid_target PID 2640 set thread context of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 -
Program crash 1 IoCs
pid pid_target Process procid_target 2668 2812 WerFault.exe 35 -
System Location Discovery: System Language Discovery 1 TTPs 2 IoCs
Attempt gather information about the system language of a victim in order to infer the geographical location of that host.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Control\NLS\Language RegAsm.exe -
Suspicious use of WriteProcessMemory 38 IoCs
description pid Process procid_target PID 2640 wrote to memory of 2788 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 32 PID 2640 wrote to memory of 2788 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 32 PID 2640 wrote to memory of 2788 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 32 PID 2640 wrote to memory of 2788 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 32 PID 2640 wrote to memory of 2788 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 32 PID 2640 wrote to memory of 2788 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 32 PID 2640 wrote to memory of 2788 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 32 PID 2640 wrote to memory of 2792 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 33 PID 2640 wrote to memory of 2792 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 33 PID 2640 wrote to memory of 2792 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 33 PID 2640 wrote to memory of 2792 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 33 PID 2640 wrote to memory of 2792 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 33 PID 2640 wrote to memory of 2792 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 33 PID 2640 wrote to memory of 2792 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 33 PID 2640 wrote to memory of 2816 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 34 PID 2640 wrote to memory of 2816 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 34 PID 2640 wrote to memory of 2816 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 34 PID 2640 wrote to memory of 2816 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 34 PID 2640 wrote to memory of 2816 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 34 PID 2640 wrote to memory of 2816 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 34 PID 2640 wrote to memory of 2816 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 34 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2640 wrote to memory of 2812 2640 3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe 35 PID 2812 wrote to memory of 2668 2812 RegAsm.exe 36 PID 2812 wrote to memory of 2668 2812 RegAsm.exe 36 PID 2812 wrote to memory of 2668 2812 RegAsm.exe 36 PID 2812 wrote to memory of 2668 2812 RegAsm.exe 36
Processes
-
C:\Users\Admin\AppData\Local\Temp\3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe"C:\Users\Admin\AppData\Local\Temp\3f9daff50fd608eb15026903bf89ad2aafae0b344f0fd82e9ea82d4071a781d7.exe"1⤵
- Suspicious use of SetThreadContext
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:2640 -
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2788
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2792
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵PID:2816
-
-
C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"C:\Windows\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe"2⤵
- System Location Discovery: System Language Discovery
- Suspicious use of WriteProcessMemory
PID:2812 -
C:\Windows\SysWOW64\WerFault.exeC:\Windows\SysWOW64\WerFault.exe -u -p 2812 -s 2523⤵
- Program crash
PID:2668
-
-