Article
Avaddon Ransomware Hits AXA
Arete Analysis
Combating Ransomware
Endpoint Detection and Response

Summary
Avaddon ransomware allegedly attacked European insurance provider AXA shortly after the company announced that it will stop paying ransoms for its clients. Our analysis provides an in-depth look at Avaddon’s tactics and recommended mitigations.
_________________________________________________________________________________________________________________________________
From September 2020 to May 2021, Arete responded to nine Avaddon ransomware engagements across varying industry sectors, including professional services, financial services, healthcare, hospitality, public services, and retail.
During the first week of May, Arete received an FBI Liaison Alert System (FLASH) CU-000145-MW from the FBI Cyber Division. The Australian Cyber Security Center (ACSC) also released an alert about an ongoing Avaddon ransomware campaign.
According to reports, at the beginning of May 2021, AXA (one of Europe’s top five insurers) said it will stop reimbursing people in France who pay ransoms after cybercriminals target them with ransomware. It will also stop writing cyber insurance policies that cover customers for extortion payments to ransomware attackers. This decision is said to have come in response to concerns aired by French justice and cybersecurity officials during a recent senate roundtable in Paris about the global ransomware epidemic.
AXA has now found itself a victim of a ransomware breach. Public reports say that the Avaddon ransomware group has impacted AXA Asia Assistance IT operations in Thailand, Malaysia, Hong Kong, and the Philippines. The group claims to have stolen 3 terabytes of data, including ID cards, passport copies, customer claims, reserved agreements, denied reimbursements, payments to customers, contracts and reports, customer IDs, bank account scanned papers, hospital and doctor reserved material (private investigation for fraud), and customer medical reports, including HIV, hepatitis, STD, and other illness reports. According to reports, the ransomware group said AXA had 240 hours to communicate and cooperate or they would start leaking valuable company documents.
While the juxtaposition of the AXA decision to not pay ransoms for French victims or even write ransomware coverage in France could have motivated the attack, Arete has no information or evidence to link these events. In general, and as disclosed in publicly released news reports, attacks against insurance companies are increasing.
In a recent interview, a member of the REvil ransomware gang was asked if they target organizations with cyber insurance. His response:
“Yes, this is one of the tastiest morsels. Especially to hack the insurers first — to get their customer base and work in a targeted way from there. And after you go through the list, then hit the insurer themselves.”
- "Unknown" REvil Ransomware Representative
In its CU-000145-MW FLASH Alert, the FBI notified of activity by cyber actors using Avaddon ransomware-as-a-service (RaaS) to target U.S. and foreign private sector companies, manufacturing organizations, and healthcare agencies. The alert states that the threat actors:
Have compromised victims through remote access login credentials like remote desktop protocol (RDP) and virtual private network (VPN) with single-factor authentication or improperly configured RDP.
Once they gain access to a victim’s network, they map the network and identify backups for deletion and/or encryption. They use malware that escalates privileges, contains anti-analysis protection code, enables persistence on a victim system, and verifies the victim is not located in the Commonwealth of Independent States (CIS). Their ransomware terminates services and processes related to backup and antivirus running in system memory before encrypting victims’ data.
Encrypt and exfiltrate data from the victim network for extortion, threatening its release in their TOR leak site (avaddongun7rngel.onion) if victims don’t pay the ransom.
Will perform a 5% data leak if the ransom is not paid within three to five days and follow with a full leak of the data stolen if the ransom is not paid.
Announced in January 2021 that they would attack victims who do not pay ransoms with distributed denial-of-service (DDoS) attacks.
Have used the following IPs during RDP connections: 185.216.33.0/24, 45.145.67.0/23, 193.27.229.0/23, 217.8.117.63.
The ACSC report includes some of the following tactics, techniques, and procedures (TTPs):
Phishing and malicious email spam (malspam) campaigns to deliver malicious JavaScript files. These are often low in sophistication, containing a threat suggesting the attached file contains a compromising photo of the victim.
Using “double extortion” techniques as coercion and further pressure to pay a ransom, including:
Threatening to publish the victim’s data via the Avaddon Data Leak Site (DLS): avaddongun7rngel.onion.
Threatening the use of DDoS attacks against the victim (first identified in February 2021).
Identify the default geolocation and system language of the user’s device to determine whether the user will be targeted for attack or not.
Use of Windows Scheduled Task to establish persistence.
The report also includes the following information about countries and sectors affected by this threat:


Statistical Data on Avaddon Ransomware From Arete Metrics
The information listed is based on Avaddon cases investigated by Arete IR since September 2020. Our IR and Data Analytics practices work together to track key data points for every ransomware engagement, and our IR practice tracks data points on the ransomware variant and collects statistics based on handled engagements:
Arete has responded to nine Avaddon breach response engagements since September 2020 in the following sectors: Professional Services | Financial Services | Healthcare | Hospitality | Public Services | Retail
At victim/breach coach/carrier request, Arete negotiated and paid the ransom in four of the nine Avaddon cases. In the remaining five cases, we were able to assist the victim in recovering from backups.
Average ransom demand: US$1,089,375.
Maximum ransom demand: US$4,000,000.
Minimum ransom demand: US$15,000.
We observed data exfiltration in 67% of the incidents.
Phishing emails and RDP were the methods of infection 60% of the time.
During investigations, our incident responders have observed threat actors using RDP to remote into the victim environment. We have seen attackers use Mimikatz, Advanced Port Scanner, Advanced IP Scanner, PsExec, Rclone, Gmer, and svhost.exe. We have also seen exe_[victim_org].exe as the ransomware file names.
Mitigation Measures Recommended By The FBI and ACSC
Back up critical data offline.
Ensure copies of critical data are in the cloud or on an external hard drive or storage device.
Secure your backups and ensure data is not accessible for modification or deletion from the system where the data resides.
Use two-factor authentication with strong passwords, including for remote access services.
Monitor cyber threat reporting regarding the publication of compromised VPN login credentials and change passwords/settings, if applicable.
Regularly change passwords to critical systems.
Keep computers, devices, and applications patched and up to date.
Install and regularly update antivirus or antimalware software on all hosts.
Scan emails and attachments to detect and block malware.
Implement a training program and processes to identify phishing and externally sourced emails.
Back to Blog Posts
Article
Ransomware Trends & Data Insights: October 2026
Although Akira once again emerged as the most active ransomware group in October, overall ransomware and extortion activity was not dominated by any single threat group and instead remained widely distributed among a variety of threat actors, continuing the trend that began around August. Arete identified 31 unique named threat groups in October, the most observed in a single month so far in 2026. In addition to Akira, Settra, and The Gentlemen were among the three most active groups. Several new threat actors also emerged, including BYOD, Kubera Team, QWCrypt, AoQin, Emperador, Osiris Team, and Cinder, with Cinder assessed as possibly part of a threat actor cluster affiliated with the former BlackFile group.

Figure 1. Activity from the top 10 threat groups in October 2026
Throughout the month, analysts at Arete identified several trends behind the threat actors perpetrating cybercrime activities:
PHP2Shell emerged as one of the most significant threats in October, with increasing exploitation of the critical PHP vulnerabilities CVE-2026-109618 and CVE-2026-109619. Other notable vulnerabilities included CVE-2026-104286 affecting FortiMail, and CVE-2026-102255, a critical pre-authentication Server-Side Request Forgery (SSRF) vulnerability affecting SonicWall SMA1000 appliances, highlighting continued threat actor interest in internet-facing enterprise infrastructure.
International law enforcement operations against cybercriminal groups continued to make headlines in October. German authorities announced the arrest of 28-year-old Russian national Vladimir K., suspected of being a senior operator within the Qilin Ransomware-as-a-Service (RaaS) group. Separately, the FBI arrested an individual with suspected links to ShinyHunters, adding to recent law enforcement activity targeting ransomware and extortion groups, including the disruption of KillSec. While Vladimir K.’s arrest has not yet had a notable impact on Qilin’s operational activity, it could provide law enforcement with greater insight into the group’s infrastructure and affiliate network, potentially supporting further disruption efforts.
In early October, “The Luna Moth Files” exposed several files containing alleged internal communications associated with Luna Moth, also known as Silent Ransom Group, revealing insights into the group’s social engineering, data extortion, and victim negotiation operations. However, several claims remain unverified, and the exposure has not notably disrupted the group’s activity thus far, as it was among the top threat actors Arete observed throughout the month.
Sources
Arete Internal
Article
PHP2Shell Exploitation Update
PHP2Shell exploitation activity continues to increase globally, with threat actors targeting the critical PHP remote code execution (RCE) vulnerabilities CVE-2026-109618 and CVE-2026-109619. Researchers recently identified low-volume scanning targeting unpatched or partially mitigated hosts across multiple countries and sectors, and the activity is assessed with moderate confidence as linked to a Korean-speaking operator associated with the Lazarus Group ecosystem. While PHP2Shell (CVE-2026-109618 and CVE-2026-109619) has been patched in PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35, the separately identified CVE-2026-115560 remains unpatched.
What’s Notable and Unique
PHP2Shell vulnerabilities can cause memory corruption due to improper error handling, potentially allowing threat actors to achieve remote code execution on vulnerable PHP servers.
Observed activity includes mass scanning, PHP environment fingerprinting, exploitation attempts, credential and secret theft attempts, and attempts to deliver second-stage payloads and malware.
Successful in-the-wild exploitation has also been reported against honeypots, resulting in shell command execution and the retrieval of additional payloads, demonstrating the potential for follow-on malicious activity.
Mitigations
Organizations should prioritize upgrading internet-facing PHP deployments to patched versions, migrating unsupported PHP versions, updating embedded and containerized PHP runtimes, and implementing available Web Application Firewall (WAF) protections as a temporary defense-in-depth measure.
Analyst Comments
PHP2Shell poses a significant security concern due to its potential to enable unauthenticated remote code execution on vulnerable PHP servers. The progression from mass scanning and exploitation attempts to reports of successful command execution demonstrates the potential for these vulnerabilities to support initial access and subsequent malicious activity. Arete has been closely monitoring PHP2Shell exploitation activity and regularly reviewing and updating related indicators to support detection and blocking efforts. Given the potential for remote exploitation and follow-on activity, PHP2Shell represents a high-priority initial-access risk, emphasizing the importance of timely patching and remediation of affected PHP environments.
Sources
PHP shares mitigation for new RCE vulnerability with no patch
PHP2Shell Exploitation Attempts Continue Amid Suspected N. Korea Global Scanning Activity
PHP2Shell Exploit Attempts Hit Millions as Attackers Try to Deploy Mirai Malware
Advisory: PHP2Shell Vulnerabilities (CVE-2026-109618, CVE-2026-109619)
Article
LiteLLM Supply-Chain Compromise
A software supply-chain attack compromised the release pipeline of LiteLLM, a widely used open-source Python SDK and AI gateway. Attackers leveraged the compromised pipeline on October 21st to publish a malicious LiteLLM version through PyPI and associated Docker registries. The affected release, LiteLLM 1.107.0, contained malware designed to steal credentials, sensitive configuration data, private keys, browser information, and other secrets from compromised systems.
What’s Notable and Unique
The incident is particularly significant because LiteLLM provides a common API for applications to interact with AI models from multiple providers. It is reported that the project had approximately 61,800 GitHub stars and 92 million monthly PyPI downloads.
Rather than modifying the core LiteLLM application source code, the threat actors reportedly tampered with the installation package itself. The malware was designed for broad credential and information theft and encrypted the collected data before uploading it to the attacker's endpoint.
The compromise went beyond one-time credential theft. A malicious Python component launched a detached loader that checked a GitHub-hosted pointer every hour and could download Python code from an external server for execution on the compromised machine. This provided threat actors with a mechanism for subsequent remote code execution.
Analyst Comments
Although the malicious packages were subsequently removed, simply uninstalling or deleting the affected LiteLLM package may not be sufficient, because malicious Python startup files or the detached loader could remain on the host. All exposed information should be rotated immediately, and infected systems should be isolated and rebuilt from clean backups. The most recent clean release prior to the attack, LiteLLM 1.106.2, is currently the suggested recovery version.
Sources
LiteLLM release pipeline hacked to distribute info-stealer malware
LiteLLM 1.107.0 Compromised: Python Startup Hooks Steal Cloud, AI, and Proxy Credentials
The Collector Reaches Beyond Provider API Keys
Article
French Supermarket Cyberattack Highlights Risks in Exposed Refrigeration Controllers
Hundreds of French supermarkets were reportedly affected by a cyberattack in which threat actors compromised internet-connected refrigeration controllers and manipulated temperature and defrost settings, which caused refrigeration units to overheat, resulting in widespread food spoilage and significant financial loss. Impacted refrigeration systems were associated with Danfoss, Copeland, and Dixell, and demonstrated how vulnerabilities in industrial control systems (ICS) can disrupt physical operations without relying on conventional data theft or encryption. The attack also raised concerns about the wider exposure of similar devices, as thousands of refrigeration management interfaces remain accessible from the public internet. The incident highlights the growing risk posed by insecure operational technology (OT), particularly where legacy equipment and remote-management interfaces lack adequate security controls.
What’s Notable and Unique
Researchers identified approximately 2,765 internet-accessible Danfoss AK-SM 800A interfaces during assessment. This figure reflects the scope of that research and should not be interpreted as a current count of exposed devices. Publicly accessible management interfaces increase the opportunity for unauthorized access to industrial equipment.
Research also identified several security flaws in the Danfoss AK-SM 800A platform, including an authentication bypass command injection that could enable remote code execution and a weakness involving web-server configuration changes. Danfoss addressed these findings through firmware updates.
Authorities reported compromised Danfoss AK-SM and AK-SC systems, alongside Copeland XWEB and Dixell XWEB monitoring platforms.
Analyst Comments
The incident demonstrates the business consequences of insufficiently secured industrial infrastructure and reinforces the need to integrate OT security into enterprise risk management. Organizations operating connected facility systems should establish clear ownership of industrial assets, enforce secure remote-access policies, and prioritize remediation based on exposure and operational criticality. The findings also highlight the importance of coordinating security teams with facilities and engineering personnel to ensure that protective measures do not compromise essential operations. A risk-based approach to OT security can help organizations reduce exposure while maintaining the availability and reliability of critical equipment.
Sources
France Supermarket Hacks Expose Risks of Internet-Facing Refrigeration Systems
Freeze the Controller, Defrost the Food: Uncovering Vulnerabilities in Danfoss Refrigeration Controllers
Attackers Heat French Supermarket Fridges Up to 50°C by Hijacking Danfoss Controllers



