6d9a57fb6ede0c2878d297c5a4c15c3c39269d6919f7feea70fa7700fb4b2d24

Analysis

max time kernel
179s
max time network
190s
platform
windows10-2004_x64
resource
win10v2004-20221111-en
resource tags

arch:x64arch:x86image:win10v2004-20221111-enlocale:en-usos:windows10-2004-x64system
submitted
03-02-2023 18:56

Sharing

Copy URL

Twitter E-mail

Report Analysis Logs

General

Target

c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
Size

37KB
MD5

f314dc3a42f3125ef12c61b01134476e
SHA1

c6adfedee311fb7abfebdfa53b19e73b9ef39cfb
SHA256

6d9a57fb6ede0c2878d297c5a4c15c3c39269d6919f7feea70fa7700fb4b2d24
SHA512

2ae641c1987357f53608a3d0b7b82b6a1e577d16e63854447ca69275bcf02d6e370cc90eb16897254eb40cba694c4bb44ba6ac3417a41d21c4db2455868cce9c
SSDEEP

768:HevwNCHW1TxGm+N9erXsgJZnt+AcQqt5RYVMUr24v:/NC21T4m+N9qX/vt+WqtfY4

Score

7^/10

Malware Config

Signatures

Uses the VBS compiler for execution 1 TTPs

Scripting
T1064

Suspicious behavior: EnumeratesProcesses 62 IoCs

pid	Process
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe

Suspicious use of AdjustPrivilegeToken 1 IoCs

description	pid	Process
Token: SeDebugPrivilege	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe

Suspicious use of WriteProcessMemory 64 IoCs

description	pid	Process	procid_target
PID 400 wrote to memory of 4000	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	80
PID 400 wrote to memory of 4000	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	80
PID 400 wrote to memory of 440	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	81
PID 400 wrote to memory of 440	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	81
PID 400 wrote to memory of 1188	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	82
PID 400 wrote to memory of 1188	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	82
PID 400 wrote to memory of 4556	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	83
PID 400 wrote to memory of 4556	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	83
PID 400 wrote to memory of 5048	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	84
PID 400 wrote to memory of 5048	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	84
PID 400 wrote to memory of 4812	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	85
PID 400 wrote to memory of 4812	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	85
PID 400 wrote to memory of 4692	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	86
PID 400 wrote to memory of 4692	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	86
PID 400 wrote to memory of 5052	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	87
PID 400 wrote to memory of 5052	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	87
PID 400 wrote to memory of 4860	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	88
PID 400 wrote to memory of 4860	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	88
PID 400 wrote to memory of 3844	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	89
PID 400 wrote to memory of 3844	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	89
PID 400 wrote to memory of 3844	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	89
PID 400 wrote to memory of 5024	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	90
PID 400 wrote to memory of 5024	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	90
PID 400 wrote to memory of 4228	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	91
PID 400 wrote to memory of 4228	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	91
PID 400 wrote to memory of 4028	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	92
PID 400 wrote to memory of 4028	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	92
PID 400 wrote to memory of 1664	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	93
PID 400 wrote to memory of 1664	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	93
PID 400 wrote to memory of 2132	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	94
PID 400 wrote to memory of 2132	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	94
PID 400 wrote to memory of 4620	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	95
PID 400 wrote to memory of 4620	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	95
PID 400 wrote to memory of 1640	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	96
PID 400 wrote to memory of 1640	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	96
PID 400 wrote to memory of 1784	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	97
PID 400 wrote to memory of 1784	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	97
PID 400 wrote to memory of 4120	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	98
PID 400 wrote to memory of 4120	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	98
PID 400 wrote to memory of 4416	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	99
PID 400 wrote to memory of 4416	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	99
PID 400 wrote to memory of 2964	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	100
PID 400 wrote to memory of 2964	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	100
PID 400 wrote to memory of 3160	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	101
PID 400 wrote to memory of 3160	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	101
PID 400 wrote to memory of 964	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	103
PID 400 wrote to memory of 964	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	103
PID 400 wrote to memory of 5032	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	102
PID 400 wrote to memory of 5032	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	102
PID 400 wrote to memory of 2220	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	104
PID 400 wrote to memory of 2220	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	104
PID 400 wrote to memory of 2332	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	106
PID 400 wrote to memory of 2332	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	106
PID 400 wrote to memory of 1980	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	105
PID 400 wrote to memory of 1980	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	105
PID 400 wrote to memory of 1700	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	107
PID 400 wrote to memory of 1700	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	107
PID 400 wrote to memory of 1700	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	107
PID 400 wrote to memory of 1688	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	108
PID 400 wrote to memory of 1688	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	108
PID 400 wrote to memory of 2508	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	109
PID 400 wrote to memory of 2508	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	109
PID 400 wrote to memory of 1780	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	110
PID 400 wrote to memory of 1780	400	c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe	110

C:\Users\Admin\AppData\Local\Temp\c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe
"C:\Users\Admin\AppData\Local\Temp\c6adfedee311fb7abfebdfa53b19e73b9ef39cfb.exe"
1⤵
- Suspicious behavior: EnumeratesProcesses
- Suspicious use of AdjustPrivilegeToken
- Suspicious use of WriteProcessMemory
PID:400
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInUtil.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInUtil.exe"
  2⤵
  PID:4000
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngen.exe"
  2⤵
  PID:440
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_state.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_state.exe"
  2⤵
  PID:1188
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegAsm.exe"
  2⤵
  PID:4556
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\DataSvcUtil.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\DataSvcUtil.exe"
  2⤵
  PID:5048
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AppLaunch.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AppLaunch.exe"
  2⤵
  PID:4812
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ServiceModelReg.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ServiceModelReg.exe"
  2⤵
  PID:4692
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_wp.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_wp.exe"
  2⤵
  PID:5052
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\EdmGen.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\EdmGen.exe"
  2⤵
  PID:4860
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess32.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess32.exe"
  2⤵
  PID:3844
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regbrowsers.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regbrowsers.exe"
  2⤵
  PID:5024
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorsvw.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\mscorsvw.exe"
  2⤵
  PID:4228
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_compiler.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_compiler.exe"
  2⤵
  PID:4028
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\InstallUtil.exe"
  2⤵
  PID:1664
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WsatConfig.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\WsatConfig.exe"
  2⤵
  PID:2132
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\dfsvc.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\dfsvc.exe"
  2⤵
  PID:4620
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\RegSvcs.exe"
  2⤵
  PID:1640
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ComSvcConfig.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ComSvcConfig.exe"
  2⤵
  PID:1784
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\MSBuild.exe"
  2⤵
  PID:4120
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ilasm.exe"
  2⤵
  PID:4416
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\csc.exe"
  2⤵
  PID:2964
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\cvtres.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\cvtres.exe"
  2⤵
  PID:3160
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Workflow.Compiler.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Workflow.Compiler.exe"
  2⤵
  PID:5032
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regsql.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regsql.exe"
  2⤵
  PID:964
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet_regiis.exe"
  2⤵
  PID:2220
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngentask.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\ngentask.exe"
  2⤵
  PID:1980
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\SMSvcHost.exe"
  2⤵
  PID:2332
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\jsc.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\jsc.exe"
  2⤵
  PID:1700
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\AddInProcess.exe"
  2⤵
  PID:1688
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\vbc.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\vbc.exe"
  2⤵
  PID:2508
- C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CasPol.exe
  "C:\Windows\Microsoft.NET\Framework64\v4.0.30319\CasPol.exe"
  2⤵
  PID:1780

Network

MITRE ATT&CK Enterprise v6

Initial Access

Execution

Scripting

T1064

Persistence

Privilege Escalation

Defense Evasion

Scripting

T1064

Credential Access

Discovery

Lateral Movement

Collection

Command and Control

Exfiltration

Impact

Replay Monitor

Loading Replay Monitor...

Downloads

memory/400-132-0x000002345EE00000-0x000002345EE0E000-memory.dmp

Filesize
56KB

Download
memory/400-133-0x00007FF9D48E0000-0x00007FF9D53A1000-memory.dmp

Filesize
10.8MB

Download
memory/400-134-0x000002345F1F0000-0x000002345F1F8000-memory.dmp

Filesize
32KB

Download
memory/400-135-0x00007FF9D48E0000-0x00007FF9D53A1000-memory.dmp

Filesize
10.8MB

Download