It has been reported that Sweden's Government Offices are blocking direct access to ChatGPT from OpenAI and Claude from Anthropic's ...
A Russia-aligned hacking group that researchers had not previously named or documented has been running a systematic intelligence campaign against Ukrainian institutions since at least February 2025, targeting courts, prosecutors, local government bodies, and a major foreign military aid hub, according to a report published Tuesday by cybersecurity firm ESET.
The group, which ESET has labeled Gorbag, operates with a focused mandate: collect documents and credentials that give Russian intelligence visibility into how Ukraine is tracking war crimes, where foreign weapons are arriving, and how effectively Russian strikes are degrading infrastructure near the front lines. ESET said the group "demonstrates precise targeting and operational intent to contribute to Russia's broader strategic goals in the war with Ukraine."
About a quarter of Gorbag's known targets are law enforcement and judicial institutions. ESET researchers say this pattern points to Russian efforts to monitor ongoing war crimes investigations, including which soldiers and officers have been identified, what evidence has been gathered, and which individuals face prosecution. Courts and prosecutors hold precisely that case material, and the Kremlin would have an obvious interest in knowing what investigators know.
Another quarter of the group's victims are local government bodies, concentrated among city councils operating near active fighting. These are not high-profile targets on their own, but they hold something specific: internal damage assessments from Russian airstrikes, including infrastructure repair estimates that have never been publicly released. For Russian military planners evaluating whether strikes are achieving their intended effect, that internal accounting is far more useful than what appears in news reports.
ESET also identified a major transportation hub for foreign military aid as a Gorbag target, one that had been previously struck in Russian airstrikes. Its inclusion in the campaign fits a third intelligence priority the firm attributes to the group: tracking inbound weapons deliveries and mapping the logistics infrastructure that moves military equipment into Ukraine from abroad.
Getting in through the mailbox
Gorbag's entry method is phishing, specifically emails carrying malicious attachments formatted to look like official correspondence about administrative penalties or outstanding taxes. The choice of lure is deliberate. Administrative staff in Ukrainian municipal offices process exactly these kinds of documents, and a notice framed as an overdue government fine is designed to generate urgency without triggering immediate suspicion.
Once a machine is compromised, Gorbag deploys a custom info-stealer ESET calls BeautyStealer. The tool searches the infected computer, removable drives, and connected network shares for files of value, then attempts to erase itself after sending the data out, limiting what forensic investigators would find. The group also uses a remote access tool called Prime ReverseShell, built on publicly available code, that allows operators to issue commands to a compromised machine directly.
What BeautyStealer collects is a combination of credentials and documents. Saved browser passwords, authentication cookies, VPN configuration files, Microsoft Office documents, email archives, and compressed files all fall within scope. That mixture is significant: credentials open doors to systems the attacker has not yet reached, while the documents provide the raw intelligence. ESET notes Gorbag may pass stolen credentials to separate groups for follow-on intrusions, though this relationship has not been confirmed.
An old flaw put to new use
Starting in early 2026, Gorbag added another technique. The group began exploiting CVE-2025-8088, a path traversal vulnerability in WinRAR that lets an attacker write files outside an intended extraction folder by abusing NTFS Alternate Data Streams. The flaw was patched in July 2025, but systems running older versions remained open. WinRAR is used extensively across Ukrainian organizations, making it a consistent point of interest for Russia-aligned actors. RomCom, another Russian-linked group, had exploited the same vulnerability before Gorbag adopted it.
"As long as the war in Ukraine continues, we expect groups such as Gorbag to remain a persistent threat to Ukrainian government, justice, and defense entities." [ESET researchers]
ESET characterizes Gorbag as less technically sophisticated than elite Russian state hacking units. The group shows little interest in deep persistence or careful lateral movement through networks over time. Its posture is transactional: access a machine, harvest whatever is reachable, and exit. That approach may reflect a division of labor inside Russia's intelligence apparatus, where collection-focused units gather raw material and pass it upstream to actors with more specialized capabilities.
The targeting reinforces that reading. Gorbag is not hitting central government ministries or high-value military command networks in Kyiv. It is operating at the administrative layer of a country at war, the city councils, the courts, the logistics checkpoints, the bureaucratic infrastructure that underpins both civilian governance and military operations near the contact line. That is exactly where granular, operational intelligence lives, and exactly where it is least expected to be a target.
The operation has been linked to APT29, a cyberespionage group associated with Russia's Foreign Intelligence Service (SVR). According to cybersecurity researchers, the attackers abused a third-party web analytics service to reach visitors of legitimate websites without requiring them to download suspicious applications or files.
According to Sekoia researchers Amaury-Jacques Garçon and Félix Aime, the campaign relied on three main methods to infect devices. These included compromising legitimate websites, creating fake websites that impersonated well-known organisations, and conducting a supply-chain attack against Plerdy SEO Tracker.
The supply-chain compromise took place between August 27 and September 3, 2026. During this period, attackers injected malicious code into the JavaScript file hosted on Plerdy's infrastructure. Since the analytics script was used by thousands of websites, the compromise potentially exposed a large number of visitors to the malicious code.
The researchers discovered that the attackers also created lookalike websites impersonating organisations in the United States, Ukraine, the Czech Republic and Bulgaria. Some compromised websites were associated with the chemical industry, political organisations and military-related activities.
Once the malicious JavaScript executes, it collects information about the visitor's browser, operating system and device configuration.
For Apple devices, the attackers used the DarkSword exploit kit to target vulnerable iOS versions. Depending on the device, the malware could steal Safari cookies or extract more extensive information, including text messages, WhatsApp and Telegram databases, contacts, call history, photographs, Wi-Fi passwords and iCloud Keychain data.
Android users were targeted through a separate malware payload called AndroSnitch. The attack exploited vulnerabilities in Google Chrome to gain access to the device and collect browser information, including cookies, saved login details and Wi-Fi passwords.
Researchers identified several security vulnerabilities used in the campaign, including CVE-2025-43529, CVE-2026-20700 and CVE-2026-3910. These vulnerabilities allowed attackers to execute malicious code and bypass security protections on vulnerable devices.
Sekoia said the campaign appeared to focus on websites likely to attract strategically important visitors, particularly those connected to military organisations and defence-related industries.
A cyberattack targeting OPSSHIELD's software distribution infrastructure allowed an unidentified attacker to compromise cPGuard updates and deploy a malicious script across customers' Linux servers, harvesting password hashes, SSH keys, database credentials, and other sensitive information.
The incident began on November 2, 2026, when the attacker exploited compromised credentials to access OPSSHIELD's update distribution infrastructure. According to the company's investigation, approximately 2,950 customer servers executed the malicious update, while nearly 7,900 billing portal account records were also exposed.
cPGuard, OPSSHIELD's Linux server security solution, provides malware scanning, firewall management, and attack protection for web hosting environments, including servers running cPanel, DirectAdmin, and Plesk.
Compromised Update Infrastructure Delivered Malicious Script
OPSSHIELD's investigation traced the intrusion to its billing and licensing application. The attacker initially registered a customer account under a false identity on November 1 and requested a free cPGuard trial to examine communications between the software and its licensing infrastructure.
After probing the billing portal and submitting specially crafted requests, the attacker obtained command execution on the company's billing and licensing server. This access enabled the theft of credentials used to distribute software updates.
Between 02:04 and 02:09 UTC on November 2, the attacker uploaded a malicious update using a stolen access key. The compromised versions, ranging from 5.88.12 through 5.88.19, were distributed for approximately 70 minutes and executed with root privileges on servers checking for updates during that period.
OPSSHIELD detected the compromise within 12 hours and subsequently revoked the stolen update key.
Password Hashes and SSH Credentials Targeted
The malicious script collected sensitive system information and transferred it to OPSSHIELD's licensing infrastructure through a compromised account, allowing the attacker to retrieve the uploaded data.
The targeted files included "/etc/shadow" and "/etc/passwd", root's MariaDB/MySQL configuration ("my.cnf"), shell history, and SSH authorization and known-hosts files. The script also accessed root's SSH private keys and cloud storage credentials on some systems.
The "/etc/shadow" file contains password hashes rather than plaintext credentials. However, attackers can attempt offline password cracking against these hashes, particularly when passwords are weak, commonly used, or previously exposed. Database configurations and shell histories may contain credentials and API tokens that are immediately usable without requiring password cracking.
OPSSHIELD initially confirmed that attackers retrieved 32 collected files, each associated with a different customer server. Its subsequent disclosure estimated approximately 2,950 servers executed the malicious update.
The attackers also copied approximately 7,900 billing portal records containing customer names, company information, postal addresses, email addresses, and bcrypt-hashed passwords.
OPSSHIELD Releases Security Updates
The malicious script left several identifiable artifacts, including "cpguard-v58812-i91511.sh", a hidden root shell at "/var/tmp/.cpg91511_sh", and a collection directory at "/var/tmp/.cpg91511", containing the staged archive "loot.tgz".
OPSSHIELD's corrective updates remove the known backdoor and associated malicious files. However, removing these artifacts does not establish that a server was never compromised.
The company initially recommended updating to version 5.88.25 or later. Its subsequent disclosure identified version 5.88.26 as the clean release, which also addresses additional persistence mechanisms.
Administrators should run "cpgcli update --start" and verify the installed version using "cpgcli --version".
For potentially affected systems, OPSSHIELD recommends resetting local account passwords, rotating database credentials, S3 access keys, DigitalOcean tokens, and other exposed secrets. Administrators must also replace root SSH private keys and remove corresponding public keys from systems that previously trusted them.
Customers should additionally reset their OPSSHIELD billing portal passwords and enable two-factor authentication.
OPSSHIELD has also begun revoking its previously deployed support-access keys and rebuilding compromised internal infrastructure. Although the company initially did not recommend routine operating system reinstalls, its updated disclosure confirms that affected customer servers are being rebuilt where necessary.