Microsoft Removes WMIC from Windows 11 After Years of Abuse as LOLBIN by Ransomware and Attackers
Microsoft has started the final removal of the legacy command-line utility WMIC from Windows 11. The tool is already missing from new installations of versions 24H2 and 25H2, is no longer offered as an optional component, and has disappeared from the latest beta builds of the operating system.
WMIC allowed administrators to manage Windows Management Instrumentation through text commands, retrieving information about hardware, processes, services, and security software while also executing administrative operations. The core WMI technology itself remains intact; only the old command-line interface has been retired.
Microsoft has been preparing this deprecation for years. WMIC was first marked as deprecated in Windows Server 2012, then again in Windows 10 21H1. In Windows 11 22H2 it was moved to optional components, later disabled by default, and is now being fully removed.
The decision stems not only from the tool's age but also from its widespread abuse as a LOLBIN. Attackers have long used the signed Microsoft binary instead of deploying suspicious executables. Ransomware groups have employed WMIC to delete shadow copies, preventing victims from restoring encrypted data. Other threat actors have used it to discover installed security products, disable them, or add exclusions to Microsoft Defender.
Administrators are advised to transition to PowerShell, the COM API for WMI, .NET libraries, and contemporary scripting languages. Existing scripts that rely on WMIC commands will need to be rewritten after the update, or automation workflows will stop functioning.
The change reduces the number of built-in tools available to attackers but also removes a familiar utility from the toolkit of system administrators.
Related articles
uCreator Spyware Infiltrates Modified Telegram, WeChat and GCash Builds on Android
Security researcher Ovi has published a detailed analysis of uCreator, also known as YingGai, a commercial Android spyware platform designed for surveillance and remote app control. The malware intercepts messages, verification codes and account data directly inside legitimate applications without requiring root privileges. Infection vectors include tampered Telegram, WeChat and GCash APKs distributed through unofficial sources, as well as the Onion Box container that launches the target app inside a controlled environment. Once active, uCreator hooks into the host process, reads Telegram’s local message database through client interfaces, captures two-factor authentication passwords and hides its own session from the user. The operation is supported by cloud-based command panels and exposed GitLab repositories that revealed server-side code and development history. Compatibility problems have been noted on Android 17, and the total number of victims remains unknown.
Researchers Deploy Cowrie Honeypot Disguised as NVIDIA H100 Server to Study SSH Botnet Tactics
A cybersecurity team set up a realistic Cowrie honeypot on a fake server equipped with four NVIDIA H100 GPUs, 128 AMD EPYC cores, and terabytes of storage to observe what SSH brute-force bots actually do after gaining access. The trap used a custom StickyAuth module that allowed entry only after several failed attempts and locked in the successful credential pair per IP address. Over the first 12.5 hours the system recorded 1,846 connections from 126 unique IPs, 175 successful logins, and 1,524 commands executed, with the majority of activity traced to a single botnet linked to the Outlaw group. The attackers deployed SSH keys signed mdrfckr, changed the root password, killed competing processes, installed cron jobs, and downloaded a mining archive called dota3 containing an IRC backdoor and its own SSH scanner. The researchers also identified three realism issues in the base Cowrie setup—limited grep flags, outdated filesystem paths in Debian 12, and inconsistent hostname reporting—and patched them to keep sophisticated bots engaged longer. An auxiliary LLM service later summarized each session in Telegram for easier analysis.
Hirudo Android Banking Trojan Uninstalls Legitimate Bank Apps and Installs Attacker-Controlled Fakes
Researchers at ThreatFabric have detailed Hirudo, a sophisticated Android banking trojan that also serves as a remote access tool and replaces genuine bank applications with attacker-controlled copies. The malware spreads through decoy apps themed around shopping, adult video, and short series, including Shopora, 1V1 X, ZoyaTV, and KoiShort. Once installed, it uses accessibility services to detect target banking apps, verify their signatures, display a fake update prompt, and force uninstallation of the real application before installing a malicious replica signed with a publicly known test key. The trojan employs components from the open-source YAHFA and Dobby projects to intercept signature checks, hide accessibility services, bypass screenshot restrictions, and forward Play Integrity attestations to the attacker’s server. Eight ready-made replicas target seven Indonesian banks, while credential theft focuses on users in China, India, Mexico, Morocco, and Thailand. Server logs collected in August 2026 contained thousands of credentials, device data, and financial profiles, with the attestation key set confirmed as publicly leaked and partially revoked by Google.
Over 300 Tor Exit Nodes Hijacked to Intercept SSH Passwords and Deploy Ebury Backdoor
Attackers compromised hundreds of Tor exit nodes and repurposed them to perform man-in-the-middle attacks against SSH connections. Instead of reaching the intended server, users were redirected to attacker-controlled infrastructure where they could be tricked into accepting a forged host key and revealing their credentials. Researcher kaba identified 333 malicious exit nodes routing traffic through the same 12 interception servers after noticing an unexpected host-key warning on October 2. The campaign also attempted to install the Ebury Linux backdoor designed to steal authentication data. The Tor Project confirmed that operators' servers had their configurations altered and some middle relays were converted into exit nodes. The initial access vector remains unknown, but the activity window was limited to October 1-5. Users who connected via Tor during this period, accepted an unfamiliar key, and entered a password should treat their credentials as compromised.