20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec

Analysis

max time kernel
31s
max time network
46s
platform
windows7_x64
resource
win7-20220812-en
resource tags

arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system
submitted
30/10/2022, 01:29

Sharing

Copy URL Twitter E-mail

Report Analysis Logs

General

Target

20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
Size

41KB
MD5

43eeddc138ddec160004451513592940
SHA1

340ba5f0111618165bbfad9952f6bfde29099251
SHA256

20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec
SHA512

b5804c56bdda10ac0fdd45d7ca7425352f11330b5ec089238b55eadf6ea51346598560e908d725922436f30f878847cf0817ac8eb9f7abc546317977391b21f3
SSDEEP

768:9/vt5FHGA/MNDxWLHMOfpTbALmr46YeAFEuVkEORKdHydh:99/mA/8WLMOfpTsqrSNfVu+Sd

Score

1^/10

Malware Config

Signatures

Suspicious behavior: EnumeratesProcesses 1 IoCs

pid	Process
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe

Suspicious behavior: MapViewOfSection 22 IoCs

pid	Process
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe

Suspicious use of AdjustPrivilegeToken 1 IoCs

description	pid	Process
Token: SeDebugPrivilege	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe

Suspicious use of WriteProcessMemory 64 IoCs

description	pid	Process	procid_target
PID 1668 wrote to memory of 372	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	25
PID 1668 wrote to memory of 372	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	25
PID 1668 wrote to memory of 372	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	25
PID 1668 wrote to memory of 372	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	25
PID 1668 wrote to memory of 372	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	25
PID 1668 wrote to memory of 372	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	25
PID 1668 wrote to memory of 384	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	4
PID 1668 wrote to memory of 384	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	4
PID 1668 wrote to memory of 384	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	4
PID 1668 wrote to memory of 384	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	4
PID 1668 wrote to memory of 384	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	4
PID 1668 wrote to memory of 384	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	4
PID 1668 wrote to memory of 420	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	3
PID 1668 wrote to memory of 420	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	3
PID 1668 wrote to memory of 420	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	3
PID 1668 wrote to memory of 420	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	3
PID 1668 wrote to memory of 420	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	3
PID 1668 wrote to memory of 420	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	3
PID 1668 wrote to memory of 464	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	2
PID 1668 wrote to memory of 464	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	2
PID 1668 wrote to memory of 464	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	2
PID 1668 wrote to memory of 464	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	2
PID 1668 wrote to memory of 464	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	2
PID 1668 wrote to memory of 464	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	2
PID 1668 wrote to memory of 480	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	1
PID 1668 wrote to memory of 480	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	1
PID 1668 wrote to memory of 480	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	1
PID 1668 wrote to memory of 480	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	1
PID 1668 wrote to memory of 480	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	1
PID 1668 wrote to memory of 480	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	1
PID 1668 wrote to memory of 488	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	5
PID 1668 wrote to memory of 488	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	5
PID 1668 wrote to memory of 488	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	5
PID 1668 wrote to memory of 488	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	5
PID 1668 wrote to memory of 488	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	5
PID 1668 wrote to memory of 488	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	5
PID 1668 wrote to memory of 600	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	24
PID 1668 wrote to memory of 600	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	24
PID 1668 wrote to memory of 600	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	24
PID 1668 wrote to memory of 600	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	24
PID 1668 wrote to memory of 600	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	24
PID 1668 wrote to memory of 600	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	24
PID 1668 wrote to memory of 676	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	23
PID 1668 wrote to memory of 676	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	23
PID 1668 wrote to memory of 676	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	23
PID 1668 wrote to memory of 676	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	23
PID 1668 wrote to memory of 676	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	23
PID 1668 wrote to memory of 676	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	23
PID 1668 wrote to memory of 760	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	22
PID 1668 wrote to memory of 760	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	22
PID 1668 wrote to memory of 760	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	22
PID 1668 wrote to memory of 760	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	22
PID 1668 wrote to memory of 760	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	22
PID 1668 wrote to memory of 760	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	22
PID 1668 wrote to memory of 804	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	21
PID 1668 wrote to memory of 804	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	21
PID 1668 wrote to memory of 804	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	21
PID 1668 wrote to memory of 804	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	21
PID 1668 wrote to memory of 804	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	21
PID 1668 wrote to memory of 804	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	21
PID 1668 wrote to memory of 848	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	20
PID 1668 wrote to memory of 848	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	20
PID 1668 wrote to memory of 848	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	20
PID 1668 wrote to memory of 848	1668	20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe	20

C:\Windows\system32\lsass.exe
C:\Windows\system32\lsass.exe
1⤵
PID:480

C:\Windows\system32\services.exe
C:\Windows\system32\services.exe
1⤵
PID:464
- C:\Windows\System32\spoolsv.exe
  C:\Windows\System32\spoolsv.exe
  2⤵
  PID:1028
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation
  2⤵
  PID:980
- C:\Windows\system32\sppsvc.exe
  C:\Windows\system32\sppsvc.exe
  2⤵
  PID:1660
- C:\Windows\system32\taskhost.exe
  "taskhost.exe"
  2⤵
  PID:1140
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k LocalServiceNoNetwork
  2⤵
  PID:1072
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k NetworkService
  2⤵
  PID:324
- - C:\Windows\system32\wininit.exe
    wininit.exe
    3⤵
    PID:372
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k netsvcs
  2⤵
  PID:884
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k LocalService
  2⤵
  PID:848
- C:\Windows\System32\svchost.exe
  C:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted
  2⤵
  PID:804
- C:\Windows\System32\svchost.exe
  C:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted
  2⤵
  PID:760
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k RPCSS
  2⤵
  PID:676
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k DcomLaunch
  2⤵
  PID:600

C:\Windows\system32\winlogon.exe
winlogon.exe
1⤵
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=16
1⤵
PID:384

C:\Windows\system32\lsm.exe
C:\Windows\system32\lsm.exe
1⤵
PID:488

\\?\C:\Windows\system32\wbem\WMIADAP.EXE
wmiadap.exe /F /T /R
1⤵
PID:1676

C:\Windows\system32\wbem\wmiprvse.exe
C:\Windows\system32\wbem\wmiprvse.exe
1⤵
PID:1792

C:\Windows\Explorer.EXE
C:\Windows\Explorer.EXE
1⤵
PID:1256
- C:\Users\Admin\AppData\Local\Temp\20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe
  "C:\Users\Admin\AppData\Local\Temp\20c7d4fef90514ccdd63eadd6aa3cfaebee21d651480fc4ee859e192b57af9ec.exe"
  2⤵
  - Suspicious behavior: EnumeratesProcesses
  - Suspicious behavior: MapViewOfSection
  - Suspicious use of AdjustPrivilegeToken
  - Suspicious use of WriteProcessMemory
  PID:1668

C:\Windows\system32\Dwm.exe
"C:\Windows\system32\Dwm.exe"
1⤵
PID:1208

Network

MITRE ATT&CK Matrix

Replay Monitor

Loading Replay Monitor...

Downloads

memory/1668-54-0x0000000075241000-0x0000000075243000-memory.dmp

Filesize
8KB

Download
memory/1668-55-0x0000000001000000-0x000000000100D000-memory.dmp

Filesize
52KB

Download