Bitter Hackers Deploy New PapRAT Backdoor in Cyberespionage Campaign Targeting South Asia
PapRAT is malware built to give attackers remote control of an infected Windows computer. That matters because it combines surveillance, file handling, and command execution in one tool. Fortinet observed both C++ and Rust implementations used by Bitter. The malware supports eight commands. These include remote shell access, directory listing, file deletion, arbitrary file execution, drive enumeration, screenshots, uploads, and downloads. The Rust variant adds PowerShell execution, sleeping and polling, and process termination. This gives an operator several ways to inspect and manage a compromised system. PapRAT was delivered through MSI installers in Bitter’s campaigns. In one chain, it also dropped WmRAT, another malware linked to Bitter. The article does not quantify how many computers were infected, but it shows that Bitter continues refining custom tools to maintain access. Monitoring installer activity and unusual command behavior is therefore important.
What is PapRAT, and what kinds of control can it give an attacker over an infected computer?
PapRAT is malware built to give attackers remote control of an infected Windows computer. That matters because it combines surveillance, file handling, and command execution in one tool. Fortinet observed both C++ and Rust implementations used by Bitter.
The malware supports eight commands. These include remote shell access, directory listing, file deletion, arbitrary file execution, drive enumeration, screenshots, uploads, and downloads. The Rust variant adds PowerShell execution, sleeping and polling, and process termination. This gives an operator several ways to inspect and manage a compromised system.
PapRAT was delivered through MSI installers in Bitter’s campaigns. In one chain, it also dropped WmRAT, another malware linked to Bitter. The article does not quantify how many computers were infected, but it shows that Bitter continues refining custom tools to maintain access. Monitoring installer activity and unusual command behavior is therefore important.
How many different infection chains did Bitter use, and what legitimate-looking Windows files or tools did they exploit?
Bitter used three infection chains to deliver PapRAT. This variety matters because each route can make malicious activity look like normal file opening, downloading, or software installation. The campaign used familiar Windows formats and utilities rather than relying on one delivery method.
One chain used a Windows Shortcut, or LNK, to abuse ftp.exe, run scripts, and create scheduled tasks. Another hid an LNK inside a VHDX disk image, opening a lure Excel spreadsheet while an MSI installer ran in the background. The third used a URL shortcut to fetch an LNK through WebDAV, leading to an MSI installer. A script also downloaded an MSI with curl.
These chains show how the actor combined files, scripts, and installers. The article highlights unexpected LNK files, URL shortcuts, disk images, and MSI packages as items requiring caution, especially in unsolicited messages.
Who is Bitter, and why would a cyberespionage group target organizations in South Asia?
Bitter is a cyberespionage group associated with the names APT-C-08, APT-Q-37, Hazy Tiger, Orange Yali, T-APT-17, and TA397. The group has been observed targeting organizations in South Asia with PapRAT. Its activity is presented as espionage because it seeks access, reconnaissance, command execution, and data movement.
The campaign collected information such as directory and task lists, folders on the Desktop, Documents, and Downloads, installed antivirus products, and mounted drives. PapRAT then offered remote control, screenshots, uploads, downloads, and command execution. These capabilities could support continued access and information gathering.
The source does not explain Bitter’s specific objectives, victims’ industries, or why South Asian organizations were chosen. It only establishes the region targeted and the group’s continuing effort to refine its custom arsenal. Any more specific motivation would go beyond the stated facts.
What information did the attackers collect before deploying or using PapRAT?
The attackers first gathered reconnaissance to understand the infected computer and its environment. They collected directory and task lists, information from the Desktop, Documents, and Downloads folders, installed antivirus product data, and mounted drives. This matters because it gives the operator a picture of available files, defenses, and connected storage.
The living-off-the-land script ran commands from a remote server. It saved the gathered information as abc.pdf, exfiltrated that file with curl, and then deleted it from the host. A second script version retrieved talk.log, whose Base64-encoded content provided more instructions and PowerShell commands.
This reconnaissance happened alongside the campaign’s delivery and remote-control activity. The exact timing relative to every PapRAT deployment is not fully specified, but the article presents it as part of the attack process. It shows why unusual scripting, file staging, and outbound transfers deserve attention.
What can happen to an organization after PapRAT gives attackers remote shell access, file-transfer abilities, screenshots, and PowerShell execution?
PapRAT gives an operator practical control over an infected computer. Remote shell access can run commands, while file uploads and downloads move data in either direction. Screenshots can reveal what is displayed, and directory or drive enumeration helps locate information. PowerShell execution in the Rust version expands the available command options.
For example, the malware can list directories, delete files, execute an arbitrary file, capture a screenshot, upload local files, or download new ones. Its commands are labeled MSG, FDD, DEL, RUN, GDR, SS1, UPP, and DWW. The Rust version adds MS2 for PowerShell, SLP for sleeping and polling, and BYE for termination.
The article does not describe a specific business impact or confirmed theft beyond the collected reconnaissance. It does show the potential for sustained access, surveillance, file manipulation, and further instructions. Organizations should monitor these behaviors, not only known malware names.
Why does using trusted tools such as ftp.exe, curl, PowerShell, scheduled tasks, and MSI installers make this campaign harder to detect?
Living-off-the-land attacks use tools already present on a computer. That can blur the difference between attacker activity and ordinary administration. In this campaign, ftp.exe, curl, PowerShell, scheduled tasks, and MSI installers performed parts of the infection, staging, persistence, or command process.
For example, a Shortcut abused ftp.exe to run scripts and create scheduled tasks. Another script used curl to download an MSI and later exfiltrate abc.pdf. A Base64-encoded script supplied PowerShell instructions from a server. The staging model let attackers change commands server-side without pushing a new binary.
This approach can reduce obvious indicators such as new executable files or process injection. Fortinet said it avoids PE drops and process injection that some security appliances could detect more easily. Detection therefore needs to connect scripting, scheduled-task creation, installer activity, unusual shortcuts, and network behavior.
What is a command-and-control server, and how does it let malware receive instructions and send stolen data?
A command-and-control, or C2, server is a remote system used by an attacker to communicate with malware. It can provide instructions and receive information from compromised computers. In this campaign, C2 communication helped Bitter operate scripts and PapRAT after delivery.
The scripts contacted remote servers to collect directory and task information, inspect user folders, identify antivirus products, and list mounted drives. That information was saved as abc.pdf and sent back with curl before being deleted. PapRAT also supported uploads to one C2 server and downloads from it. Another server supplied a file containing encoded PowerShell instructions.
This arrangement gives an operator flexibility because instructions can change without replacing the malware binary. The article describes commands being updated server-side and staged payloads being retrieved when needed. It does not state the servers’ physical locations or how many systems connected to them.
This brief was written by AI from the original reporting and checked by other models. Names, figures and quotes come from the source; read it for full context.
Read more in the JupiteX app
Pulse is free. New stories every 4 hours, each one broken into the questions that explain it.
Or read more news on the web