Cybersecurity researchers have disclosed details of a new campaign dubbed TASK#STOMP that delivers a PowerShell backdoor designed to harvest sensitive data from compromised hosts.
The backdoor “automatically harvests and exfiltrates business documents, watches the filesystem for new files in real time, steals Wi-Fi passwords and clipboard contents, takes screenshots, and accepts arbitrary remote commands through two redundant, token-authenticated C2 servers,” Securonix researchers Akshay Gaikwad and Aaron Beardslee said in a report shared with The Hacker News.
The starting point of the infection chain is the use of “wscript.exe” to execute an encoded Visual Basic Script (VBScript) file staged on the victim’s desktop (“95c9050t66.vbs”). The exact initial access pathway used to deliver the payload is unclear, although it’s possible that it may have been via email-based phishing or social engineering.
By giving it a completely random file name, it’s suspected that the intention may have been to evade file name-based detection mechanisms. The VBScript functions as the orchestrator for establishing persistence on the host using scheduled tasks and launching subsequent stages.
The tasks are given the names Local Credential Manager, Network Audio Service, Windows Display Manager, and Device Credential Handler so as to blend in with regular operating system activity and avoid raising any red flags.
The VBScript installer also sets up a backup persistence method that uses the Windows Startup folder to launch another script payload (“msdiag.vbs”) every time the user logs in to the system. In the next phase, the malware executes PowerShell commands to forcibly terminate previously running instances and ensure there exists only one active session
These strategies, paired with deliberate timestamp modification (aka timestomping), hidden execution, and cleanup behavior, suggest a deliberate effort to get around superficial administrative reviews and complicate forensic analysis. The use of redundant persistence methods guarantees continued execution even if one of them fails or is detected and removed.
“Running the modules as separate processes provides functional separation and operational redundancy: failure or termination of one branch does not immediately remove the other,” Securonix said.
Both the modules communicate with the same C2 infrastructure (“corecloudfileshare[.]xyz” or “attachmentsharingdrive[.]xyz”). Interestingly, the two components incorporate a mutual-watchdog relationship in which “diag_pack.dat” checks if “win_conn.ps1” is running, and restart it if not, and vice versa.
The end goal of the attack is to provide a pathway for continuous document collection, credential and clipboard theft, screenshot capture, redundant C2 communications, and arbitrary code execution, while leveraging an array of techniques to fly under the radar.
Leave a Reply