51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e

Analysis

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

arch:x64arch:x86image:win7-20220812-enlocale:en-usos:windows7-x64system
submitted
06/11/2022, 17:48

Sharing

Copy URL

Twitter E-mail

Report Analysis Logs

General

Target

51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
Size

35KB
MD5

0ed165387ae92b644bca5a821b924de0
SHA1

1bb759fca7db7df1265fb2680e11cba2468be266
SHA256

51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e
SHA512

aaf20c47f8d6991713256aa8c3fff513a6465af19f80151de9cc0376a6ec3b3c8b2fe520a95f5330f06916ab986908bf4b6403a39c51b3f3cb74f6eed529626f
SSDEEP

768:oau+UoFJ4NINSkmfaQJXWi/XNNa8KSzXQn3:XUUJ4Nkmfa6GedXjC

Score

1^/10

Malware Config

Signatures

Suspicious behavior: EnumeratesProcesses 1 IoCs

pid	Process
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe

Suspicious behavior: MapViewOfSection 23 IoCs

pid	Process
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe

Suspicious use of AdjustPrivilegeToken 1 IoCs

description	pid	Process
Token: SeDebugPrivilege	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe

Suspicious use of WriteProcessMemory 64 IoCs

description	pid	Process	procid_target
PID 240 wrote to memory of 372	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	5
PID 240 wrote to memory of 372	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	5
PID 240 wrote to memory of 372	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	5
PID 240 wrote to memory of 372	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	5
PID 240 wrote to memory of 372	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	5
PID 240 wrote to memory of 372	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	5
PID 240 wrote to memory of 372	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	5
PID 240 wrote to memory of 384	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	4
PID 240 wrote to memory of 384	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	4
PID 240 wrote to memory of 384	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	4
PID 240 wrote to memory of 384	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	4
PID 240 wrote to memory of 384	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	4
PID 240 wrote to memory of 384	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	4
PID 240 wrote to memory of 384	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	4
PID 240 wrote to memory of 420	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	3
PID 240 wrote to memory of 420	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	3
PID 240 wrote to memory of 420	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	3
PID 240 wrote to memory of 420	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	3
PID 240 wrote to memory of 420	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	3
PID 240 wrote to memory of 420	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	3
PID 240 wrote to memory of 420	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	3
PID 240 wrote to memory of 464	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	2
PID 240 wrote to memory of 464	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	2
PID 240 wrote to memory of 464	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	2
PID 240 wrote to memory of 464	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	2
PID 240 wrote to memory of 464	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	2
PID 240 wrote to memory of 464	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	2
PID 240 wrote to memory of 464	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	2
PID 240 wrote to memory of 480	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	1
PID 240 wrote to memory of 480	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	1
PID 240 wrote to memory of 480	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	1
PID 240 wrote to memory of 480	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	1
PID 240 wrote to memory of 480	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	1
PID 240 wrote to memory of 480	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	1
PID 240 wrote to memory of 480	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	1
PID 240 wrote to memory of 488	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	8
PID 240 wrote to memory of 488	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	8
PID 240 wrote to memory of 488	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	8
PID 240 wrote to memory of 488	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	8
PID 240 wrote to memory of 488	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	8
PID 240 wrote to memory of 488	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	8
PID 240 wrote to memory of 488	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	8
PID 240 wrote to memory of 596	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	26
PID 240 wrote to memory of 596	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	26
PID 240 wrote to memory of 596	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	26
PID 240 wrote to memory of 596	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	26
PID 240 wrote to memory of 596	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	26
PID 240 wrote to memory of 596	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	26
PID 240 wrote to memory of 596	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	26
PID 240 wrote to memory of 676	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	25
PID 240 wrote to memory of 676	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	25
PID 240 wrote to memory of 676	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	25
PID 240 wrote to memory of 676	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	25
PID 240 wrote to memory of 676	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	25
PID 240 wrote to memory of 676	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	25
PID 240 wrote to memory of 676	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	25
PID 240 wrote to memory of 748	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	24
PID 240 wrote to memory of 748	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	24
PID 240 wrote to memory of 748	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	24
PID 240 wrote to memory of 748	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	24
PID 240 wrote to memory of 748	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	24
PID 240 wrote to memory of 748	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	24
PID 240 wrote to memory of 748	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	24
PID 240 wrote to memory of 800	240	51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe	23

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\svchost.exe
  C:\Windows\system32\svchost.exe -k netsvcs
  2⤵
  PID:884
- - \\?\C:\Windows\system32\wbem\WMIADAP.EXE
    wmiadap.exe /F /T /R
    3⤵
    PID:2028
- C:\Windows\system32\sppsvc.exe
  C:\Windows\system32\sppsvc.exe
  2⤵
  PID:1216
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k LocalServiceAndNoImpersonation
  2⤵
  PID:1812
- C:\Windows\system32\taskhost.exe
  "taskhost.exe"
  2⤵
  PID:1300
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k LocalServiceNoNetwork
  2⤵
  PID:1040
- C:\Windows\System32\spoolsv.exe
  C:\Windows\System32\spoolsv.exe
  2⤵
  PID:456
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k NetworkService
  2⤵
  PID:344
- C:\Windows\system32\svchost.exe
  C:\Windows\system32\svchost.exe -k LocalService
  2⤵
  PID:852
- C:\Windows\System32\svchost.exe
  C:\Windows\System32\svchost.exe -k LocalSystemNetworkRestricted
  2⤵
  PID:800
- C:\Windows\System32\svchost.exe
  C:\Windows\System32\svchost.exe -k LocalServiceNetworkRestricted
  2⤵
  PID:748
- 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:596

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\conhost.exe
  \??\C:\Windows\system32\conhost.exe "-2029095213-945007214-58559832937777695416153269841752292400-229896753-957676167"
  2⤵
  PID:992

C:\Windows\system32\wininit.exe
wininit.exe
1⤵
PID:372
- C:\Windows\system32\lsm.exe
  C:\Windows\system32\lsm.exe
  2⤵
  PID:488

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

C:\Windows\Explorer.EXE
C:\Windows\Explorer.EXE
1⤵
PID:1432
- C:\Users\Admin\AppData\Local\Temp\51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe
  "C:\Users\Admin\AppData\Local\Temp\51e1c540a6231ed47cd6e17f24cf8f5145ef361736a11f66f6522308a5f62e6e.exe"
  2⤵
  - Suspicious behavior: EnumeratesProcesses
  - Suspicious behavior: MapViewOfSection
  - Suspicious use of AdjustPrivilegeToken
  - Suspicious use of WriteProcessMemory
  PID:240

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

Network

MITRE ATT&CK Matrix

Replay Monitor

Loading Replay Monitor...

Downloads

memory/240-54-0x0000000001000000-0x000000000100D000-memory.dmp

Filesize
52KB

Download