The PapRAT backdoor campaign demonstrates how Bitter combines Windows-native utilities, deceptive files, and staged malware delivery to target South Asian organizations.
FortiGuard Labs identified three infection chains involving LNK files, FTP utilities, VHDX images, MSI installers, and WebDAV.
PapRAT supports remote command execution, file operations, file transfers, and screenshot capture. Its Rust variant adds PowerShell execution.
Enterprises should investigate suspicious scripts, scheduled tasks, installer activity, and process relationships rather than relying exclusively on executable-based detection.
How Did Bitter Use Three Windows Infection Chains to Deploy the PapRAT Backdoor?
The PapRAT backdoor campaign involves three distinct infection chains targeting Windows environments. Bitter uses scripts and scheduled tasks in the first chain, while the other two deploy PapRAT through MSI installers.
FortiGuard Labs attributed the campaign to Bitter with high confidence. Its assessment considered lure filenames, command-and-control (C2) patterns, file metadata, and malware analysis.
BITTER is a suspected South Asian cyberespionage group active since at least 2013. Its historical targets include government, energy, and engineering organizations. MITRE ATT&CK lists T-APT-17 as an associated group.
FortiGuard Labs published its campaign findings on November 2, 2026. The investigation identified three distinct delivery methods.
1. LNK and FTP-based script execution
The first chain abuses a Windows shortcut and the native FTP utility, ftp.exe, to execute local commands. The scripts establish scheduled tasks and contact attacker-controlled infrastructure to retrieve further instructions.
Unlike the other chains, this sequence does not have a documented PapRAT deployment.
2. VHDX-based MSI deployment
The second chain uses a virtual hard disk image containing a shortcut, a decoy Excel spreadsheet, and a hidden MSI installer.
Opening the shortcut launches the spreadsheet while silently running the installer. The MSI contains PapRAT’s executable payload, which masquerades as a Microsoft component.
3. WebDAV-based MSI deployment
The third chain begins with a RAR archive containing an internet shortcut. The shortcut retrieves another LNK file through WebDAV, which leads to MSI execution and PapRAT deployment.
PapRAT subsequently downloads WmRAT, a secondary remote access trojan. This chain combines deceptive shortcuts, remote file retrieval, and custom malware delivery.
Together, these chains demonstrate how Bitter varies its delivery mechanisms. However, only the second and third chains document PapRAT deployment.
What Can the PapRAT Backdoor Do on Compromised Windows Hosts?
PapRAT provides attackers with remote command execution, filesystem operations, file transfers, and screenshot-capture capabilities. FortiGuard identified C++ and Rust implementations, with the Rust variant introducing three additional commands.
The C++ implementation supports eight commands, while the Rust implementation adds three.
MS2: PowerShell execution. SLP: Pauses and resumes command polling. BYE: Terminates the malware process.
The C++ variant communicates with a hardcoded C2 server over plaintext HTTP. It checks for instructions every 10 seconds and identifies victims using their usernames and computer names.
The Rust variant follows a separate implementation path and uses HTTPS-based C2 communication.
These capabilities allow operators to interact with compromised hosts, inspect their filesystems, execute commands, and transfer files. They also provide mechanisms for collecting information from victim environments.
How Does Bitter’s Script-Based Staging Avoid Conventional Malware Delivery?
Bitter’s first infection chain demonstrates how attackers can execute commands and retrieve instructions without repeatedly deploying conventional executable files.
The chain abuses the FTP utility’s ! prefix, which executes a local shell command rather than an FTP instruction. The observed command is:
Plain Text
!more res.ico
FortiGuard reports that this command pipes the contents of res.ico to the Windows command interpreter for execution.
The subsequent scripts create scheduled tasks and use curl to communicate with remote infrastructure. The attacker stores instructions in files such as err.log and talk.log.
FortiGuard reports that err.log masquerades as a system error log. Meanwhile, talk.log contains a Base64-encoded script that retrieves additional instructions from another URL.
One observed staging script collects directory listings, running-process information, installed antivirus details, and mounted-drive information. It saves the collected information to abc.pdf and sends it to the C2 server.
This server-side approach lets the operator change commands without distributing a new executable for every update. FortiGuard specifically notes that this technique avoids PE drops and process injection.
That finding applies to the first infection chain. The other two chains deploy PapRAT through MSI installers containing its executable payload.
This distinction matters for endpoint detection. Monitoring only executable drops and process injection may miss script-driven activity involving built-in utilities and scheduled tasks.
What Should Enterprises Investigate After the PapRAT Backdoor Campaign?
Enterprises investigating a suspected PapRAT backdoor infection should examine the complete execution sequence rather than treating individual file extensions as reliable indicators of compromise.
The three infection chains provide several practical investigation priorities.
1. Inspect suspicious disk images and shortcuts.
Review unexpected VHDX files, LNK shortcuts, and internet shortcuts. Investigate whether mounting an image or opening a shortcut launches unexpected commands, documents, or installers.
2. Examine MSI installer execution.
Review unexplained MSI installations and their associated process activity. Pay particular attention to installers originating from mounted disk images or executing alongside decoy documents.
3. Investigate Windows utilities and scripting activity.
Review unusual execution involving ftp.exe, curl, cmd.exe, and PowerShell. Examine parent processes, command-line arguments, execution context, and associated files.
4. Review scheduled tasks and network activity.
Look for unexpected scheduled tasks that execute scripts or contact external infrastructure. Compare task creation times, execution commands, and associated file locations.
Also investigate unusual outbound communications and unexpected file transfers.
5. Contain confirmed compromises.
When investigation confirms compromise, isolate affected endpoints and preserve relevant forensic evidence. Identify additional payloads, scheduled tasks, and persistence mechanisms before returning devices to service.
These checks address behaviors documented in the campaign. However, an individual artifact does not automatically establish PapRAT infection.
Featured resource
Introduction to Hexnode XDR
Learn how endpoint visibility, cross-endpoint correlation, and centralized incident management help security teams investigate and respond to threats.
How Can Hexnode XDR Support PapRAT-Related Endpoint Investigation?
Hexnode XDR can support investigation and containment on supported Windows endpoints through process analysis, command-line visibility, file quarantine, and endpoint isolation.
The PapRAT campaign makes process context particularly relevant. Its infection chains involve shortcuts, MSI installers, scripting utilities, and subsequent process execution.
Hexnode XDR’s Process Tree displays parent-child execution relationships directly associated with a detected threat lifecycle. It helps technicians investigate related process activity but does not provide a complete view of every process running on the endpoint.
Other relevant capabilities include:
Command-line visibility: Exposes the command string used to execute a process.
File Quarantine: Moves a suspected malicious file into a restricted, encrypted location on the endpoint.
Endpoint Isolation: Restricts endpoint network connectivity while retaining access to the XDR console for investigation.
Kill Process: Terminates the selected process.
Kill Process Tree: Terminates the selected process and every child process it spawned.
For a suspected PapRAT infection, security teams can examine available process context and investigate suspicious installer or scripting activity. They can then quarantine identified malicious files or isolate affected endpoints when appropriate.
These capabilities support endpoint investigation and response. However, Hexnode does not specify PapRAT-specific signature detection or automatic identification of Bitter’s infection chains.
Rebuilding compromised devices, investigating attacker infrastructure, and addressing other persistence mechanisms require additional incident-response procedures.
Hexnode XDR Incidents Tab: From Detection to Resolution
Explore how the Hexnode XDR Incidents tab centralizes threat triage, process investigation, and endpoint containment.
Why Does Bitter’s PapRAT Campaign Challenge Executable-Based Detection?
The PapRAT backdoor campaign demonstrates why endpoint detection must account for script execution, scheduled tasks, and installer activity alongside conventional executable-based threats.
Its three infection chains use different delivery mechanisms. The first abuses FTP-assisted script execution, while the other two deploy PapRAT through MSI installers.
Enterprises should investigate suspicious process relationships, scripts, scheduled tasks, installer activity, and network communications together. Endpoint detection must account for attacker behavior even when a particular stage does not introduce a conventional executable.
For security teams managing Windows fleets, Hexnode XDR provides documented investigation and containment capabilities that can support this response. The priority should remain identifying the execution sequence, validating compromise, and containing affected endpoints.
Strengthen endpoint investigation and response with Hexnode XDR. Explore its process investigation and containment capabilities to support your organization’s endpoint security operations.
Strengthen Endpoint Investigation and Response
Investigate suspicious endpoint activity, examine process relationships, and respond to confirmed threats with Hexnode XDR.
I write at the intersection of technology, process, and people, focusing on explaining complex products with clarity. I break down tools, systems, and workflows without any noise, jargon, or the hype.