Windows管理规范

During the 2016 Ukraine Electric Power Attack, WMI in scripts were used for remote execution and system surveys. ^[1]

Action RAT can use WMI to gather AV products installed on an infected host.^[2]

Agent Tesla has used wmi queries to gather information from the system.^[3]

Akira will leverage COM objects accessed through WMI during execution to evade detection.^[4]

APT29 used WMI to steal credentials and execute backdoors at a future time.^[5]

APT32 used WMI to deploy their tools on remote machines and to gather information about the Outlook process.^[6]

APT41 used WMI in several ways, including for execution of commands via WMIEXEC as well as for persistence via PowerSploit.^[7][8] APT41 has executed files through Windows Management Instrumentation (WMI).^[9]

Aquatic Panda used WMI for lateral movement in victim environments.^[10]

Astaroth uses WMIC to execute payloads. ^[11]

Avaddon uses wmic.exe to delete shadow copies.^[12]

BADHATCH can utilize WMI to collect system information, create new processes, and run malicious PowerShell scripts on a compromised machine.^[13][14]

Bazar can execute a WMI query to gather information about the installed antivirus engine.^[15][16]

Black Basta has used WMI to execute files over the network.^[17]

BlackCat can use wmic.exe to delete shadow copies on compromised networks.^[18]

A BlackEnergy 2 plug-in uses WMI to gather victim host details.^[19]

Blue Mockingbird has used wmic.exe to set environment variables.^[20]

Brute Ratel C4 can use WMI to move laterally.^[21]

Bumblebee can use WMI to gather system information and to spawn processes for code injection.^[22][23][24]

During C0015, the threat actors used wmic and rundll32 to load Cobalt Strike onto a target host.^[25]

During C0018, the threat actors used WMIC to modify administrative settings on both a local and a remote host, likely as part of the first stages for their lateral movement; they also used WMI Provider Host (wmiprvse.exe) to execute a variety of encoded PowerShell scripts using the DownloadString method.^[26][27]

During C0027, Scattered Spider used Windows Management Instrumentation (WMI) to move laterally via Impacket.^[28]

CharmPower can use wmic to gather information from a system.^[29]

Chimera has used WMIC to execute remote commands.^[30][31]

Cinnamon Tempest has used Impacket for lateral movement via WMI.^[32][33]

Cobalt Strike can use WMI to deliver a payload to a remote host.^[34][35][25]

Covenant can utilize WMI to install new Grunt listeners through XSL files or command one-liners.^[36]

CrackMapExec can execute remote commands using Windows Management Instrumentation.^[37]

DarkTortilla can use WMI queries to obtain system information.^[38]

DarkWatchman can use WMI to execute commands.^[39]

DEATHRANSOM has the ability to use WMI to delete volume shadow copies.^[40]

The Deep Panda group is known to utilize WMI for lateral movement.^[41]

The DustySky dropper uses Windows Management Instrumentation to extract information about the operating system and whether an anti-virus is active.^[42]

Earth Lusca used a VBA script to execute WMI.^[43]

EKANS can use Windows Mangement Instrumentation (WMI) calls to execute operations.^[44]

Ember Bear has used WMI execution with password hashes for command execution and lateral movement.^[45]

Emotet has used WMI to execute powershell.exe.^[46]

Empire can use WMI to deliver a payload to a remote host.^[47]

EvilBunny has used WMI to gather information about the system.^[48]

EVILNUM has used the Windows Management Instrumentation (WMI) tool to enumerate infected machines.^[49]

FELIXROOT uses WMI to query the Windows Registry.^[50]

FIN13 has utilized WMI to execute commands and move laterally on compromised Windows machines.^[51][52]

FIN6 has used WMI to automate the remote execution of PowerShell scripts.^[53]

FIN7 has used WMI to install malware on targeted systems.^[54]

FIN8's malicious spearphishing payloads use WMI to launch malware and spawn cmd.exe execution. FIN8 has also used WMIC and the Impacket suite for lateral movement, as well as during and post compromise cleanup activities.^{[55][56][57][58]}

FIVEHANDS can use WMI to delete files on a target machine.^[40][59]

FlawedAmmyy leverages WMI to enumerate anti-virus on the victim.^[60]

During Frankenstein, the threat actors used WMI queries to check if various security applications were running as well as to determine the operating system version.^[61]

FunnyDream can use WMI to open a Windows command shell on a remote machine.^[62]

During FunnyDream, the threat actors used wmiexec.vbs to run remote commands.^[62]

GALLIUM used WMI for execution to assist in lateral movement as well as for installing tools across multiple assets.^[63]

Gamaredon Group has used WMI to execute scripts used for discovery and for determining the C2 IP address.^[64][65]

GravityRAT collects various information via WMI requests, including CPU information in the Win32_Processor entry (Processor ID, Name, Manufacturer and the clock speed).^[66]

HALFBAKED can use WMI queries to gather system information.^[67]

HELLOKITTY can use WMI to delete volume shadow copies.^[40]

HermeticWizard can use WMI to create a new process on a remote machine via C:\windows\system32\cmd.exe /c start C:\windows\system32\\regsvr32.exe /s /iC:\windows\<filename>.dll.^[68]

During HomeLand Justice, threat actors used WMI to modify Windows Defender settings.^[69]

HOPLIGHT has used WMI to recompile the Managed Object Format (MOF) files in the WMI repository.^[70]

IcedID has used WMI to execute binaries.^[71][72]

IMAPLoader uses WMI queries to query system information on victim hosts.^[73]

Impacket's wmiexec module can be used to execute commands through WMI.^[74]

INC Ransom has used WMIC to deploy ransomware.^[75][76][77]

INC Ransomware has the ability to use wmic.exe to spread to multiple endpoints within a compromised environment.^[76][78]

Indrik Spider has used WMIC to execute commands on remote computers.^[79]

jRAT uses WMIC to identify anti-virus products installed on the victim’s machine and to obtain firewall details.^[80]

Kazuar obtains a list of running processes through WMI querying.^[81]

Koadic can use WMI to execute commands.^[82]

KOMPROGO is capable of running WMI queries.^[83]

Latrodectus has used WMI in malicious email infection chains to facilitate the installation of remotely-hosted files.^[84][85]

Lazarus Group has used WMIC for discovery as well as to execute payloads for persistence and lateral movement.^{[86][87][88][89]}

Leviathan has used WMI for execution.^[90]

Lucifer can use WMI to log into remote machines for propagation.^[91]

LunarWeb can use WMI queries for discovery on the victim host.^[92]

Magic Hound has used a tool to run cmd /c wmic computersystem get domain for discovery.^[93]

Maze has used WMI to attempt to delete the shadow volumes on a machine, and to connect a virtual machine to the network domain of the victim organization's network.^[94][95]

menuPass has used a modified version of pentesting script wmiexec.vbs, which logs into a remote machine using WMI.^[96][97][98]

Meteor can use wmic.exe as part of its effort to delete shadow copies.^[99]

Micropsia searches for anti-virus software and firewall products installed on the victim’s machine using WMI.^[100][101]

MoleNet can perform WMI commands on the system.^[102]

Mosquito's installer uses WMI to search for antivirus display names.^[103]

MuddyWater has used malware that leveraged WMI for execution and querying host information.^{[104][105][106][107]}

Mustang Panda has executed PowerShell scripts via WMI.^[108][109]

Naikon has used WMIC.exe for lateral movement.^[110]

Netwalker can use WMI to delete Shadow Volumes.^[111]

NotPetya can use wmic to help propagate itself across a network.^[112][113]

Octopus has used wmic.exe for local discovery information.^[114]

OilRig has used WMI for execution.^[115]

Olympic Destroyer uses WMI to help propagate itself across a network.^[116]

OopsIE uses WMI to perform discovery techniques.^[117]

During Operation Dream Job, Lazarus Group used WMIC to executed a remote XSL script.^[118]

During Operation Wocao, threat actors has used WMI to execute commands.^[119]

PoshC2 has a number of modules that use WMI to execute tasks.^[120]

PowerSploit's Invoke-WmiCommand CodeExecution module uses WMI to execute and retrieve the output from a PowerShell payload.^[121][122]

POWERSTATS can use WMI queries to retrieve data from compromised hosts.^[123][105]

POWRUNER may use WMI when collecting information about a victim.^[124]

ProLock can use WMIC to execute scripts on targeted hosts.^[125]

PyDCrypt has attempted to execute with WMIC.^[126]

QakBot can execute WMI queries to gather information.^[127]

Raspberry Robin can execute via LNK containing a command to run a legitimate executable, such as wmic.exe, to download a malicious Windows Installer (MSI) package.^[128]

RATANKBA uses WMI to perform process monitoring.^[129][130]

Remexi executes received commands with wmic.exe (for WMI commands). ^[131]

REvil can use WMI to monitor for and kill specific processes listed in its configuration file.^[132][133]

RogueRobin uses various WMI queries to check if the sample is running in a sandbox.^[134][135]

Sandworm Team has used Impacket’s WMIexec module for remote code execution and VBScript to run WMI queries.^[1][136]

Sardonic can use WMI to execute PowerShell commands on a compromised machine.^[137]

SharpStage can use WMI for execution.^[102][138]

Sibot has used WMI to discover network connections and configurations. Sibot has also used the Win32_Process class to execute a malicious DLL.^[139]

SILENTTRINITY can use WMI for lateral movement.^[140]

Snip3 can query the WMI class Win32_ComputerSystem to gather information.^[141]

SocGholish has used WMI calls for script execution and system profiling.^[142]

During the SolarWinds Compromise, APT29 used WMI for the remote execution of files for lateral movement.^[143][144]

Stealth Falcon malware gathers system information via Windows Management Instrumentation (WMI).^[145]

StoneDrill has used the WMI command-line (WMIC) utility to run tasks.^[146]

Stuxnet used WMI with an explorer.exe token to execute on a remote share.^[147]

SUNBURST used the WMI query Select * From Win32_SystemDriver to retrieve a driver listing.^[148]

SVCReady can use WMI queries to detect the presence of a virtual machine environment.^[149]

SysUpdate can use WMI for execution on a compromised host.^[150]

TA2541 has used WMI to query targeted systems for security products.^[151]

A Threat Group-3390 tool can use WMI to execute a binary.^[152]

ToddyCat has used WMI to execute scripts for post exploit document collection.^[153]

Ursnif droppers have used WMI classes to execute PowerShell commands.^[154]

Valak can use wmic process call create in a scheduled task to launch plugins and for execution.^[155]

Volt Typhoon has leveraged WMIC for execution, remote system discovery, and to create and use temporary directories.^{[156][157][158][159]}

WannaCry utilizes wmic to delete shadow copies.^{[160][161][162]}

Windshift has used WMI to collect information about target machines.^[163]

Wizard Spider has used WMI and LDAP queries for network discovery and to move laterally. Wizard Spider has also used batch scripts to leverage WMIC to deploy ransomware.^{[164][165][166][167][168]}

One variant of Zebrocy uses WMI queries to gather information.^[169]

On Windows 10, enable Attack Surface Reduction (ASR) rules to block processes created by WMI commands from running. Note: many legitimate tools and applications utilize WMI for command execution. ^[170]

Use application control configured to block execution of wmic.exe if it is not required for a given system or network to prevent potential misuse by adversaries. For example, in Windows 10 and Windows Server 2016 and above, Windows Defender Application Control (WDAC) policy rules may be applied to block the wmic.exe application and to prevent abuse.^[171]

Prevent credential overlap across systems of administrator and privileged accounts. ^[172]

By default, only administrators are allowed to connect remotely using WMI. Restrict other users who are allowed to connect, or disallow all users to connect remotely to WMI.