Analysis
-
max time kernel
9s -
max time network
35s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 15:59
Static task
static1
Behavioral task
behavioral1
Sample
28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe
Resource
win10v2004-20220812-en
General
-
Target
28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe
-
Size
412KB
-
MD5
40f8aa99f4d57dc1a8c08d8ed5502baf
-
SHA1
bde2cd5101642316c5f8b16761c30bae553d5b1d
-
SHA256
28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0
-
SHA512
0dfef531cfe729fdccd3d2f784f55a0e4f724cfc98b33c5a034be239ddd30d0a7529108dae1230137ea1cba9a36af157829bf02ef280cda6b57e05a25f9d6e52
-
SSDEEP
6144:8GWK9s2n1sDEm7SUknwoD6AaeICSj7kEoed0PFn0wccccccccmQP:89ysBOnKt7oUQ
Malware Config
Signatures
-
Suspicious behavior: EnumeratesProcesses 1 IoCs
Processes:
28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exepid process 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe -
Suspicious behavior: MapViewOfSection 22 IoCs
Processes:
28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exepid process 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exedescription pid process Token: SeDebugPrivilege 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exedescription pid process target process PID 1640 wrote to memory of 368 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe wininit.exe PID 1640 wrote to memory of 368 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe wininit.exe PID 1640 wrote to memory of 368 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe wininit.exe PID 1640 wrote to memory of 368 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe wininit.exe PID 1640 wrote to memory of 368 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe wininit.exe PID 1640 wrote to memory of 368 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe wininit.exe PID 1640 wrote to memory of 368 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe wininit.exe PID 1640 wrote to memory of 388 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe csrss.exe PID 1640 wrote to memory of 388 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe csrss.exe PID 1640 wrote to memory of 388 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe csrss.exe PID 1640 wrote to memory of 388 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe csrss.exe PID 1640 wrote to memory of 388 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe csrss.exe PID 1640 wrote to memory of 388 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe csrss.exe PID 1640 wrote to memory of 388 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe csrss.exe PID 1640 wrote to memory of 424 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe winlogon.exe PID 1640 wrote to memory of 424 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe winlogon.exe PID 1640 wrote to memory of 424 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe winlogon.exe PID 1640 wrote to memory of 424 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe winlogon.exe PID 1640 wrote to memory of 424 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe winlogon.exe PID 1640 wrote to memory of 424 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe winlogon.exe PID 1640 wrote to memory of 424 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe winlogon.exe PID 1640 wrote to memory of 468 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe services.exe PID 1640 wrote to memory of 468 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe services.exe PID 1640 wrote to memory of 468 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe services.exe PID 1640 wrote to memory of 468 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe services.exe PID 1640 wrote to memory of 468 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe services.exe PID 1640 wrote to memory of 468 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe services.exe PID 1640 wrote to memory of 468 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe services.exe PID 1640 wrote to memory of 484 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsass.exe PID 1640 wrote to memory of 484 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsass.exe PID 1640 wrote to memory of 484 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsass.exe PID 1640 wrote to memory of 484 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsass.exe PID 1640 wrote to memory of 484 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsass.exe PID 1640 wrote to memory of 484 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsass.exe PID 1640 wrote to memory of 484 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsass.exe PID 1640 wrote to memory of 492 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsm.exe PID 1640 wrote to memory of 492 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsm.exe PID 1640 wrote to memory of 492 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsm.exe PID 1640 wrote to memory of 492 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsm.exe PID 1640 wrote to memory of 492 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsm.exe PID 1640 wrote to memory of 492 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsm.exe PID 1640 wrote to memory of 492 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe lsm.exe PID 1640 wrote to memory of 592 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 592 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 592 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 592 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 592 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 592 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 592 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 668 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 668 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 668 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 668 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 668 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 668 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 668 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 752 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 752 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 752 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 752 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 752 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 752 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 752 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe PID 1640 wrote to memory of 800 1640 28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe svchost.exe
Processes
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe1⤵PID:484
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe1⤵PID:468
-
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:1200
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService2⤵PID:272
-
C:\Windows\system32\taskhost.exe"taskhost.exe"2⤵PID:1120
-
C:\Windows\system32\sppsvc.exeC:\Windows\system32\sppsvc.exe2⤵PID:1876
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation2⤵PID:1856
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork2⤵PID:1040
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe2⤵PID:536
-
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:752
-
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:424
-
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:388
-
C:\Windows\system32\wininit.exewininit.exe1⤵PID:368
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵PID:492
-
\\?\C:\Windows\system32\wbem\WMIADAP.EXEwmiadap.exe /F /T /R1⤵PID:1208
-
C:\Windows\system32\wbem\wmiprvse.exeC:\Windows\system32\wbem\wmiprvse.exe1⤵PID:1344
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1244
-
C:\Users\Admin\AppData\Local\Temp\28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe"C:\Users\Admin\AppData\Local\Temp\28fb212451001f5bc0f1d5467356705aea7ebc24fa4dc873b5956b981497e5b0.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1640