Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
140s -
max time network
119s -
platform
windows7_x64 -
resource
win7-20240704-en -
resource tags
arch:x64arch:x86image:win7-20240704-enlocale:en-usos:windows7-x64system -
submitted
28/09/2024, 23:47
Behavioral task
behavioral1
Sample
802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe
Resource
win7-20240704-en
General
-
Target
802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe
-
Size
320KB
-
MD5
f0d3fd155902430b5cfd0eb304e17b05
-
SHA1
d5dbaf9e890920aba36978472fda78b396fd1b37
-
SHA256
802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3
-
SHA512
52d728360f95f97956a6d231f4cde4f8f721a18d342c9ae17433137fc495059791030322f18ab88b2d5f038e5efcbb7bcc20c0d5d6e372cc5fa123b2b4f691d5
-
SSDEEP
6144:tD8BiI6mvJ3QJwujYT+GLl61uYVaqLIHk+MlWloSQN3GAhwA:tQBibmh3Q+FPLlKla2IHk+GUoSQN2AhH
Malware Config
Signatures
-
resource yara_rule behavioral1/memory/1952-0-0x0000000000400000-0x0000000000531000-memory.dmp upx behavioral1/memory/1952-3-0x0000000000400000-0x0000000000531000-memory.dmp upx -
System Location Discovery: System Language Discovery 1 TTPs 1 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 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe -
Suspicious behavior: EnumeratesProcesses 1 IoCs
pid Process 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe -
Suspicious behavior: MapViewOfSection 23 IoCs
pid Process 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe -
Suspicious use of SetWindowsHookEx 2 IoCs
pid Process 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 1952 wrote to memory of 384 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 3 PID 1952 wrote to memory of 384 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 3 PID 1952 wrote to memory of 384 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 3 PID 1952 wrote to memory of 384 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 3 PID 1952 wrote to memory of 384 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 3 PID 1952 wrote to memory of 384 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 3 PID 1952 wrote to memory of 392 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 4 PID 1952 wrote to memory of 392 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 4 PID 1952 wrote to memory of 392 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 4 PID 1952 wrote to memory of 392 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 4 PID 1952 wrote to memory of 392 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 4 PID 1952 wrote to memory of 392 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 4 PID 1952 wrote to memory of 432 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 5 PID 1952 wrote to memory of 432 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 5 PID 1952 wrote to memory of 432 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 5 PID 1952 wrote to memory of 432 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 5 PID 1952 wrote to memory of 432 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 5 PID 1952 wrote to memory of 432 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 5 PID 1952 wrote to memory of 476 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 6 PID 1952 wrote to memory of 476 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 6 PID 1952 wrote to memory of 476 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 6 PID 1952 wrote to memory of 476 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 6 PID 1952 wrote to memory of 476 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 6 PID 1952 wrote to memory of 476 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 6 PID 1952 wrote to memory of 492 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 7 PID 1952 wrote to memory of 492 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 7 PID 1952 wrote to memory of 492 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 7 PID 1952 wrote to memory of 492 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 7 PID 1952 wrote to memory of 492 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 7 PID 1952 wrote to memory of 492 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 7 PID 1952 wrote to memory of 500 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 8 PID 1952 wrote to memory of 500 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 8 PID 1952 wrote to memory of 500 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 8 PID 1952 wrote to memory of 500 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 8 PID 1952 wrote to memory of 500 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 8 PID 1952 wrote to memory of 500 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 8 PID 1952 wrote to memory of 596 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 9 PID 1952 wrote to memory of 596 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 9 PID 1952 wrote to memory of 596 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 9 PID 1952 wrote to memory of 596 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 9 PID 1952 wrote to memory of 596 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 9 PID 1952 wrote to memory of 596 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 9 PID 1952 wrote to memory of 676 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 10 PID 1952 wrote to memory of 676 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 10 PID 1952 wrote to memory of 676 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 10 PID 1952 wrote to memory of 676 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 10 PID 1952 wrote to memory of 676 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 10 PID 1952 wrote to memory of 676 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 10 PID 1952 wrote to memory of 752 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 11 PID 1952 wrote to memory of 752 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 11 PID 1952 wrote to memory of 752 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 11 PID 1952 wrote to memory of 752 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 11 PID 1952 wrote to memory of 752 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 11 PID 1952 wrote to memory of 752 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 11 PID 1952 wrote to memory of 816 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 12 PID 1952 wrote to memory of 816 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 12 PID 1952 wrote to memory of 816 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 12 PID 1952 wrote to memory of 816 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 12 PID 1952 wrote to memory of 816 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 12 PID 1952 wrote to memory of 816 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 12 PID 1952 wrote to memory of 856 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 13 PID 1952 wrote to memory of 856 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 13 PID 1952 wrote to memory of 856 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 13 PID 1952 wrote to memory of 856 1952 802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe 13
Processes
-
C:\Windows\system32\wininit.exewininit.exe1⤵PID:384
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe2⤵PID:476
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch3⤵PID:596
-
C:\Windows\system32\DllHost.exeC:\Windows\system32\DllHost.exe /Processid:{3EB3C877-1F16-487C-9050-104DBCD66683}4⤵PID:1304
-
-
C:\Windows\system32\wbem\wmiprvse.exeC:\Windows\system32\wbem\wmiprvse.exe4⤵PID:284
-
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k RPCSS3⤵PID:676
-
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted3⤵PID:752
-
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted3⤵PID:816
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"4⤵PID:1180
-
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k netsvcs3⤵PID:856
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalService3⤵PID:964
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService3⤵PID:236
-
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe3⤵PID:324
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork3⤵PID:1076
-
-
C:\Windows\system32\taskhost.exe"taskhost.exe"3⤵PID:1116
-
-
C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPSVC.EXE"C:\Program Files\Common Files\Microsoft Shared\OfficeSoftwareProtectionPlatform\OSPPSVC.EXE"3⤵PID:1632
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation3⤵PID:2476
-
-
C:\Windows\system32\sppsvc.exeC:\Windows\system32\sppsvc.exe3⤵PID:2220
-
-
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe2⤵PID:492
-
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵PID:500
-
-
C:\Windows\system32\csrss.exe%SystemRoot%\system32\csrss.exe ObjectDirectory=\Windows SharedSection=1024,20480,768 Windows=On SubSystemType=Windows ServerDll=basesrv,1 ServerDll=winsrv:UserServerDllInitialization,3 ServerDll=winsrv:ConServerDllInitialization,2 ServerDll=sxssrv,4 ProfileControl=Off MaxRequestThreads=161⤵PID:392
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵PID:432
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1208
-
C:\Users\Admin\AppData\Local\Temp\802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe"C:\Users\Admin\AppData\Local\Temp\802fc0db2030b37447f5f1a55a7b8e2adb79aea66da126ddb6cb713449b7d5f3.exe"2⤵
- System Location Discovery: System Language Discovery
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1952
-