Lufthansa flight LH717 from Tokyo landed in Frankfurt with a prisoner aboard. The 28-year-old Russian national had spent four months in Japanese custody before his October 2 transfer, ever since police detained him at an Osaka hotel during a holiday with his girlfriend. German investigators know him as "Snake." They allege he is a core member and central software developer of REVENANT SPIDER (aka Qilin, Agenda), one of the most prolific ransomware-as-a-service operations of the past two years. Japan had its own stake in the case. Qilin claimed the 2025 attack on Asahi Group, one of the breaches I tracked in Japan's accelerating breach wave.
Forty days later, Brian Krebs named a different man. According to KrebsOnSecurity, the persona "Haise," which fronted the Qilin affiliate program on the RAMP forum from 2022, belongs to Aleksey Mikhailovich Yakovtsev, 36, of St. Petersburg. Airline records reviewed for the investigation contain domestic flights between St. Petersburg, Murmansk, and Sochi. They contain no record of foreign air travel.
Snake crossed a border and entered German custody. Yakovtsev, if Krebs is right, appears to have kept his travel inside Russia. Western enforcement can arrest the first and expose the second. Qilin kept operating after the arrest, and nothing yet suggests the naming will stop it.
Operation Timeline
Trace the events, turning points, and connections behind the analysis.
Qilin, Haise, and Snake Timeline
Key events behind the Qilin leadership exposure, from the first trace of the Haise identity in 2018 to the KrebsOnSecurity identification in November 2026.
View Timeline Hide Timeline
-
2018 to 2019
-
2020 to 2023
-
June 2022
-
February 2024
-
May 2024
-
June 2024
-
Mid-2024
-
July 2024
-
September 2024
-
October 2024
-
March 2025
-
May to June 2025
-
June 2025
-
July 22, 2025
-
September to October 2025
-
October 2025
-
Late 2025
-
January 2026
-
January 2026
-
April to September 2026
-
May 26, 2026
-
June 10, 2026
-
June and July 2026
-
August 2026
-
October 2, 2026
-
On or before November 6, 2026
-
November 11, 2026
Chain From RAMP to Gosuslugi
The attribution runs through a series of links, each drawn from commercial threat intelligence or leaked Russian data. Intel 471 records show RAMP approved the Haise membership application in mid-2022, months before Qilin, then branded Agenda, surfaced publicly. Direct messages tied to that approval refer to the applicant by the Telegram username "Alexbigboss44."
Intel 471 then matched the same Telegram handle to "Rjun," an account active on the Exploit and XSS forums in 2020. Flashpoint profiles that account as a broker trading in stolen logs, traffic, and corporate access, including bulk purchases of compromised Facebook and Google Ads accounts for fraudulent advertising and gambling schemes. Rjun also registered on the Darkmarket, Verified, and Zloy forums with a Russian webmail address.
SpyCloud recovered a password for that address containing the Rjun alias itself. Constella Intelligence matched the address to a dataset attributed to Gosuslugi, the Russian state services portal, and reportedly exposed in late 2025. Those records name Yakovtsev. A second thread reaches the same name. Flashpoint tied Haise to a persistent Telegram user identifier with more than 5,000 messages since 2018, and Constella linked that identifier to a phone number and further email accounts, one of them built on Yakovtsev's name and birth year. Reporting on the investigation attributes the phone number to Yakovtsev's sister.
IntelHawk, an identity analysis platform applying stylometry to historical usernames, privately reached the same conclusion. IntelHawk's Leo Bogod describes a progression from carding and traffic arbitrage in 2018 and 2019 to malware, botnets, and payment infrastructure from 2020 to 2023. Russian education records cited by Krebs show a master's degree in computing.
Krebs was not first. On or before November 6, the anonymous Telegram leaker GangExposed published a near-identical chain naming a Russian national as Haise. SOCRadar notes the GangExposed version anchors its first link on the order of names in RAMP approval records rather than a unique identifier, a weakness the Krebs version addresses with direct messages and a persistent Telegram identifier.
Krebs credits both GangExposed and IntelHawk. The investigations converge on one man, although their evidence is not fully independent. GangExposed, IntelHawk, and the commercial providers may draw from overlapping forum archives and leaked identity datasets. Agreement strengthens the attribution only where their underlying evidence differs. Yakovtsev did not answer Krebs by phone or email. No government has charged, sanctioned, or publicly named him.
I assess with moderate confidence the Haise persona and the Rjun and Alexbigboss44 accounts share one controller, and with moderate confidence that controller is Yakovtsev.
Weak Links Worth Testing
Every link above depends on data never meant for publication, and none of it comes from a court record. Commercial breach data and leaked state registries have become a foundation of modern cyber crime attribution, yet they carry known failure modes. Four hypotheses deserve a hearing before anyone treats the identification as settled, because attribution is a confidence game even when the data looks conclusive.
Hypothesis 1, Krebs Has the Right Man
The strongest evidence is the persistent Telegram user identifier. A Telegram username can change, while the numeric identifier persists with the account. Flashpoint ties that account to Haise across six years of messages, although the identifier alone cannot prove one person controlled it throughout the period. The identifier links to a phone number, the phone number links to family records, and an email address on the same number carries Yakovtsev's own name. Two separately published chains, from Krebs and from GangExposed, reach the same person, even if parts of their data overlap. This hypothesis best fits the available evidence.
Hypothesis 2, Haise Is a Seat and Not a Person
Ransomware administrator personas are roles, and roles get shared, sold, or handed off. German investigators describe an eight-person core with three principal figures besides Snake, all believed to be in Russia. A second administrator persona, "XORacle," surfaced in a fake Europol bounty post Europol itself called a scam. Yakovtsev could have opened the Haise account in 2022 and still share control of the program with others in 2026.
Persona and alias sprawl of this kind is why threat actor naming is a hall of mirrors. Under this hypothesis, Krebs identifies a founder or one administrator rather than the sole leader, and Snake's arrest becomes one quarter of the leadership problem rather than a side story.
Hypothesis 3, A Borrowed Identity
The phone number belongs to Yakovtsev's sister, by the investigation's own account. Cyber criminals can register accounts with relatives' details, purchased SIM cards, or identities taken from leaked state databases. A careful actor could plant a family member's identity under a persona to deflect attention. The six-year trail weighs against deliberate planting because it would require a long-lived deception predating Qilin without a demonstrated payoff.
The provenance of the Gosuslugi data adds a second weakness. Krebs describes the portal as reportedly breached in late 2025, exposing more than 20 million records, but no public source identifies who took the data or how it circulated, and a leaked state registry carries no chain of custody. Anyone able to edit a leaked record before redistribution could steer an attribution. The evidence weighs against this hypothesis without excluding it.
Hypothesis 4, An Engineered Exposure
The timing invites a harder question. The FBI seized RAMP's public domains in January 2026. The public record does not establish whether investigators obtained the forum database or private messages. If they did, those records would overlap with the data anchoring the first link in this attribution chain.
German investigators had infiltrated Qilin under Operation Albus since mid-2024. GangExposed's prior target, Conti and TrickBot leader "Stern," was publicly named by the German Federal Criminal Police Office within weeks of the leaker's own disclosure. Researchers suspect GangExposed is a former insider settling scores, the same insider dynamic I tracked as ShinyHunters members began talking. An alternative fits the same facts, namely a channel for laundering identifications law enforcement cannot yet publish under its own name. No evidence proves this, and the leaker's anonymity makes it unfalsifiable for now. Analysts should hold it open rather than dismiss it.
One in Custody, One Out of Reach
Snake and Haise are not competing answers to one question. German authorities identify Snake as a developer receiving a substantial share of ransom proceeds, wanted for a September 2024 attack on a North Rhine-Westphalia logistics company with a US$165,000 bitcoin demand. North Rhine-Westphalia Interior Minister Herbert Reul called the arrest the biggest blow German investigators have struck against cyber crime, consistent with the hard line I examined when Berlin refused to pay VICE SPIDER. No public reporting links Snake to the Haise persona, and the eight-year age gap rules out Snake and Yakovtsev being one person.
The German figures frame the scale. German investigators attribute almost 4,000 attacks worldwide since 2024 to Qilin affiliates, with ransom demands approaching US$3 billion and more than US$140 million paid. Germany alone accounts for about 150 attacked organizations, including the German Bishops' Conference and the Die Linke party. NCC Group counted 108 Qilin attacks in January 2026, 17 percent of all ransomware activity it observed that month.
The arrest did not stop the dedicated leak site. Qilin posted at least 75 victims every month from April through September, according to Trellix. Qilin also listed the US Bureau of Alcohol, Tobacco, Firearms and Explosives on the day the agency disclosed a major incident affecting a standalone system. ATF did not attribute the compromise to Qilin, and the dedicated leak site supplied no files or other public evidence supporting the claim. Removing one developer from a ransomware-as-a-service operation does little once the encryptor and the affiliate panel already work, a limit I examined when arresting one hacker failed to kill a collective.
The two cases expose the geographic limit on ransomware enforcement. Evidence can produce an arrest warrant, but physical custody still depends on travel or cooperation from the country sheltering the suspect. Snake took a holiday in Japan, and German investigators turned a covert operation into a prisoner. The airline records reviewed by Krebs show only domestic travel. Russia's constitution bars the extradition of its citizens, leaving Western investigators dependent on Yakovtsev entering a cooperating jurisdiction. Washington faced the same wall when America named the man attacking its water plants and could do nothing about it.
The same pattern held for The Gentlemen, whose alleged administrator Krebs named in June 2026. Five months on, no indictment, sanction, or takedown has followed, and The Gentlemen kept posting victims through October.
Affiliate Pressure Is Already Visible
Qilin's decline began before Krebs published. Trellix counted 655 Qilin victim posts between April and September 2026, 22 percent fewer than the previous six months, yet still 48 percent above the same period a year earlier. Qilin has weakened against competitors without becoming operationally weak. Qilin led the two previous six-month periods Trellix tracked, but this time The Gentlemen rose from 209 posts to 719 and took first place. Qilin remains the more US-focused of the two, with 43 percent of its geo-identified victims in the United States against 28 percent for The Gentlemen.
The rival's lineage sharpens the point. Group-IB traces The Gentlemen to ArmCorp, a former Qilin affiliate crew that split over a US$48,000 unpaid commission after opening an arbitration claim against Qilin on RAMP in July 2025, and Silent Push followed one affiliate from LockBit, Black Basta, and Qilin to The Gentlemen. The operation now posting the most victims is, by that account, run by people who learned the business inside Qilin and left over money. Qilin's own rise followed the same pattern in reverse. Cybereason reported RansomHub affiliates moving to Qilin after RansomHub collapsed in 2025.
Affiliates are mobile, and they follow security as much as revenue. Infrastructure seizures rarely end the business, because police can seize the servers but not the business model. After Operation Cronos, the UK National Crime Agency reported LockBit's registered affiliates fell from 194 to 69.
Qilin's drop coincides with Snake's May detention in Osaka, but the timing alone proves nothing. Market fragmentation offers a competing explanation, with Trellix recording a record 124 operations posting victims in the same period. I assess with moderate confidence Qilin is losing market share to an operation reportedly founded by former affiliates. I assess with low confidence active Qilin affiliates are migrating because of Snake's arrest.
Platform for Every Motivation
Treating Qilin purely as eCrime misses how widely its tooling travels. Microsoft observed SCATTERED SPIDER (aka Octo Tempest) deploying Qilin payloads in 2024, an English-speaking affiliate base unusual for a Russian-language program. Haise has mentioned working with SCATTERED SPIDER and RansomHub on Telegram, according to Krebs. The June 2024 Synnovis attack, attributed to Qilin, forced London hospitals run by Guy's and St Thomas' and King's College Hospital to reschedule more than 800 planned operations in its first week.
The affiliate panel sells capability beyond encryption. Cybereason documented a Call Lawyer button, built-in distributed denial-of-service attacks, spam tooling, an in-house journalist team, and petabyte-scale storage for stolen data. PRODAFT reported largely automated exploitation of FortiGate devices through CVE-2024-21762 and CVE-2024-55591 in 2025, with humans choosing only the victims. In 2026, Trellix places Qilin affiliates among the first to use a Check Point remote access VPN zero-day in June and a Palo Alto Networks GlobalProtect authentication bypass in July.
A nation state adversary has used the platform too. In March 2025, Microsoft reported the North Korean adversary Moonstone Sleet deploying Qilin, the first time Moonstone Sleet used ransomware built by a ransomware-as-a-service provider rather than its own. Bitdefender later documented the Korean Leaks campaign, with 33 claimed victims and 28 publicly listed, nearly all of them South Korean asset managers. Bitdefender attributes the shared access most probably to a compromised upstream IT service provider. The dedicated leak site framed the first wave as hacktivism, promising to expose stock manipulation and corrupt politicians, before reverting to ordinary extortion language.
Bitdefender found strong evidence Qilin's core team, not the affiliate, carried out the final editing and publication of that text. It calls Moonstone Sleet collaboration in the campaign plausible and probable but stops short of attribution.
Qilin infrastructure has served financially motivated affiliates and Moonstone Sleet, but shared infrastructure does not place those threat actors under one administrator's direction. A ransomware-as-a-service administrator supplies code, infrastructure, negotiation support, and publication capacity. Affiliates retain substantial control over targeting and intrusion activity.
Russian authorities have historically tolerated ransomware administrators who avoid targets in the Commonwealth of Independent States, with rare exceptions such as the four REvil members a St. Petersburg military court sentenced in October 2024, and the Qilin RAMP advertisement carries exactly that rule. Public exposure narrows Yakovtsev's mobility if the identification is correct. It does not necessarily create new leverage for Russian services, which have long cultivated offensive talent inside the country and may already know his identity. The disclosure could make him easier to pressure, recruit, sideline, or sacrifice if Qilin becomes politically inconvenient. I assess with low confidence the identification increases Russian state leverage over Qilin's leadership.
Collection Behind the Arrest
Snake's computer may matter more than Snake's testimony. Investigators followed cryptocurrency payment flows and linked Qilin to several hundred affiliates, and Reul said they entered the perpetrators' computers unnoticed to read their communications. A developer's endpoint can expose build pipelines, affiliate identifiers, cryptocurrency wallets, support records, victim negotiations, and relationships invisible from the dedicated leak site. Those records can convert one arrest into future warrants and infrastructure actions across several countries.
Disclosure carries a cost. Affiliates who believe Snake's system or any RAMP records obtained by investigators exposed them will rotate accounts, wallets, and infrastructure. The movement creates new investigative leads while closing collection channels authorities may have spent more than two years developing. Affiliate migration therefore measures both disruption and lost visibility.
Who a Name Pressures
A government naming carries weight a journalistic one cannot. When the United States and United Kingdom named LockBit's Dmitry Khoroshev in May 2024, the Justice Department unsealed charges, the United States, United Kingdom, and Australia imposed sanctions, the State Department offered US$10 million, and the Treasury's Office of Foreign Assets Control designated a bitcoin address tied to Khoroshev. Sanctions are the lever with teeth. Designating an administrator would force victims, insurers, negotiators, and payment intermediaries to determine whether a Qilin payment benefits a blocked person or property under that person's control, a risk the Treasury's ransomware advisory already flags. Qilin's affiliates depend on victims willing to pay.
The Krebs identification carries none of those consequences, so the pressure falls on affiliates' trust. A program's value to an affiliate depends on the administrator's operational security, and the Krebs chain shows accounts linked to Haise leaking identity data across forums since 2018. Krebs has now added that persona's real-world identity to the risks affiliates weigh. Qilin has already allied with LockBit and DragonForce, which gives departing affiliates a ready destination and gives investigators a reason to watch which panels absorb them.
The devil's advocate case deserves its due as well. Every decisive identity pivot in the Krebs chain passes through a commercial data provider, although the underlying evidence includes forum records, leaked registries, education data, and travel records. Two of those providers, Flashpoint and SpyCloud, advertise on KrebsOnSecurity, a relationship Krebs discloses. A public attribution doubles as a product demonstration, and the incentive to publish runs on a different clock from the incentive to prosecute. None of this makes the chain wrong, yet it explains why the identification arrived as journalism rather than as an indictment.
Public identification also forecloses options for law enforcement. A target who learns his name is public has every reason to avoid international travel, rotate infrastructure, and treat his contacts as compromised. An identification can burn an investigation as easily as it advances one, and only the agencies holding the Operation Albus files, and any RAMP data the FBI obtained, know which outcome this one produced.
Qilin's leadership problem is geographic. Snake left the jurisdiction protecting him and arrived in custody. Yakovtsev, if the attribution holds, remains protected and confined by the same border. Krebs has made his name public. A government designation, indictment, or asset action would determine whether that identity changes the payment system around Qilin.
Until then, affiliate departures, wallet rotation, infrastructure replacement, and future arrests will measure the pressure more reliably than dedicated leak site volume. I assess with moderate confidence Qilin's dedicated leak site keeps posting more than 75 victims a month through 2026. I assess with moderate confidence Qilin's ability to retain affiliates will decide whether the operation fractures beneath the noise it continues to publish.
Analyst Annex
Evidence status as of November 14, 2026. The records cover the public attribution of the Qilin administrator persona Haise, the German investigation and arrest of the alleged Qilin developer known as Snake, and REVENANT SPIDER intrusion procedures documented by Cisco Talos and Group-IB. The ATT&CK mapping is limited to observed Qilin intrusion activity and ransomware behavior. It excludes identity research, law enforcement collection, sanctions analysis, affiliate migration, victim counts, and unverified dedicated leak site claims. SCATTERED SPIDER, Moonstone Sleet, The Gentlemen, the Korean Leaks campaign, and the claimed ATF compromise are context only. Their use of Qilin ransomware or infrastructure does not establish shared personnel, targeting, tasking, or command. Personal contact details published in the identity reporting, including email addresses, a phone number, a date of birth, and a Telegram user identifier, are deliberately excluded.
Intelligence Gaps
| Gap | Why It Matters | What Would Close It |
|---|---|---|
| Identity of the Haise controller | Public reporting links Haise, Rjun, and Alexbigboss44 to Aleksey Mikhailovich Yakovtsev through forum records, a Telegram identifier, breached data, and family contact information. No government has publicly charged, sanctioned, or identified Yakovtsev as Haise | Court records, a government attribution, seized account records, provider returns, financial records, or forensic evidence tying Yakovtsev to Qilin administration |
| Continuity of control over the Haise accounts | A persistent Telegram identifier links activity to one account without proving one person controlled it throughout the six-year record. Administrator personas can be shared, transferred, or recovered after compromise | Provider login records, device identifiers, contemporaneous communications, payment records, or seized systems spanning the relevant period |
| Independence of the public attribution chains | KrebsOnSecurity, GangExposed, IntelHawk, and commercial intelligence providers may rely on overlapping forum archives and leaked identity datasets. Repetition does not provide independent corroboration where the underlying evidence is shared | Source-level provenance showing which records were collected independently, when each source obtained them, and whether any conclusion preceded the other disclosures |
| Provenance and integrity of the attributed Gosuslugi records | The reported dataset supplies a decisive real-world identity pivot without a public chain of custody or technical account of the underlying breach | Original records, breach validation, independent registry confirmation, acquisition history, or provider documentation establishing integrity |
| Leadership structure of REVENANT SPIDER | The public record identifies Haise as a spokesperson or administrator and Snake as an alleged developer. It does not establish whether either person controlled the program alone or how authority is distributed across the reported core group | Affiliate panel records, administrator communications, revenue splits, build-system access, signing or deployment records, or testimony corroborated by seized evidence |
| Scope of Operation Albus access | German authorities report covert access to Qilin systems and communications without identifying the systems reached, the collection period, or whether access continued after the arrest | Court filings, official technical reporting, infrastructure seizure records, warrants, or later prosecutions describing the collected evidence |
| RAMP data obtained by law enforcement | Public domain seizures do not establish acquisition of the forum database, private messages, administrator systems, or historical access logs | A seizure affidavit, government statement, court exhibit, or prosecution relying on private RAMP records |
| Operational effect of Snake's arrest | Qilin continued posting victims after the May detention and October transfer. Dedicated leak site volume cannot show whether development, payments, negotiations, or affiliate support degraded | Affiliate communications, build cadence, payment delays, panel telemetry, victim negotiations, or infrastructure changes attributable to the arrest |
| Current Qilin affiliate population | Victim posts and competitor growth indicate changing market share without identifying how many affiliates remain, which affiliates moved, or whether one affiliate accounts for a large share of attacks | Current panel records, affiliate identifiers, payment ledgers, intrusion clustering, or communications documenting migration between programs |
| Cryptocurrency revenue and administrator wallets | Ransom demands, victim posts, and reported payments measure different things. The public record does not provide a complete wallet cluster or establish how revenue was divided among administrators and affiliates | Validated wallet attribution, payment records, exchange returns, panel ledgers, or blockchain analysis tied to known negotiations |
| Relationship between Qilin administrators and Russian authorities | Avoidance of Commonwealth of Independent States targets and continued operation from Russia are consistent with tolerated cyber crime. They do not establish state direction, protection, recruitment, or intelligence cooperation | Government communications, tasking, payments, protection arrangements, travel records, arrests, or corroborated human intelligence |
| Relationship between Snake and the Haise persona | No public source links the two. A link would show whether German investigators already hold data identifying the administrator | German charging documents, trial filings, or a statement from the North Rhine-Westphalia authorities |
| Snake's identity and charges | Public reporting gives only an initial, an age, and an alias, and spells the first name both Vladimir and Volodymyr | Charging documents or a statement from the Central and Contact Point for Cybercrime in North Rhine-Westphalia |
| Source and motive of GangExposed | A former insider, a rival, or a channel for law enforcement data would each change how much weight the disclosure carries. Its earlier identification of Conti leader Stern was followed by a German government naming | Forensic overlap between GangExposed material and seized records, or confirmation from law enforcement or the leaker |
| Cause of Qilin's decline in victim posts | Trellix recorded 22 percent fewer Qilin posts from April to September 2026 than in the prior six months. The drop coincides with Snake's May detention, but market fragmentation and The Gentlemen's growth offer competing explanations | Affiliate migration evidence from forums, panel data, or intrusion clustering attributing new activity to former Qilin affiliates |
| Haise's RAMP join date | KrebsOnSecurity places the approval in June 2022, while BushidoToken places the join date at May 29, 2022 | Intel 471 or RAMP records showing application and approval dates |
| Moonstone Sleet access to Qilin | Microsoft reported North Korean use of Qilin ransomware. Public reporting does not establish whether the adversary joined the affiliate program, purchased a build, received access through an intermediary, or reused leaked material | Panel records, payment evidence, malware build lineage, administrator communications, or infrastructure records connecting Moonstone Sleet to Qilin provisioning |
Entities
| Entity | Type | Role | Status | Source |
|---|---|---|---|---|
| REVENANT SPIDER (aka Qilin, Agenda and Stinkbug) | Threat actor, eCrime | CrowdStrike adversary operating the Qilin ransomware-as-a-service program, which CrowdStrike assesses is a rebrand of Agenda | Reported | CrowdStrike |
| Qilin | Ransomware and ransomware-as-a-service platform | Multi-platform ransomware operation supporting affiliates, data theft, encryption, negotiations, payments, and publication through a dedicated leak site | Confirmed | Group-IB, Cisco Talos |
| Haise | Threat actor persona | Qilin spokesperson and administrator persona active in affiliate recruitment and program communications | Confirmed | BushidoToken, KrebsOnSecurity |
| Aleksey Mikhailovich Yakovtsev | Person | Russian national publicly identified by KrebsOnSecurity as the likely controller of Haise, Rjun, and Alexbigboss44. No public government attribution or charge connects him to Qilin | Reported | KrebsOnSecurity |
| Alexbigboss44 and Rjun | Threat actor personas | Telegram username referenced in the RAMP messages approving Haise, and the Exploit and XSS account sharing that handle in 2020, profiled as a broker of stolen logs, traffic, and corporate access | Reported | KrebsOnSecurity |
| XORacle | Threat actor persona | Second Qilin administrator persona named in a fake Europol bounty post Europol called a scam | Claimed | SOCRadar |
| Snake | Threat actor persona | Persona used by a 28-year-old Russian national whom German authorities allege was a central Qilin developer and core member. Japanese authorities detained him in May 2026 before his transfer to Germany on October 2 | Reported | ad-hoc-news, The Insider |
| Operation Albus | Law enforcement operation | German investigation by the State Criminal Police Office and the Central and Contact Point for Cybercrime in North Rhine-Westphalia since mid-2024, involving covert entry into the perpetrators' computers, monitoring of communications, cryptocurrency tracing, and the identification and arrest of Snake | Confirmed | Tagesspiegel, ad-hoc-news |
| RAMP | Cybercrime forum | Russian-language forum used for ransomware recruitment and the 2022 Haise membership application. The FBI seized its public domains in January 2026 | Confirmed | KrebsOnSecurity, The Register |
| GangExposed | Anonymous disclosure persona | Anonymous account that published a separate Haise identity chain before the KrebsOnSecurity report. Its access, motivation, and relationship to law enforcement remain unestablished | Reported | SOCRadar, The Register |
| Qilin.B | Ransomware | Qilin variant observed by Cisco Talos in 2025 incidents, including dual encryptor deployment against endpoints and network shares | Confirmed | Cisco Talos |
| CVE-2023-27532 | Vulnerability | Veeam Backup & Replication vulnerability used in reported Qilin activity to obtain encrypted credentials from the configuration database | Reported | Group-IB, NVD |
| CVE-2024-21762 | Vulnerability | Fortinet FortiOS out-of-bounds write vulnerability associated by Group-IB and PRODAFT with Qilin access through exposed Fortinet devices | Reported | Group-IB, PRODAFT via Security Affairs, NVD |
| CVE-2024-55591 | Vulnerability | FortiOS and FortiProxy authentication bypass vulnerability associated by Group-IB and PRODAFT with Qilin access through exposed Fortinet devices | Reported | Group-IB, PRODAFT via Security Affairs, NVD |
| Mimikatz | Credential access tool | Used in Cisco Talos Qilin cases to recover credentials, browser passwords, previous logons, and remote access configuration data | Confirmed | Cisco Talos |
| Cyberduck | Legitimate file transfer tool | Abused in Cisco Talos Qilin cases to transfer stolen data to cloud storage, including a reported Backblaze destination | Confirmed | Cisco Talos |
| SystemBC | Proxy malware and backdoor | Observed on compromised systems before Qilin deployment in Cisco Talos incident response cases | Confirmed | Cisco Talos |
| Cobalt Strike | Commercial adversary simulation framework | Abused before Qilin deployment. Cisco Talos recovered a loader executing an encrypted Beacon in memory | Confirmed | Cisco Talos |
MITRE ATT&CK Mapping
Cisco Talos 2025 Qilin Intrusions
| Tactic | Technique | Procedure | Status | Source |
|---|---|---|---|---|
| Initial Access | T1078, Valid Accounts | In some cases, Cisco Talos assessed with moderate confidence that administrative credentials leaked on the dark web were used to access a VPN. In one case the VPN had no multifactor authentication | Reported | Cisco Talos |
| Initial Access | T1133, External Remote Services | The threat actor entered through a victim VPN and used remote access paths into the internal network | Reported | Cisco Talos |
| Execution | T1059.001, Command and Scripting Interpreter: PowerShell | The threat actor used PowerShell to disable AMSI, query Active Directory, clear event logs, and run a script against vCenter and ESXi disabling HA and DRS, changing the root password, and enabling SSH | Confirmed | Cisco Talos |
| Persistence | T1053.005, Scheduled Task/Job: Scheduled Task | The threat actor created the TVInstallRestore task to run a ransomware executable disguised as a TeamViewer installer as SYSTEM at logon |
Confirmed | Cisco Talos |
| Persistence | T1547.001, Boot or Logon Autostart Execution: Registry Run Keys / Startup Folder | The threat actor added a Qilin executable and its password argument to the Windows Run key for execution after reboot | Confirmed | Cisco Talos |
| Defense Impairment | T1685, Disable or Modify Tools | The threat actor disabled AMSI and attempted to stop or uninstall endpoint protection through service commands, dark-kill, and HRSword | Confirmed | Cisco Talos |
| Stealth | T1070.001, Indicator Removal: Clear Windows Event Logs | Qilin used PowerShell and Mimikatz functionality to clear Windows event logs | Confirmed | Cisco Talos |
| Credential Access | T1003.001, OS Credential Dumping: LSASS Memory | The threat actor enabled WDigest plaintext credential retention and used Mimikatz and related utilities to recover logon material | Confirmed | Cisco Talos |
| Credential Access | T1555.003, Credentials from Password Stores: Credentials from Web Browsers | Mimikatz and SharpDecryptPwd collected saved credentials from Chrome and other client applications | Confirmed | Cisco Talos |
| Discovery | T1018, Remote System Discovery | The threat actor used nltest, network scanning, and Active Directory queries to identify domain controllers and reachable hosts |
Confirmed | Cisco Talos |
| Discovery | T1087.002, Account Discovery: Domain Account | The threat actor used net user and Active Directory tools to enumerate domain users, groups, and privileges |
Confirmed | Cisco Talos |
| Discovery | T1057, Process Discovery | The threat actor used tasklist to enumerate active processes and identify logged-on user activity |
Confirmed | Cisco Talos |
| Lateral Movement | T1021.001, Remote Services: Remote Desktop Protocol | The threat actor used RDP from the compromised VPN to reach the domain controller and internal hosts | Confirmed | Cisco Talos |
| Lateral Movement | T1021.002, Remote Services: SMB/Windows Admin Shares | Qilin.B used PsExec to copy and execute one encryptor across remote Windows hosts | Confirmed | Cisco Talos |
| Collection | T1560.001, Archive Collected Data: Archive via Utility | The threat actor used WinRAR to package selected victim data before exfiltration | Confirmed | Cisco Talos |
| Exfiltration | T1048, Exfiltration Over Alternative Protocol | A script sent consolidated credential data to an attacker-controlled SMTP server | Confirmed | Cisco Talos |
| Exfiltration | T1537, Transfer Data to Cloud Account | The threat actor used Cyberduck to upload stolen data to cloud storage, including a reported Backblaze destination | Confirmed | Cisco Talos |
| Impact | T1490, Inhibit System Recovery | Qilin changed the Volume Shadow Copy Service configuration and deleted all shadow copies | Confirmed | Cisco Talos |
| Impact | T1489, Service Stop | Qilin configurations directed the malware to terminate database, backup, security, virtualization, and remote management processes and services | Confirmed | Cisco Talos |
| Impact | T1486, Data Encrypted for Impact | Qilin.B encrypted local systems and network shares. Cisco Talos observed separate encryptors for endpoint propagation and remote share encryption | Confirmed | Cisco Talos |
Other Reported Qilin Intrusions
| Tactic | Technique | Procedure | Status | Source |
|---|---|---|---|---|
| Initial Access | T1190, Exploit Public-Facing Application | Qilin affiliates exploited FortiGate devices through CVE-2024-21762 and CVE-2024-55591 in largely automated attacks in 2025 | Reported | PRODAFT via Security Affairs, Group-IB |
| Initial Access | T1190, Exploit Public-Facing Application | Qilin exploited CVE-2023-27532 in internet-facing Veeam Backup & Replication to extract stored credentials, then reached the backup server over RDP | Reported | Group-IB |
| Initial Access | T1199, Trusted Relationship | Qilin affiliates most probably used a compromised upstream IT service provider to reach South Korean asset managers in the Korean Leaks campaign | Reported | Bitdefender |
| Impact | T1486, Data Encrypted for Impact | Qilin affiliates encrypted and stole data from a North Rhine-Westphalia logistics company in September 2024 and demanded US$165,000 in bitcoin, the attack behind Germany's warrant for Snake | Reported | The Insider |
Indicators
The table contains a capped operational subset from Cisco Talos Qilin incidents documented in 2025. Domains and IP addresses are defanged and may be inactive or reassigned. Hashes identify samples from those cases and will not cover customized or later Qilin builds. PsExec, Mimikatz, Cyberduck, Cobalt Strike, ScreenConnect, AnyDesk, Chrome Remote Desktop, Quick Assist, WinRAR, Backblaze, and other legitimate or dual-use products are not indicators by themselves.
| Indicator | Type | Context | Status | Source |
|---|---|---|---|---|
regsvchst[.]com |
Domain | Listed in the Cisco Talos Qilin incident indicator set | Confirmed | Cisco Talos |
holapor67[.]top |
Domain | Listed in the Cisco Talos Qilin incident indicator set | Confirmed | Cisco Talos |
85.239.34[.]91 |
IPv4 address | Listed in the Cisco Talos Qilin incident indicator set | Confirmed | Cisco Talos |
86.106.85[.]36 |
IPv4 address | Listed in the Cisco Talos Qilin incident indicator set | Confirmed | Cisco Talos |
8fe746dd277e644fa0337db3394f0eadfafe57df029e13df9feef25c536adf4d |
SHA-256 | Qilin ransomware sample, detected as Win.Ransomware.Qilin | Confirmed | Cisco Talos |
dbe9ed8e8e8cdff3670e7205cb9f11b5a0fa9d1983a6c6bab67527d8775c4ffd |
SHA-256 | Listed in the Cisco Talos Qilin incident indicator set | Confirmed | Cisco Talos |
e129dd5cc80f39b24db489df999c847335d169910bd966814d2f81b0b1bbc365 |
SHA-256 | Listed in the Cisco Talos Qilin incident indicator set | Confirmed | Cisco Talos |
dd29138bf369863c33402a3fc995458ab5fc015a13a9378022131ab31d940c9f |
SHA-256 | Listed in the Cisco Talos Qilin incident indicator set | Confirmed | Cisco Talos |
The complete Cisco Talos collection includes additional ScreenConnect, Cyberduck, Mimikatz, HRSword, network scanning, SystemBC, and Cobalt Strike artifacts from the same incident set.
Related Activity
The activity below provides context for Qilin's affiliate ecosystem, cross-motivation use, victim claims, and enforcement pressure. None establishes that Haise or Snake personally directed the reported intrusions, that every affiliate shares the same procedures, or that the Qilin administrators controlled the external threat actors using their ransomware.
| Activity | Relationship | Status | Source |
|---|---|---|---|
| SCATTERED SPIDER deployment of Qilin | Microsoft observed the English-speaking eCrime adversary adding Qilin and RansomHub payloads in 2024. Use of the ransomware does not establish membership in the Qilin core | Reported | Security Affairs |
| Moonstone Sleet use of Qilin | Microsoft observed the North Korean adversary deploying Qilin in a limited number of attacks from February 2025, its first use of ransomware built by a ransomware-as-a-service provider. The access path and the relationship with Qilin administrators remain unpublished | Reported | Security Affairs |
| Korean Leaks campaign | Bitdefender documented 33 claimed victims and 28 public listings, focused largely on South Korean financial organizations. It found evidence that the Qilin core edited and published dedicated leak site text while assessing Moonstone Sleet involvement as plausible and probable | Reported | Bitdefender |
| The Gentlemen and ArmCorp lineage | Group-IB describes The Gentlemen as evolving from ArmCorp, a former Qilin affiliate group that split over a US$48,000 unpaid commission, while Silent Push followed one affiliate from LockBit, Black Basta, and Qilin to The Gentlemen. The evidence supports affiliate mobility without establishing broad migration from Qilin | Reported | Group-IB, Silent Push |
| Qilin, LockBit, and DragonForce alliance announcement | The ransomware operations announced plans to share resources and infrastructure. Public statements do not establish merged leadership, common targeting, or completed technical integration | Claimed | The Hacker News |
| ATF dedicated leak site claim | Qilin listed the US Bureau of Alcohol, Tobacco, Firearms and Explosives when the agency disclosed a major incident affecting a standalone system. ATF did not attribute the intrusion and Qilin published no supporting files | Claimed | SOCRadar |
| Synnovis attack | The June 2024 Qilin intrusion disrupted pathology services in London, forced the rescheduling of more than 800 planned operations during the first week, and carried Qilin's highest reported ransom demand of US$50 million | Reported | Security Affairs, Group-IB |
| Trellix victim post data, April to September 2026 | Qilin posted 655 victims, 22 percent fewer than the previous six months and 48 percent above the same period a year earlier, and lost first place to The Gentlemen with 719 | Reported | Trellix |
| The Gentlemen administrator identification, June 2026 | KrebsOnSecurity named the alleged administrator. As of October 23, no arrest, indictment, sanction, or seizure had followed, and the dedicated leak site kept publishing | Reported | Ransomnews |
| LockBit administrator naming, May 2024 | Government identification of Dmitry Khoroshev came with charges, US, UK, and Australian sanctions, a US$10 million reward, and a designated bitcoin address. LockBit's registered affiliates had fallen from 194 to 69 after Operation Cronos | Confirmed | The Register, TRM Labs |
| Conti and TrickBot leader Stern identification, May 2025 | GangExposed's earlier disclosure, followed within weeks by the German Federal Criminal Police Office naming the same individual | Confirmed | The Register |