Analysis
-
max time kernel
47s -
max time network
52s -
platform
windows7_x64 -
resource
win7-20220901-en -
resource tags
arch:x64arch:x86image:win7-20220901-enlocale:en-usos:windows7-x64system -
submitted
23-11-2022 21:10
Static task
static1
Behavioral task
behavioral1
Sample
c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe
Resource
win7-20220901-en
Behavioral task
behavioral2
Sample
c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe
Resource
win10v2004-20221111-en
General
-
Target
c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe
-
Size
388KB
-
MD5
1cb7c67bc6d0570e882295b20d2e07c7
-
SHA1
b715b81428766029deb665904c3d95ddc1c84af1
-
SHA256
c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556
-
SHA512
a6031c5341ddd28a146b0751164df9d7f93f765bb704bfe5e9734ed1c8a8f427d79954666282d73696f2894dacb80103d9e64b2c640dd8883902930515b4d6d8
-
SSDEEP
6144:5/uKKKK/TSoxX/8KtG9RtbHqkLN/rKrI/b:5OnxXlgRtbHn7z
Malware Config
Signatures
-
Suspicious behavior: EnumeratesProcesses 1 IoCs
Processes:
c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exepid process 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe -
Suspicious behavior: MapViewOfSection 21 IoCs
Processes:
c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exepid process 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe -
Suspicious use of AdjustPrivilegeToken 1 IoCs
Processes:
c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exedescription pid process Token: SeDebugPrivilege 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe -
Suspicious use of SetWindowsHookEx 1 IoCs
Processes:
c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exepid process 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe -
Suspicious use of WriteProcessMemory 64 IoCs
Processes:
c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exedescription pid process target process PID 1380 wrote to memory of 372 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe wininit.exe PID 1380 wrote to memory of 372 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe wininit.exe PID 1380 wrote to memory of 372 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe wininit.exe PID 1380 wrote to memory of 372 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe wininit.exe PID 1380 wrote to memory of 372 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe wininit.exe PID 1380 wrote to memory of 372 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe wininit.exe PID 1380 wrote to memory of 384 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe csrss.exe PID 1380 wrote to memory of 384 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe csrss.exe PID 1380 wrote to memory of 384 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe csrss.exe PID 1380 wrote to memory of 384 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe csrss.exe PID 1380 wrote to memory of 384 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe csrss.exe PID 1380 wrote to memory of 384 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe csrss.exe PID 1380 wrote to memory of 420 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe winlogon.exe PID 1380 wrote to memory of 420 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe winlogon.exe PID 1380 wrote to memory of 420 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe winlogon.exe PID 1380 wrote to memory of 420 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe winlogon.exe PID 1380 wrote to memory of 420 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe winlogon.exe PID 1380 wrote to memory of 420 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe winlogon.exe PID 1380 wrote to memory of 464 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe services.exe PID 1380 wrote to memory of 464 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe services.exe PID 1380 wrote to memory of 464 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe services.exe PID 1380 wrote to memory of 464 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe services.exe PID 1380 wrote to memory of 464 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe services.exe PID 1380 wrote to memory of 464 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe services.exe PID 1380 wrote to memory of 480 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsass.exe PID 1380 wrote to memory of 480 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsass.exe PID 1380 wrote to memory of 480 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsass.exe PID 1380 wrote to memory of 480 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsass.exe PID 1380 wrote to memory of 480 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsass.exe PID 1380 wrote to memory of 480 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsass.exe PID 1380 wrote to memory of 488 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsm.exe PID 1380 wrote to memory of 488 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsm.exe PID 1380 wrote to memory of 488 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsm.exe PID 1380 wrote to memory of 488 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsm.exe PID 1380 wrote to memory of 488 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsm.exe PID 1380 wrote to memory of 488 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe lsm.exe PID 1380 wrote to memory of 584 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 584 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 584 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 584 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 584 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 584 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 660 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 660 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 660 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 660 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 660 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 660 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 724 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 724 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 724 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 724 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 724 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 724 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 792 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 792 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 792 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 792 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 792 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 792 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 832 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 832 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 832 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe PID 1380 wrote to memory of 832 1380 c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe svchost.exe
Processes
-
C:\Windows\system32\lsass.exeC:\Windows\system32\lsass.exe1⤵
-
C:\Windows\system32\services.exeC:\Windows\system32\services.exe1⤵
-
C:\Windows\system32\sppsvc.exeC:\Windows\system32\sppsvc.exe2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalServiceNoNetwork2⤵
-
C:\Windows\system32\taskhost.exe"taskhost.exe"2⤵
-
C:\Windows\System32\spoolsv.exeC:\Windows\System32\spoolsv.exe2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k NetworkService2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k netsvcs2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k LocalService2⤵
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted2⤵
-
C:\Windows\System32\svchost.exeC:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k RPCSS2⤵
-
C:\Windows\system32\svchost.exeC:\Windows\system32\svchost.exe -k DcomLaunch2⤵
-
C:\Windows\system32\winlogon.exewinlogon.exe1⤵
-
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⤵
-
C:\Windows\system32\wininit.exewininit.exe1⤵
-
C:\Windows\system32\lsm.exeC:\Windows\system32\lsm.exe2⤵
-
\\?\C:\Windows\system32\wbem\WMIADAP.EXEwmiadap.exe /F /T /R1⤵
-
C:\Windows\Explorer.EXEC:\Windows\Explorer.EXE1⤵
-
C:\Users\Admin\AppData\Local\Temp\c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe"C:\Users\Admin\AppData\Local\Temp\c0ee3ebb8b64b69a6d6da3d8371c969484e1d1f2af430ec7fbc93ab691e5c556.exe"2⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious behavior: MapViewOfSection
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of SetWindowsHookEx
- Suspicious use of WriteProcessMemory
-
C:\Windows\system32\Dwm.exe"C:\Windows\system32\Dwm.exe"1⤵
Network
MITRE ATT&CK Matrix
Replay Monitor
Loading Replay Monitor...
Downloads
-
memory/1380-56-0x0000000000400000-0x0000000000463000-memory.dmpFilesize
396KB