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
07/11/2022, 22:07
Static task
static1
Behavioral task
behavioral1
Sample
f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe
Resource
win10v2004-20220901-en
General
-
Target
f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe
-
Size
488KB
-
MD5
0f7cc9653df0c3be4dc36e99b7477000
-
SHA1
81842fefc3b1d53d11a023886278d8a766b2557c
-
SHA256
f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581
-
SHA512
c37d51d51fad31c4421b351b041cb526bad549d7108b4b3b7dddbfecad880958330c126021474666c6364fdfff224cf6465a0a608d13c67ff9ecfa72aeb23905
-
SSDEEP
12288:3lHIeD3h/N1jpZNi9R+swevu2XVgwZCeUTM4n:KANtN81UwO
Malware Config
Signatures
-
Maps connected drives based on registry 3 TTPs 2 IoCs
Disk information is often read in order to detect sandboxing environments.
description ioc Process Key opened \REGISTRY\MACHINE\SYSTEM\ControlSet001\Services\Disk\Enum f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe Key value queried \REGISTRY\MACHINE\SYSTEM\ControlSet001\services\Disk\Enum\0 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe -
Suspicious behavior: EnumeratesProcesses 2 IoCs
pid Process 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe -
Suspicious behavior: MapViewOfSection 21 IoCs
pid Process 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
description pid Process Token: SeDebugPrivilege 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
pid Process 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe -
Suspicious use of WriteProcessMemory 64 IoCs
description pid Process procid_target PID 1048 wrote to memory of 368 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 5 PID 1048 wrote to memory of 368 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 5 PID 1048 wrote to memory of 368 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 5 PID 1048 wrote to memory of 368 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 5 PID 1048 wrote to memory of 368 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 5 PID 1048 wrote to memory of 368 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 5 PID 1048 wrote to memory of 368 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 5 PID 1048 wrote to memory of 380 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 4 PID 1048 wrote to memory of 380 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 4 PID 1048 wrote to memory of 380 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 4 PID 1048 wrote to memory of 380 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 4 PID 1048 wrote to memory of 380 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 4 PID 1048 wrote to memory of 380 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 4 PID 1048 wrote to memory of 380 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 4 PID 1048 wrote to memory of 416 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 3 PID 1048 wrote to memory of 416 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 3 PID 1048 wrote to memory of 416 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 3 PID 1048 wrote to memory of 416 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 3 PID 1048 wrote to memory of 416 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 3 PID 1048 wrote to memory of 416 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 3 PID 1048 wrote to memory of 416 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 3 PID 1048 wrote to memory of 460 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 2 PID 1048 wrote to memory of 460 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 2 PID 1048 wrote to memory of 460 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 2 PID 1048 wrote to memory of 460 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 2 PID 1048 wrote to memory of 460 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 2 PID 1048 wrote to memory of 460 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 2 PID 1048 wrote to memory of 460 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 2 PID 1048 wrote to memory of 476 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1 PID 1048 wrote to memory of 476 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1 PID 1048 wrote to memory of 476 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1 PID 1048 wrote to memory of 476 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1 PID 1048 wrote to memory of 476 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1 PID 1048 wrote to memory of 476 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1 PID 1048 wrote to memory of 476 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 1 PID 1048 wrote to memory of 484 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 8 PID 1048 wrote to memory of 484 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 8 PID 1048 wrote to memory of 484 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 8 PID 1048 wrote to memory of 484 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 8 PID 1048 wrote to memory of 484 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 8 PID 1048 wrote to memory of 484 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 8 PID 1048 wrote to memory of 484 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 8 PID 1048 wrote to memory of 592 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 25 PID 1048 wrote to memory of 592 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 25 PID 1048 wrote to memory of 592 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 25 PID 1048 wrote to memory of 592 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 25 PID 1048 wrote to memory of 592 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 25 PID 1048 wrote to memory of 592 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 25 PID 1048 wrote to memory of 592 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 25 PID 1048 wrote to memory of 672 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 24 PID 1048 wrote to memory of 672 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 24 PID 1048 wrote to memory of 672 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 24 PID 1048 wrote to memory of 672 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 24 PID 1048 wrote to memory of 672 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 24 PID 1048 wrote to memory of 672 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 24 PID 1048 wrote to memory of 672 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 24 PID 1048 wrote to memory of 756 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 23 PID 1048 wrote to memory of 756 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 23 PID 1048 wrote to memory of 756 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 23 PID 1048 wrote to memory of 756 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 23 PID 1048 wrote to memory of 756 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 23 PID 1048 wrote to memory of 756 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 23 PID 1048 wrote to memory of 756 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 23 PID 1048 wrote to memory of 800 1048 f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe 9
Processes
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe1⤵PID:476
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe1⤵PID:460
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted2⤵PID:800
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"3⤵PID:1340
-
-
-
C:\Windows\system32\taskhost.exe"taskhost.exe"2⤵PID:1264
-
-
C:\Windows\system32\sppsvc.exeC:\Windows\system32\sppsvc.exe2⤵PID:1752
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation2⤵PID:1676
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork2⤵PID:1028
-
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe2⤵PID:284
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService2⤵PID:300
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k netsvcs2⤵PID:868
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalService2⤵PID:844
-
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted2⤵PID:756
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k RPCSS2⤵PID:672
-
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch2⤵PID:592
-
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵PID:416
-
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:380
-
C:\Windows\system32\wininit.exewininit.exe1⤵PID:368
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵PID:484
-
-
\\?\C:\Windows\system32\wbem\WMIADAP.EXEwmiadap.exe /F /T /R1⤵PID:1604
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1400
-
C:\Users\Admin\AppData\Local\Temp\f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe"C:\Users\Admin\AppData\Local\Temp\f54af8a0870f1b7b520397c1e34f15a62eb733e6b0cdefe42eea175fa9fc6581.exe"2⤵
- Maps connected drives based on registry
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
PID:1048
-