Skip to main content
All incident reports
Incident report

Suspected Qilin ransomware member extradited from Japan to Germany

Japan detained a 28-year-old Russian national suspected of being a core member of the Qilin ransomware group and handed him to Germany on 2 October 2026. Germany sought him over a September 2024 attack on a logistics company whose systems were encrypted and which paid more than $160,000 in cryptocurrency.

· First published

The short version

  • The arrest. Japan detained the suspect in Osaka in May and reportedly transferred him to German authorities on 2 October. Japan's National Police Agency has confirmed the extradition.
  • The German case. Germany obtained an arrest warrant over a September 2024 break-in at a logistics company, where data was encrypted and more than $160,000 in cryptocurrency was extorted. The company is not named.
  • The group. Qilin, also known as Agenda, has operated since August 2022 as a ransomware-as-a-service gang that deployed double-extortion attacks. One count puts its victims at more than 2,350 organisations across 62 countries.
  • Continued activity. The group kept listing victims after the May detention, with more than 450 added since June, and it has been tied to exploitation of VPN flaws at Check Point and Palo Alto.

Timeline

DateEvent
August 2022Qilin, also called Agenda, begins operating as a ransomware-as-a-service group.
September 2024A logistics company is hacked, its data encrypted and more than $160,000 in cryptocurrency extorted; Germany later obtains an arrest warrant.
May 2026Japanese authorities detain the 28-year-old Russian national in Osaka after he arrives as a tourist.
2 October 2026The suspect was reportedly handed over to German authorities.
October 2026After Japanese media report the arrest from internal sources, Japan's National Police Agency officially confirms the detention and extradition.

How the suspect was detained and moved

According to Japan's National Police Agency, the man was detained after arriving in the country as a tourist. BleepingComputer, citing a machine translation of the agency's release, says the Japanese Ministry of Justice, the Tokyo High Public Prosecutors Office and Germany worked together to obtain a provisional detention warrant under the Extradition Law for Fugitives and then arrange the handover.

SecurityWeek reported that the suspect had been detained in Osaka in May and was reportedly handed to German authorities on 2 October. Japanese media had reported the arrest from internal sources before the authorities confirmed it publicly.

The German warrant relates to a September 2024 intrusion into a logistics company, whose systems were encrypted and which was extorted of more than $160,000 in cryptocurrency. Neither source names the company, and neither reports what the suspect has said about the allegations.

What Qilin is and who it has hit

Qilin emerged in August 2022 under the name Agenda and became one of the busiest ransomware-as-a-service operations. BleepingComputer describes the gang's pattern as double extortion, with data stolen before encryption.

Named victims include Synnovis, the pathology provider behind disruption at several London hospitals, Nissan, Lee Enterprises, Inotiv, Court Services Victoria and, in August, the US Bureau of Alcohol, Tobacco, Firearms and Explosives. The sources disagree on the Asahi breach: SecurityWeek says personal information of roughly 2 million people was compromised, while BleepingComputer puts the figure at 1.5 million.

On scale, BleepingComputer reports more than 2,350 known victims in 62 countries. SecurityWeek counted 400 victims listed on the group's leak site during 2025, and BleepingComputer says more than 450 were added from June onwards.

The VPN flaws and the group's pace

SecurityWeek reports that in June the group was exploiting a critical authentication bypass, CVE-2026-50751, in Check Point VPN and firewall products. BleepingComputer also links Qilin to exploitation of Check Point VPN zero-days and of known flaws in Palo Alto VPNs.

The detention did not stop the operation. BleepingComputer says the group remained a major ransomware player after the May detention, listing more than 450 victims since June. No source states whether the arrested man's role affected the gang's activity, and no source links his arrest to the VPN exploitation or to any specific listed victim.

What is not known yet

  • Whether the suspect has been formally charged in Germany, what plea he intends, and whether other suspected Qilin members are being sought.
  • The identity of the German logistics company, how much data was taken and how many people were affected.
  • Whether the arrest has changed Qilin's operations; the sources record only that victim listings continued.
  • The true size of the Asahi breach, reported as 1.5 million people by one source and roughly 2 million by another.
  • Whether the suspect took part in the Check Point or Palo Alto VPN exploitation attributed to the group.

What to do

If you run internet-facing VPN or firewall products

  1. Inventory every Check Point VPN or firewall appliance and every Palo Alto VPN reachable from the internet, and record the software version each is running.
  2. Check those versions against the vendors' advisories for CVE-2026-50751 and the Palo Alto flaws, and update the ones affected.
  3. Review authentication and access logs on those appliances for sessions you cannot account for.
  4. Restrict management interfaces to trusted addresses rather than leaving them open to the internet.

If you are reviewing ransomware exposure

  1. Confirm that offline backups restore, since Qilin steals data before encrypting so recovery alone does not end the incident.
  2. Keep logs long enough to reconstruct how an intruder entered and what they accessed.
  3. Agree in advance who monitors for stolen data being published and who handles any notification to affected people.

For everyone else

  1. Do not treat the arrest of one suspected member as a drop in risk: the group's leak-site listings continued after the detention, so keep externally reachable services patched and watched.

Update log

  • First published.

Sources

New incident reports by email

One email a week with the reports published since the last one.

Want us to look at your domain?

Give us one apex domain and we'll send back a written snapshot of what is already visible from outside. No call required.