Analysis
-
max time kernel
11s -
max time network
33s -
platform
windows7_x64 -
resource
win7-20221111-en -
resource tags
arch:x64arch:x86image:win7-20221111-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 18:59
Static task
static1
Behavioral task
behavioral1
Sample
03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe
Resource
win7-20221111-en
Behavioral task
behavioral2
Sample
03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe
Resource
win10v2004-20220812-en
General
-
Target
03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe
-
Size
107KB
-
MD5
52e0791516d8ba8536b9bdb68ed5d980
-
SHA1
8e2170a6eff937eddc0576ddc9d500f52233124a
-
SHA256
03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b
-
SHA512
78f56e1d929e340807531c6a69c41dadea328e61e34f9a8eacfbfaa3c000d98dcafc1d31525fd41fe9524578910fe1637437b5143cdeb62600e4a956c999b93f
-
SSDEEP
1536:RntREC/rMcgEPJV+G57ThjEC0kzJP+V5JwLTUCMe57c9MD3x149bGQMP:JzECTMpuDhjRVJG2XUfeNc9ixObK
Malware Config
Signatures
-
Suspicious behavior: EnumeratesProcesses 1 IoCs
Processes:
03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exepid process 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe -
Suspicious behavior: MapViewOfSection 22 IoCs
Processes:
03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exepid process 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exedescription pid process Token: SeDebugPrivilege 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exedescription pid process target process PID 1780 wrote to memory of 368 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe wininit.exe PID 1780 wrote to memory of 368 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe wininit.exe PID 1780 wrote to memory of 368 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe wininit.exe PID 1780 wrote to memory of 368 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe wininit.exe PID 1780 wrote to memory of 368 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe wininit.exe PID 1780 wrote to memory of 368 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe wininit.exe PID 1780 wrote to memory of 368 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe wininit.exe PID 1780 wrote to memory of 384 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe csrss.exe PID 1780 wrote to memory of 384 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe csrss.exe PID 1780 wrote to memory of 384 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe csrss.exe PID 1780 wrote to memory of 384 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe csrss.exe PID 1780 wrote to memory of 384 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe csrss.exe PID 1780 wrote to memory of 384 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe csrss.exe PID 1780 wrote to memory of 384 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe csrss.exe PID 1780 wrote to memory of 420 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe winlogon.exe PID 1780 wrote to memory of 420 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe winlogon.exe PID 1780 wrote to memory of 420 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe winlogon.exe PID 1780 wrote to memory of 420 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe winlogon.exe PID 1780 wrote to memory of 420 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe winlogon.exe PID 1780 wrote to memory of 420 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe winlogon.exe PID 1780 wrote to memory of 420 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe winlogon.exe PID 1780 wrote to memory of 468 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe services.exe PID 1780 wrote to memory of 468 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe services.exe PID 1780 wrote to memory of 468 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe services.exe PID 1780 wrote to memory of 468 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe services.exe PID 1780 wrote to memory of 468 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe services.exe PID 1780 wrote to memory of 468 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe services.exe PID 1780 wrote to memory of 468 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe services.exe PID 1780 wrote to memory of 476 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsass.exe PID 1780 wrote to memory of 476 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsass.exe PID 1780 wrote to memory of 476 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsass.exe PID 1780 wrote to memory of 476 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsass.exe PID 1780 wrote to memory of 476 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsass.exe PID 1780 wrote to memory of 476 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsass.exe PID 1780 wrote to memory of 476 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsass.exe PID 1780 wrote to memory of 484 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsm.exe PID 1780 wrote to memory of 484 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsm.exe PID 1780 wrote to memory of 484 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsm.exe PID 1780 wrote to memory of 484 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsm.exe PID 1780 wrote to memory of 484 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsm.exe PID 1780 wrote to memory of 484 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsm.exe PID 1780 wrote to memory of 484 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe lsm.exe PID 1780 wrote to memory of 584 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 584 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 584 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 584 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 584 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 584 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 584 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 660 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 660 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 660 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 660 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 660 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 660 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 660 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 736 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 736 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 736 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 736 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 736 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 736 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 736 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe PID 1780 wrote to memory of 804 1780 03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe svchost.exe
Processes
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe1⤵PID:476
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe1⤵PID:468
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted2⤵PID:736
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork2⤵PID:1044
-
C:\Windows\system32\sppsvc.exeC:\Windows\system32\sppsvc.exe2⤵PID:1664
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation2⤵PID:1104
-
C:\Windows\system32\taskhost.exe"taskhost.exe"2⤵PID:1124
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe2⤵PID:308
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService2⤵PID:108
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k netsvcs2⤵PID:864
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalService2⤵PID:832
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted2⤵PID:804
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k RPCSS2⤵PID:660
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch2⤵PID:584
-
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:368
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵PID:484
-
C:\Windows\system32\wbem\wmiprvse.exeC:\Windows\system32\wbem\wmiprvse.exe1⤵PID:1960
-
\\?\C:\Windows\system32\wbem\WMIADAP.EXEwmiadap.exe /F /T /R1⤵PID:1996
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵PID:1252
-
C:\Users\Admin\AppData\Local\Temp\03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe"C:\Users\Admin\AppData\Local\Temp\03dcf6f55e4b7f62de3e217b661bceca2a54e8252f0c84a2a538b874d0709a2b.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:1780
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"1⤵PID:1172