Windows 7 deprecation
Windows 7 will be removed from tria.ge on 2025-03-31
Analysis
-
max time kernel
44s -
max time network
49s -
platform
windows7_x64 -
resource
win7-20220901-en -
resource tags
arch:x64arch:x86image:win7-20220901-enlocale:en-usos:windows7-x64system -
submitted
11/10/2022, 21:42
Static task
static1
Behavioral task
behavioral1
Sample
7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe
Resource
win10v2004-20220812-en
General
-
Target
7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe
-
Size
162KB
-
MD5
641ee9e4f79a6618d82f032543542b50
-
SHA1
22402e61259db4ec850aaeea4942043fa3f7c25a
-
SHA256
7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded
-
SHA512
ffa03fd7971e8509224ee5ad13af697599f7040218cc7f81ac8379206cc47b237449ea5b491a2e966d94f066cb87a8caee6b31d607772ca7d10f9af8892efdcb
-
SSDEEP
3072:x4d5Eow6rzVJaolwYG0/RZJAV9DoRBbGyI3RnYLlxOFRqF/uC:WdvrzKYW9URxjI3iLDOFRB
Malware Config
Signatures
-
Suspicious behavior: EnumeratesProcesses 1 IoCs
pid Process 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe -
Suspicious behavior: MapViewOfSection 21 IoCs
pid Process 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe -
Suspicious use of SetWindowsHookAW 1 IoCs
pid Process 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 620 wrote to memory of 372 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 5 PID 620 wrote to memory of 372 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 5 PID 620 wrote to memory of 372 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 5 PID 620 wrote to memory of 372 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 5 PID 620 wrote to memory of 372 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 5 PID 620 wrote to memory of 372 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 5 PID 620 wrote to memory of 372 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 5 PID 620 wrote to memory of 384 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 4 PID 620 wrote to memory of 384 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 4 PID 620 wrote to memory of 384 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 4 PID 620 wrote to memory of 384 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 4 PID 620 wrote to memory of 384 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 4 PID 620 wrote to memory of 384 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 4 PID 620 wrote to memory of 384 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 4 PID 620 wrote to memory of 420 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 3 PID 620 wrote to memory of 420 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 3 PID 620 wrote to memory of 420 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 3 PID 620 wrote to memory of 420 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 3 PID 620 wrote to memory of 420 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 3 PID 620 wrote to memory of 420 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 3 PID 620 wrote to memory of 420 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 3 PID 620 wrote to memory of 464 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 2 PID 620 wrote to memory of 464 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 2 PID 620 wrote to memory of 464 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 2 PID 620 wrote to memory of 464 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 2 PID 620 wrote to memory of 464 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 2 PID 620 wrote to memory of 464 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 2 PID 620 wrote to memory of 464 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 2 PID 620 wrote to memory of 480 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 1 PID 620 wrote to memory of 480 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 1 PID 620 wrote to memory of 480 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 1 PID 620 wrote to memory of 480 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 1 PID 620 wrote to memory of 480 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 1 PID 620 wrote to memory of 480 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 1 PID 620 wrote to memory of 480 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 1 PID 620 wrote to memory of 488 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 8 PID 620 wrote to memory of 488 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 8 PID 620 wrote to memory of 488 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 8 PID 620 wrote to memory of 488 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 8 PID 620 wrote to memory of 488 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 8 PID 620 wrote to memory of 488 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 8 PID 620 wrote to memory of 488 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 8 PID 620 wrote to memory of 592 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 25 PID 620 wrote to memory of 592 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 25 PID 620 wrote to memory of 592 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 25 PID 620 wrote to memory of 592 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 25 PID 620 wrote to memory of 592 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 25 PID 620 wrote to memory of 592 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 25 PID 620 wrote to memory of 592 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 25 PID 620 wrote to memory of 668 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 24 PID 620 wrote to memory of 668 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 24 PID 620 wrote to memory of 668 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 24 PID 620 wrote to memory of 668 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 24 PID 620 wrote to memory of 668 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 24 PID 620 wrote to memory of 668 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 24 PID 620 wrote to memory of 668 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 24 PID 620 wrote to memory of 752 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 9 PID 620 wrote to memory of 752 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 9 PID 620 wrote to memory of 752 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 9 PID 620 wrote to memory of 752 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 9 PID 620 wrote to memory of 752 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 9 PID 620 wrote to memory of 752 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 9 PID 620 wrote to memory of 752 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 9 PID 620 wrote to memory of 804 620 7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe 10
Processes
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe1⤵PID:480
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe1⤵PID:464
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted2⤵PID:752
-
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted2⤵PID:804
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"3⤵PID:1168
-
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k netsvcs2⤵PID:884
-
\\?\C:\Windows\system32\wbem\WMIADAP.EXEwmiadap.exe /F /T /R3⤵PID:2012
-
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService2⤵PID:340
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork2⤵PID:1080
-
-
C:\Windows\system32\taskhost.exe"taskhost.exe"2⤵PID:1108
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation2⤵PID:1788
-
-
C:\Windows\system32\sppsvc.exeC:\Windows\system32\sppsvc.exe2⤵PID:1656
-
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe2⤵PID:836
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalService2⤵PID:840
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k RPCSS2⤵PID:668
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch2⤵PID:592
-
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵PID:420
-
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:384
-
C:\Windows\system32\wininit.exewininit.exe1⤵PID:372
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵PID:488
-
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1192
-
C:\Users\Admin\AppData\Local\Temp\7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe"C:\Users\Admin\AppData\Local\Temp\7e8fa84f6e0031eab9ec3415c2b7832465605802ff549035bd4f278abddd2ded.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookAW
- Suspicious use of WriteProcessMemory
PID:620
-