Cyber & AI intelligence
Briefs indexed3961
Issues37
Published Mondays07:30 CT
█ Ransomware AGRAM-QILIN-RANSOM 2026-11-20

Agram: Qilin Leaks 2.38 Million Files After Unpaid Ransom

"The Qilin ransomware group has published about 2.38 million files it says it stole from Agram, the Croatian insurance and healthcare group that owns Euroherc, Adriatic osiguranje and a network of clinics and financial…"

The Qilin ransomware group has published about 2.38 million files it says it stole from Agram, the Croatian insurance and healthcare group that owns Euroherc, Adriatic osiguranje and a network of clinics and financial firms in Croatia and the wider region. Croatian outlets Bug.hr and MOJ KRAJ report that the leaked material includes client names, addresses and contact details, medical findings, and photos of identity cards and passports. Croatia's Personal Data Protection Agency (AZOP) has confirmed that Agram notified it of a personal data breach under Article 33 of the GDPR, and its proceedings are ongoing. That confirms a breach took place. It does not confirm the attackers' claims about how much data they took or how they got in. Agram has not commented publicly. MOJ KRAJ reports that affected clients had still not received any notification as of 19 November.

What Happened

Accounts differ on when Qilin first made its claim. According to Istra24, as cited by Sajber Radar, Qilin listed Agram on 9 November 2026 and said it held about 1,258 GB of data across 2.38 million files. The threat monitoring firm DeXpose dates the listing to 16 November and quotes Qilin's usual ultimatum: "The full leak will be published soon, unless a company representative contacts us via the channels provided." Both dates may be right, since leak sites often post a teaser listing first and update it later, but no source settles the question.

Bug.hr and MOJ KRAJ both report that the full set of files went up on Qilin's leak site a few days after the breach was detected, once it was clear no ransom would be paid. Bug.hr notes that paying would not have guaranteed the data stayed private anyway.

Agram did not reply to MOJ KRAJ's questions within three days of receiving them. Sajber Radar notes that nobody has confirmed whether Qilin encrypted any Agram systems, how many people are affected, or which of the group's companies are involved. Agram has not reported any disruption to its operations.

One unrelated item: on 2 November, before any reported breach, shareholders of Agram banka voted to delist the bank's shares from the Zagreb Stock Exchange, citing the cost of staying listed, according to HINA via 24sata. Nothing suggests the two events are connected.

What Was Taken

Sajber Radar cautions against assuming every Agram client or patient is affected. The number of affected people has not been published.

Why It Matters

This leak combines verified identity documents, health records and insurance policy details for the same individuals. That is enough for convincing impersonation, insurance fraud and targeted scams. A caller who knows someone's policy number and recent diagnosis will easily pass as a real insurer or clinic. The data is now public, so anyone can use it, not just Qilin.

Qilin, also known as Agenda, is among the busiest ransomware operations in the world. Acronis's research team counts 179 publicly reported attacks in 2024, more than 1,000 claimed victims in 2025, and more than 900 so far in 2026. It runs as ransomware-as-a-service: affiliates carry out the intrusions using Qilin's platform. Acronis notes the group regularly targets healthcare and that some of its operators have started separate operations, including The Gentlemen and Securotrop.

Defenders should still treat a leak-site claim with caution. CiberLATAM's October review of Latin American incidents found that most Qilin mentions in that region came from extortion sites and intelligence aggregators rather than confirmed forensic findings. In Agram's case, the regulator's acknowledgement and Istra24's review of sample files put this above an unverified claim. The volume and scope are still Qilin's own account.

The Attack Technique

Bug.hr, citing unofficial sources, reports that the intrusion began with a targeted phishing campaign against Agram staff. One employee reportedly clicked a malicious link to a fake version of a popular online shop, which gave the attackers a way into the group's network. MOJ KRAJ reports the same account. Agram has not confirmed it, and no forensic report has been published.

That account matches how Qilin affiliates usually work. Acronis lists phishing, stolen credentials, vulnerable internet-facing systems and abuse of remote-management tools as their usual ways in. Hexastrike's recent investigation of a Qilin attack on a German company gives a useful picture of what follows. The attackers logged in to a VPN that asked only for a password. They took advantage of more than 60 accounts with domain administrator rights and reused local admin passwords. They took over the domain within four days and copied data to cloud storage they controlled before encrypting servers. They also installed a previously unknown backdoor, which Hexastrike calls S5PIVOT, hidden inside a normal Python installation, and wiped Windows event logs on most of the servers they encrypted. Nobody has linked those specific tools to the Agram attack, but this is the sequence Qilin affiliates typically follow after getting in.

What Organizations Should Do

  1. Require phishing-resistant MFA everywhere. Put FIDO2 or passkey-based MFA on VPNs, email and remote access. A stolen password alone should never be enough to get into the network.
  2. Reduce domain admin rights. Check who holds Domain Admin and Enterprise Admin rights. Remove those rights from service and backup accounts, and use LAPS or a similar tool so local admin passwords are unique on every machine.
  3. Watch for large outbound transfers. Alert on bulk uploads to cloud storage and on file-sync tools appearing on servers. In Qilin attacks, the data is stolen before anything is encrypted.
  4. Store logs where attackers can't erase them. Send endpoint and Windows event logs to a central, tamper-resistant store, and deploy EDR on servers as well as laptops.
  5. Separate the most sensitive data. Medical records and scanned ID documents should sit in separate, access-controlled storage with logging, not on general file shares.
  6. Prepare breach notifications in advance. Agram's clients reportedly learned about the leak from the press. Have plain-language notices and a dedicated contact line ready so affected people can be warned quickly. Tell them to verify any call or message that mentions their policy or medical details by contacting the insurer through a number they look up themselves.

Sources: Qilin publishes 2.38 million files stolen from Agram — MOJ KRAJ. | Qilin objavio uzorke podataka Agrama, AZOP potvrdio prijavu povrede... | Hakeri napali koncern Agram osiguranja, objavili ukradene podatke -... | Qilin Strikes Agram Concern in Croatia - DeXpose | Octubre 2026: Qilin, Interseguro — CiberLATAM | Inside Qilin ransomware: ESXi attacks, affiliate networks and doubl... | Agram banka povlači svoje dionice sa Zagrebačke burze 24sata | S5PIVOT – A Python Backconnect Proxy Hidden Inside a Qilin Ransomwa...