On this page (8 sections)
A group known as Bitter, also tracked as TA397, is running an espionage campaign that mixes a custom remote access trojan called PapRAT with utilities that come built into Windows. The research comes from Cara Lin of Fortinet's FortiGuard Labs, published on November 2 and summarized by Infosecurity Magazine.
The named targets are organizations in South Asia, so most website owners are not the intended victims. Still, the campaign is a useful case study for administrators and agencies: one of its three infection chains deployed no traditional malware executable, and Keeper Security's Shane Barney argued that when an intrusion uses trusted system processes, signature-based controls have nothing to alert on.
What happened
Per Infosecurity Magazine, FortiGuard followed the activity over several months. Its high-confidence link to Bitter rests on lure filenames, command-and-control (C2) patterns, file metadata and analysis of the malware itself. The decoy documents were themed around a bilateral meeting request, an ambassador's letter concerning the 11th Belt and Road Summit, and an invitation to a 2026 gala dinner. The coverage does not say which sectors or job roles were hit.
Dark Reading describes Bitter as an India-linked threat group that leverages legitimate Windows functionality in three distinct attack chains, while Infosecurity Magazine calls it a suspected South Asian group. The detailed account in this article comes from a single report, Infosecurity Magazine's, and Dark Reading's short summary adds no independent confirmation.
The three infection chains
The reporting describes three chains. The first uses a shortcut file and Windows tools. The other two deliver PapRAT through MSI packages. The source says PapRAT downloaded WmRAT in the "third chain" but does not map the VHDX or RAR delivery routes to that numbering, so the headings below stay neutral.
The chain with no malware binary
Here the attackers relied on what Windows already provides. A malicious shortcut (LNK) file abused the built-in ftp.exe utility to run scripts and create scheduled tasks, and those tasks used curl to fetch fresh commands from attacker servers. FortiGuard said operators could change their instructions on the server without pushing a new binary. FortiGuard found no PapRAT in this chain: only the shortcut, Windows tools, scripts and scheduled tasks.
The two MSI-delivered PapRAT chains
The other two chains delivered PapRAT through Windows Installer (MSI) packages. In one, the package was hidden with a decoy spreadsheet in a virtual hard disk (VHDX) image. In the other, the package was fetched via an internet shortcut in a RAR archive.
WmRAT
In the third chain, PapRAT downloaded WmRAT, a C++ RAT previously documented by other researchers. FortiGuard cited it as a further indicator linking the campaign to Bitter.
What PapRAT can do
| Build | Disguise and transport | Capabilities |
|---|---|---|
| C++ | Posed as a Microsoft component; beaconed over plaintext HTTP | Eight commands, including remote shell access, file transfers and screenshots |
| Rust (obtained more recently) | Switched to HTTPS | Three more commands: PowerShell execution, pausing and exiting |
The sources do not discuss how the HTTPS switch affects detection. It is plausible that tools inspecting beacon contents would see less, but that is our inference, not a research finding.
Who is realistically exposed
- Organizations in South Asia, the stated focus, plus those in Southeast Asia and South Korea where FortiGuard's telemetry showed activity.
- Staff on Windows endpoints who receive unsolicited shortcuts, disk images, archives or installers, including files themed as meeting requests, summit letters or event invitations.
- Organizations that let users open LNK files, mount disk images or run MSI installers from email or downloads without restriction (our observation, not a research finding).
Nothing in the research suggests web servers or content management systems are being attacked. The risk described is to Windows endpoints, which can include the workstations of people who administer websites.
How to check your exposure
Since one chain involved no PapRAT, searching for the name alone is not enough. Sectigo's Jason Soroko told Infosecurity Magazine that such a search could miss part of the campaign and that deleting the first implant found might not remove the attacker. Hunt for behaviors instead.
This read-only command, run in a Windows Command Prompt, lists scheduled tasks in verbose format. Look for tasks you cannot account for, especially ones that run curl or scripts:
schtasks /query /fo LIST /vThis read-only PowerShell command prints each task's path, name and state so you can compare against a known-good baseline:
Get-ScheduledTask | Select-Object TaskPath, TaskName, StateAlso review endpoint logs for ftp.exe or curl.exe started by a shortcut or script, and for MSI installs that originated from a mounted VHDX image or an extracted RAR archive. These are our suggestions based on the reported chains, not published detection rules.
What to do now
- Handle unexpected LNK files, internet shortcuts, disk images and MSI installers with care, as FortiGuard recommends.
- Our own suggestion: do not open such files from unsolicited email, and confirm unexpected ones with the sender through another channel.
- Audit scheduled tasks on Windows endpoints and investigate any that run scripts or curl without a clear owner (our suggestion, based on the reported first chain).
- Our own suggestion, not a published detection rule: alert when ftp.exe or curl.exe is started by shortcuts, scripts or scheduled tasks on machines where that is not normal.
- Apply least-privilege access and remove standing administrative rights, as Keeper Security's Shane Barney argued in the coverage.
- Tighten limits on native scripting engines where your business allows it, another point Barney raised, so abused built-in tools have less room to run.
- If you find one implant, assume there may be more: check scheduled tasks, scripts and other persistence before declaring a host clean (consistent with Soroko's warning).
- Our own suggestion: brief staff who open external files about lures that look like meeting requests, letters or event invitations.
Detection and monitoring
Barney pointed out that when an intrusion leverages trusted system processes, signature-based controls have nothing to alert on. Watching process launches, task creation and outbound connections from ordinary Windows utilities is a more productive angle, though that is our suggestion rather than something the research prescribes.
If you run websites, keep admin workstations tidy and watch your public infrastructure for unexpected changes. Certificate, DNS and header monitoring such as Webforta Monitor can flag changes on your public sites, though it cannot see inside a compromised workstation. For the limits of outside-in tools, read what outside-in malware detection can and cannot see. If you suspect a compromise, follow website hacked: what to do.
What is still unknown
- No CVE, CVSS score or vendor advisory for this campaign appears in the research.
- The number of victims, the sectors affected and the data stolen have not been reported in the sources reviewed.
- Specific indicators of compromise were not included in the coverage, so consult FortiGuard's original research for those.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
