Article
What To Do When A Hacker Encrypts Your Data
Combating Ransomware
Cyber Threats

RANSOMWARE, RANSOMWARE...
It’s the boogeyman looming in the corners of every digital task we do. Even businesses that don’t operate primarily online have data points that can be exploited, and hackers are always on the lookout for those with poor cyber health.

[This article originally appeared in Risk & Insurance at:
We Talk About Ransomware All the Time. So What Do We Actually Do When a Hacker Has Our Data? : Risk & Insurance (riskandinsurance.com)]
The cost of an attack is growing, too. As Gallagher reported in its 2022 Cyber Insurance Market Conditions Report, during the first six months of 2021, $590 million were paid in ransom payments, as opposed to $416 million paid in all of 2020.
While we talk about best practices to protect ourselves, how often do we flip the conversation and look at the steps we must take when a hack actually occurs? “Unfortunately, no one is safe from ransomware,” said Evgueni Erchov, head of security research & strategy, Arete.
“The most sophisticated groups can focus on larger organizations … but we also see the small companies being targeted all the time.”
Erchov is an experienced hacker negotiator, with more than 20 years in IT security, application development, cybercrime investigations, computer forensics, cryptocurrency blockchain and cyber threat intelligence analysis.
Erchov, alongside John Farley, managing director, cyber practice, at Gallagher, put on a recent webinar on what to do when a hacker strikes, running through a simulated hack to give businesses recovery tips.
The presentation, “What Really Happens When You Negotiate With a Hacker: An Insider’s View,” illuminated several key points, from how to communicate with hackers, where to gather cryptocurrency if a hacker demands it, and what conversations with underwriters should look like when reviewing cyber controls.
Getting in Touch with Your Hacker
Believe it or not, hacking is a business, and hackers treat what they do as such.
Organized criminals work together to suss out vulnerable targets — from a large corporation all the way down to the neighborhood corner store. If the business has the capability to store data — credit card info, health records, trade secrets, you name it — the business is a viable target.
When a hacker infiltrates a system, the language used in their demand can follow a similar pattern. Hackers will note the data they have access to — employee personal records, partner and client data, financial and accountant documents — and how they intend to gain ransom for encrypting these files.
Next steps will focus on how to communicate with the hacker.
“It depends on how sophisticated the group is,” Erchov said. “Sometimes a ransom note will contain an email address that will be used to go back and forth and negotiate a ransom.”
Money and Extortion: How Demands Lives Have Changed
“In the old days, five or six years ago, we had hackers typically freezing our data, we had extortion, but if you didn’t pay, you just didn’t get your data back,” Farley said.
The scare tactics being used by hackers are changing.
In the simulation during the presentation, the fictive hacker threatens to reveal extremely sensitive data from the company CEO if they don’t receive $1 million in bitcoin within five days. To prove how serious they are, the hacker sends an excerpt of that sensitive info.
Extortion and double extortion are commonplace for hackers these days, Erchov said.
“That really happens quite often, on average, close to 70% of cases nowadays will involve data exfiltration along with the encryption,” he said.
It’s a tactic used to encourage payment, because it not only involves the encryption of sensitive data, but it also hangs corporate reputation in the balance. The ransom becomes more than just retrieving data; it becomes about keeping that data out of public hands.
Bitcoin: How the Heck Do I get My Hands on That?
Once the decision to pay the hackers is made, the next issue is figuring out how to follow through. More hackers are demanding bitcoin payments in their ransoms, but not all companies are working in bitcoin.
So then, what do companies do when their data is held for ransom?
As noted by Farley and Erchov, people believe the first place to go for bitcoin is their cyber insurer. But this is not correct.
“The forensic investigator … the company that deals with forensic investigation and interim response, that’s typically the company that will be handling that,” Erchov said.
However, the cyber insurer can be there to guide the process.
“The beauty of the cyber insurance policy is that you have access to these companies [like a forensic investigation company] that have access to bitcoin and can facilitate the payments,” added Farley.
Forensic investigation companies are often operating on a 24/7 basis as well, and the cyber insurance policy acts as a bridge between client and forensics.
Farley noted these payments are also on reimbursement, so the cyber policy is typically designed to reimburse ransoms after the fact.
The Decision to Negotiate
While paying a hacker immediately to get encrypted data back seems like a no brainer, sometimes negotiating down the ransom is the best line of action, especially if a ransom demand is really large or unfeasible.
But what if low-balling a hacker leads to a bigger data leak?
“They almost expect the initial demand is not going to be paid,” said Erchov.
But it’s important to partner with a negotiator, he said, because the negotiation strategist knows what is a reasonable offer versus what could anger the hacker.
The good news: On average, hackers will negotiate down a ransom by 70%, according to Erchov, based on the cases his company Arete has dealt with in the past.
But that depends on several different factors.
“Potentially, the backups might be available. So in that case, if we only have to negotiate for promise of data deletion, it gives us additional leverage because we don’t need a decryption tool,” Erchov gave as an example.
Questions Your Underwriter Will Ask
“We have a very hard cyber insurance marketplace today,” said Farley. “We’re in a place where ransomware and other factors are really getting the underwriting community very nervous.”
Because of the risk landscape and the size of demand, rates are increasing. Some entities with less cyber controls in place are facing nonrenewal.
So, how can a company make itself a good risk for an underwriter?
“They are going to have a lot of questions for you,” said Farley. He noted his list was not all encompassing, but these are key areas to start.
“Multi-factor authentication. If you don’t have that in place, there’s a chance you might not get underwritten at all,” he said.
Underwriters will also want to see patch management — a written and detailed plan to manage any hacker exploitation. Point detection and response, which is technology used to find a hacker in your system and alert you to them, is another control underwriters like to see.
At the end of the day, the key thing to remember is if your company is on the receiving end of a cyber ransomware event, call your cyber partners immediately.
They will know which resources, from bitcoin, negotiators, forensics and more, will aid in appeasing the hacker and getting your data secured.
Back to Blog Posts
Report
Malware Spotlight: Qilin Ransomware
Executive Summary
Over the past few years, Arete’s Incident Response (IR) team has responded to more than one hundred incidents attributed to the Qilin ransomware group. Active since October 2022 under a different name (Agenda), the group had an increase in activity at the beginning of 2025, especially during the second quarter, when it was the most active threat group. Notably, most of its activity came in June 2025, as the group exploited vulnerabilities in Fortinet’s FortiGate appliances and reportedly attempted to recruit ex-RansomHub affiliates. In the first quarter of 2026, the group remained the second most active extortion group behind Akira and actively targeted WatchGuard Firebox devices for initial access, particularly those vulnerable to CVE-2025-14733, a critical vulnerability in WatchGuard Fireware OS that allows a remote, unauthenticated threat actor to execute arbitrary code.
This spotlight explores the ransomware group’s observed behavior, background information on the threat actor, and statistics from Incident Response engagements, along with a technical analysis of Qilin’s ransomware executable. Finally, we discuss security recommendations to better defend against this evolving cyber threat and mitigate the risk of financial and reputational losses. For more insights and data on Qilin and other top threat groups, explore Arete’s Q1 2026 Crimeware Report.
Incident Response Data on the Qilin Ransomware Group
The information below is based on Arete engagements attributed to Qilin since August 2023. Our IR, Threat Intelligence, and Data Analytics teams work together to analyze key data points during every ransomware engagement and form real-time threat actor (TA) insights.
Impacted sectors include professional services, public services, healthcare, financial services, manufacturing, high technology, retail, and hospitality.
The median initial ransom demand is $400,000.
Tools observed during investigations include Mimikatz, Lazagne, FGDump, PsExec, Splashtop, Mesh Agent, Atera, ScreenConnect Client, AnyDesk, SoftPerfect Network Scanner (Netscan), Advanced Port Scanner, WinRAR, WinSCP, FileZilla, Putty, Rclone, and MEGAsync.
Qilin-affiliated actors often exploit edge device vulnerabilities or use legitimate credentials.
The group operates a TOR data leak site (DLS), where it self-identifies as Qilin and commonly threatens to release stolen data if a payment is not made.
The ransom note identifies the group as Qilin and contains links to its data leak and chat negotiation sites. To initiate negotiations, login credentials are included in the ransom note. Part of the ransom note filename matches the encrypted file extension as a naming convention.
In addition to encrypting files and creating a ransom note, the Qilin ransomware requires a password to execute properly, supports various command-line arguments, deletes volume shadow copies, clears the Windows Event Logs, and creates a desktop wallpaper displaying information about the encryption event.
Background
Arete first observed Qilin in incident response engagements in 2023. Over time, the group evolved into an increasingly sophisticated and notable ransomware operation, becoming the top threat group in Q2 of 2025 and the second-most active, after Akira, in Q3 and Q4 of 2025 and Q1 of 2026.
TOP THREAT GROUPS OBSERVED BY QUARTER

Figure 1: Top threat groups observed by Arete by quarter
Qilin impacts a broad range of organizations throughout North America and often lists victims that fail to reach a negotiation agreement on its data leak site. The group maintains Windows and Linux versions of its ransomware, and the most recently observed Windows-based version was developed in the Rust programming language. Qilin has been observed exploiting vulnerabilities in Fortinet appliances as an initial access vector.
In 2025, Qilin broadened its RaaS platform by introducing a “Call Lawyer” negotiation-support feature, through which affiliates can request assistance from individuals that Qilin portrays as an internal legal team when victims delay or resist negotiations. The goal is to provide affiliates with tactics that pressure victims into believing that non-compliance could lead to regulatory scrutiny, fines, or even criminal exposure. Additionally, the platform offers affiliates more aggressive coercion methods, such as launching distributed denial of service (DDoS) attacks against victim websites.
Technical Analysis
Malware analysis revealed that Qilin ransomware:
Supports multiple command-line arguments.
Requires the correct password to fully encrypt files.
Appends a file extension to all encrypted files; however, the extension is not static. Instead, it is randomly generated for each incident. As an example, this report uses the extension XXXXXXXXX (e.g., file.docx.XXXXXXXXX).
Generates a ransom note with a filename that incorporates the same randomized extension value used during encryption. Continuing the example above, the ransom note was named README-RECOVER-XXXXXXXXXX.txt, where XXXXXXXXXX corresponds to the unique extension assigned in this incident.
Self-identifies the group as Qilin in the ransom note.
References a data leak site in the ransom note that, when accessed, also self-identifies the group as Qilin.
Kills a list of processes and services.
Clears Windows event logs.
Maintains a list of whitelisted files and directories to ensure the system does not become unusable, preventing recovery when running a decryptor.
Attempts to prevent system recovery by deleting the system's volume shadow copies.
Creates a mutex during execution.
Creates an image file in the %Temp% directory and later modifies a registry key to change the desktop wallpaper.
Creates log files in a QLOG directory created in %TEMP% (e.g., ThreadId(1).LOG).
Has a well-defined ransomware configuration with various fields like company_id, accounts, note, password_hash, directory_black_list, file_ black_list, process_black_list, and file_pattern_black_list.
Execution Pattern/Arguments
Qilin ransomware will not execute in the system without the correct “--password” argument.
Example of the command to run the executable:
Qilin.exe --password XXXXXXXXXXXXX --no-admin |
Screenshot of the ransomware execution in the command prompt with the password argument redacted:

Figure 2. Ransomware execution in command prompt
List commands supported by the Qilin ransomware analyzed:
Command Line Parameters | Description |
|---|---|
--password | Required to start program. Reads password from password.txt. |
--spread | Spreads to Windows hosts using login credentials. Does not encrypt local machine. |
--spread-vcenter | Distributes payload to ESXi/vCenter hosts and installs modules. No local encryption. |
--no-admin | Disables admin rights check. |
--no-priority | Disables CPU and IO priority settings. |
--no-extension | Prevents file extension change during encryption. |
--no-note | Disables ransom note saving in folders. |
--timer | Delays execution by specified seconds. |
--paths | Encrypts only specified paths/directories. |
--ips | Encrypts only network resources on specified IPs or hosts. |
--no-ef | Disables file extension filtering. |
--no-ff | Disables file name/type filtering. |
--no-df | Disables directory filtering. |
--no-proc | Disables process killer functionality. |
--no-services | Disables service killer functionality. |
--no-vm | Disables virtual machine detection and related kills. |
--no-sandbox | Disables sandbox detection logic. |
--kill-cluster | Enables destruction of cluster environments. |
--safe | Reboots to safe mode, enables autologin, and begins encryption. |
--no-autostart | Prevents self-autostart configuration. |
--no-wallpaper | Prevents wallpaper or lockscreen changes. |
--no-destruct | Prevents self-destruction after execution. |
--no-zero | Disables wiping of free disk space post-encryption. |
--no-local | Skips encryption of local volumes. |
--no-mounted | Skips encryption of mounted shares and network shortcuts. |
--no-domain | Skips host discovery in domain networks. |
--no-network | Skips host discovery in the entire subnet. |
--exclude | Skips specified hosts/IPs from encryption and scanning. |
--print-image | Prints a message to all available printers post-encryption. |
--print-delay | Sets delay before printing with --print-image. |
--force | Allows multiple instances by skipping mutex creation. |
--no-logs | Disables writing of log files. |
--logs | Collects and archives logs to local directory. |
--dry-run | Runs encryption simulation without modifying files. |
Stop Services and Processes
Before file encryption, the ransomware terminates a pre-determined list of processes and services to encrypt as many files as possible.
Process names:
vmms, vmwp, vmcompute, agntsvc, dbeng50, dbsnmp, encsvc, excel, firefox, infopath, isqlplussvc, sql, msaccess, mspub, mydesktopqos, mydesktopservice, notepad, ocautoupds, ocomm, ocssd, onenote, oracle, outlook, powerpnt, sqbcoreservice, steam, synctime, tbirdconfig, thebat, thunderbird, visio, winword, wordpad, xfssvccon, bedbh, vxmon, benetns, bengien, pvlsvr, beserver, raw_agent_svc, vsnapvss, cagservice, qbidpservice, qbdbmgrn, qbcfmonitorservice, sap, teamviewer_service, teamviewer, tv_w32, tv_x64, cvmountd, cvd, cvfwd, cvods, saphostexec, saposcol, sapstartsrv, avagent, avscc, dellsystemdetect, enterpriseclient, veeamnfssvc, veeamtransportsvc, veeamdeploymentsvc, mvdesktopservice |
Service names:
vmms, mepocs, memtas, veeam, backup, vss, sql, msexchange, sophos, msexchange, msexchange\\$, wsbexchange, pdvfsservice, backupexecvssprovider, backupexecagentaccelerator, backupexecagentbrowser, backupexecdivecimediaservice, backupexecjobengine, backupexecmanagementservice, backupexecrpcservice, gxblr, gxvss, gxclmgrs, gxcvd, gxcimgr, gxmmm, gxvsshwprov, gxfwd, sapservice, sap, sap\\$, sapd\\$, saphostcontrol, saphostexec, qbcfmonitorservice, qbdbmgrn, qbidpservice, acronisagent, veeamnfssvc, veeamdeploymentservice, veeamtransportsvc, mvarmor, mvarmor64, vsnapvss, acrsch2svc, (.*?)sql(.*?) |
File and Directory Exclusions
The ransomware excludes system-related files and folders, ransomware-related files, and whitelisted extensions during encryption.
Excluded file extensions:
themepack, nls, diapkg, msi, lnk, exe, scr, bat, drv, rtp, msp, prf, msc, ico, key, ocx, diagcab, diagcfg, pdb, wpx, hlp, icns, rom, dll, msstyles, mod, ps1, ics, hta, bin, cmd, ani, 386, lock, cur, idx, sys, com, deskthemepack, shs, theme, mpa, nomedia, spl, cpl, adv, icl, msu, XXXXXXXXXX |
Excluded directories:
windows, system volume information, intel, admin$, ipc$, sysvol, netlogon, $windows.~ws, application data, mozilla, program files (x86), program files, $windows.~bt, msocache, tor browser, programdata, boot, config.msi, google, perflogs, appdata, windows.old, appdata, .., ., boot, windows, windows.old, $recycle.bin, admin$ |
Excluded files:
desktop.ini, autorun.ini, ntldr, bootsect.bak, thumbs.db, boot.ini, ntuser.dat, iconcache.db, bootfont.bin, ntuser.ini, ntuser.dat.log, autorun.inf, bootmgr, bootmgr.efi, bootmgfw.efi, #recycle, autorun.inf, boot.ini, bootfont.bin, bootmgr, bootmgr.efi, bootmgfw.efi, desktop.ini, iconcache.db, ntldr, ntuser.dat, ntuser.dat.log, ntuser.ini, thumbs.db, #recycle, bootsect.bak |
Inhibit System Recovery
Windows operating systems contain features that can help fix corrupted system files, including shadow copies, which are backups of files created by the Volume Shadow Copy Service (VSS). By deleting shadow copies, the ransomware can prevent victims from restoring files from backups, making it more difficult for them to recover their data without paying the ransom.
The ransomware deletes volume shadow copies and disables the Windows Volume Shadow Copy Service (VSS) before file encryption by starting the following processes:
wmic service where name='vss' call ChangeStartMode Manual |
System Network Connections Discovery
Qilin ransomware can enumerate network-mounted shares by scanning the network interfaces.
Data Encrypted for Impact
The ransomware initially finds available drives, then loads the files one by one using the Windows APIs “FindFirstFileW“ and “FindNextFileW”. The ransomware generates random AES keys to encrypt the files, then encrypts the AES keys using a public RSA key. The resulting key is placed at the end of the file.
The ransomware encrypts files, adds a randomized extension to the encrypted files, and appends the following bytes towards the end of each file.
-----END CIPHERTEXT BLOCK----- |

Figure 3. “.XXXXXXXXXX” extension added to the encrypted files

Figure 4. Encrypted file padding bytes followed by encrypted AES keys
Upon successful execution, the ransomware creates a ransom note with the file name README-XXXXXXX-XXXXXXXXXX.txt.

Figure 5. Screenshot showing a portion of the Qilin ransom note
Ransom note content:
-- Qilin Your network/system was encrypted. -- Compromising and sensitive data We have downloaded compromising and sensitive data from your system/network. Blog links: Data includes: -- Warning 1) If you modify files - our decrypt software won't able to recover data -- Recovery 1) Download tor browser: https://www.torproject[.]org/download/ Please note that communication with us is only possible via the website in the Tor browser, which is specified in this note. -- Credentials Extension: XXXXXXXXXX |
Modify Registry
The Windows registry is a database that stores configuration settings and values for the Windows operating system. It manages user preferences, installed software, system configurations, and more. Malware abuses the Windows registry to maintain persistence, hide its presence, disable security settings, and launch malicious scripts.
The QIlin ransomware performs a registry key modification to change the desktop wallpaper.
Registry Key | Value Name | Value Data |
|---|---|---|
Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Wallpapers | BackgroundHistoryPath0 | C:\Users\Akxy\AppData\Local\Temp\jjAJrgQA.jpg |

Figure 6. Screenshot showing the registry modification

Figure 7. Wallpaper image content from the C:\Users\%USERNAME%\AppData\Local\Temp\jjAJrgQA.jpg file
The ransomware performs the following registry key modification to achieve persistence:
Registry Key | Value Name | Value Data |
|---|---|---|
Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run | *zgngnt | Qilin.exe --password XXXXXXXXXXXXX --no-admin --no-admin |

Figure 8. Screenshot showing the registry modification
Mutex
The mutex is the fundamental tool for managing shared resources between multiple threads or processes. Typically, malware uses a mutex to avoid reinfecting the victim system and causing multiple layers of encryption. The ransomware creates the following mutex value: c4eed3e3a7e1114c2864980024a9c68f88e647866a180835afafd5ef80da1afe

Figure 9. Screenshot of the mutex value created while debugging the ransomware
Network Activity
The ransomware did not try to communicate with a remote server other than encrypting data from mounted shares.
Indicator Removal
Windows Event Logs keep a record of a computer's alerts and notifications, and the ransomware clears these logs to hide its malicious activity. The following command was executed to clear the logs:
"powershell" $logs = Get-WinEvent -ListLog * | Where-Object {$_.RecordCount} | Select-Object -ExpandProperty LogName ; ForEach ( $l in $logs | Sort | Get-Unique ) {[System.Diagnostics.Eventing.Reader.EventLogSession]::GlobalSession.ClearLog($l)} |
File and Directory Modification
The ransomware uses the fsutil tool to redirect file system access to a different location after gaining access to compromised networks by executing the following commands:
"cmd" /C fsutil behavior set SymlinkEvaluation R2R:1 |
Indicators of Compromise
Indicator | Type | Context |
|---|---|---|
8d608d85e4785592857988c0cd749881a5e888e49e30b80ea90d214792547135 f910b2a6d84d0677cda9aefabfa4a45863ba51a8831588e3b527e8e1d3a9927c | SHA256 hash | Qilin ransomware |
C:\README-RECOVER-XXXXXXXXXX.txt | File path | Qilin ransom note |
.XXXXXXXXXX | Extension | Encrypted file extension example |
"cmd" /C vssadmin.exe delete shadows /all /quiet | Process | Volume Shadow Copy deletion and disabling of the Volume Shadow Copy (VSS) service |
"powershell" $logs = Get-WinEvent -ListLog * | Where-Object {$_.RecordCount} | Select-Object -ExpandProperty LogName ; ForEach ( $l in $logs | Sort | Get-Unique ) {[System.Diagnostics.Eventing.Reader.EventLogSession]::GlobalSession.ClearLog($l)} | Process | Clearing Windows event logs |
"cmd" /C fsutil behavior set SymlinkEvaluation R2R:1 | Process | File and directory permissions modification |
Key: Computer\HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Wallpapers\ Name: BackgroundHistoryPath0 Data: C:\Users\%USERNAME%\AppData\Local\Temp\jjAJrgQA.jpg | Registry | Registry modification to display the Qilin ransomware desktop wallpaper image |
Key: Computer\HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run Name: *zgngnt Data: "C:\Users\%USERNAME%\Desktop\Qilin.exe" --password XXXXXXXXXXXXX --no-admin --no-admin | Registry | Registry modification to achieve persistence |
http://kbsqoivihgdmwczmxkbovk7ss2dcynitwhhfu5yw725dboqo5kthfaad[.]onion | URL | TA data leak site (DLS) |
Ransomware Configuration
=== START EMBEDDED CONFIGURATION === extension_black_list: ["themepack", "nls", "diapkg", "msi", "lnk", "exe", "scr", "bat", "drv", "rtp", "msp", "prf", "msc", "ico", "key", "ocx", "diagcab", "diagcfg", "pdb", "wpx", "hlp", "icns", "rom", "dll", "msstyles", "mod", "ps1", "ics", "hta", "bin", "cmd", "ani", "386", "lock", "cur", "idx", "sys", "com", "deskthemepack", "shs", "theme", "mpa", "nomedia", "spl", "cpl", "adv", "icl", "msu", "XXXXXXXXXX"] extension_white_list: ["mdf", "ldf", "bak", "vib", "vbk", "vbm", "vrb", "vmdk", "abk", "bkz", "sqb", "trn", "backup", "bkup", "old", "tibx", "pfi", "pvhd", "pbf", "dim", "gho", "vpcbackup", "arc", "mtf", "bkf", "dr"] filename_black_list: ["desktop.ini", "autorun.ini", "ntldr", "bootsect.bak", "thumbs.db", "boot.ini", "ntuser.dat", "iconcache.db", "bootfont.bin", "ntuser.ini", "ntuser.dat.log", "autorun.inf", "bootmgr", "bootmgr.efi", "bootmgfw.efi", "#recycle", "autorun.inf", "boot.ini", "bootfont.bin", "bootmgr", "bootmgr.efi", "bootmgfw.efi", "desktop.ini", "iconcache.db", "ntldr", "ntuser.dat", "ntuser.dat.log", "ntuser.ini", "thumbs.db", "#recycle", "bootsect.bak"] directory_black_list: ["windows", "system volume information", "intel", "admin$", "ipc$", "sysvol", "netlogon", "$windows.~ws", "application data", "mozilla", "program files (x86)", "program files", "$windows.~bt", "msocache", "tor browser", "programdata", "boot", "config.msi", "google", "perflogs", "appdata", "windows.old", "appdata", "..", ".", "boot", "windows", "windows.old", "$recycle.bin", "admin$"] win_services_black_list: ["vmms", "mepocs", "memtas", "veeam", "backup", "vss", "sql", "msexchange", "sophos", "msexchange", "msexchange\\$", "wsbexchange", "pdvfsservice", "backupexecvssprovider", "backupexecagentaccelerator", "backupexecagentbrowser", "backupexecdivecimediaservice", "backupexecjobengine", "backupexecmanagementservice", "backupexecrpcservice", "gxblr", "gxvss", "gxclmgrs", "gxcvd", "gxcimgr", "gxmmm", "gxvsshwprov", "gxfwd", "sapservice", "sap", "sap\\$", "sapd\\$", "saphostcontrol", "saphostexec", "qbcfmonitorservice", "qbdbmgrn", "qbidpservice", "acronisagent", "veeamnfssvc", "veeamdeploymentservice", "veeamtransportsvc", "mvarmor", "mvarmor64", "vsnapvss", "acrsch2svc", "(.*?)sql(.*?)"] |
Data Leak Site
The ransom note contains a data leak site (DLS) that, when accessed, displayed the following page, self-identifying the group as Qilin:
TOR DLS: ijzn3sicrcy7guixkzjkib4ukbiilwc3xhnmby4mcbccnsd7j2rekvqd[.]onion

Figure 10. Tor DLS
Detection Mechanisms
Arete Bloktd℠ Rules
Arete Bloktd℠ includes expert threat analysis, crafted threat hunting queries, and active deployment of preventive rules for adversarial behaviors on SentinelOne® protected assets monitored by Arete.
SentinelOne® S1QL 2.0 Query Syntax
Qilin Ransomwareendpoint.os = 'windows' and event.category = 'process' and event.type = 'Process Creation' and src.process.cmdline matches '\\.exe {1,4}--password {1,4}[a-zA-Z0-9-]{32} {1,4}--no-admin' Note: This threat hunting query may need to be tuned for your specific network environment. |
|---|
Yara
rule Qilin_ransomware_executable strings: condition: |
|---|
Recommended Mitigations
Utilize an endpoint detection and response (EDR) solution with the capability to halt detected processes and isolate systems on the network based on identified conditions.
Block any known attacker C2s in the firewall.
Implement multi-factor authentication on RDP and VPN to restrict access to critical network resources.
Eliminate unnecessary RDP ports exposed to the internet.
Block a high number of SMB connection attempts from one system to others in the network over a short period of time.
Perform periodic dark web monitoring to verify if data is available for sale on the black market.
Perform penetration tests.
Periodically patch systems and update tools.
Monitor connections to the network from suspicious locations.
Monitor downloads and uploads of files to file-sharing services outside standard work hours.
Monitor file uploads from domain controllers to the internet.
Monitor network scans from uncommon servers (e.g., RDP server).
Organizations can find the full list of US government-recommended ransomware prevention and mitigation guidance here: https://www.cisa.gov/stopransomware/ransomware-guide.
Arete Advisors, LLC makes no claims, promises or guarantees about the accuracy, completeness, or adequacy of the contents of this report and expressly disclaims liability for errors and omissions in the content. Neither Arete Advisors, LLC, nor its employees and contractors make any warranty, express or implied or statutory, including but not limited to the warranties of non-infringement of third-party rights, title, and the warranties of merchantability and fitness for a particular purpose, with respect to content available from this report. Arete Advisors, LLC assumes no liability for any direct, indirect, or any other loss or damage of any kind for the accuracy, completely, or usefulness of any information, product, or process disclosed herein, and does not represent that the use of such information, product, or process would not infringe on privately owned rights. Information contained in this report is provided for educational purposes only and should not be considered as legal advice.
Article
Critical Vulnerability in Progress Kemp LoadMaster Exploited
Researchers have identified active exploitation of CVE-2026-8037, a critical unauthenticated remote code execution vulnerability affecting Progress Kemp LoadMaster. The vulnerability affects LoadMaster GA versions 7.2.63.1 and earlier and LTSF versions 7.2.54.17 and earlier and can allow a remote adversary to execute commands on an affected appliance without valid credentials when the vulnerable API is exposed. Progress has released updates addressing CVE-2026-8037 and CVE-2026-33691, a separate Web Application Firewall security control bypass, in GA 7.2.63.2 and LTSF 7.2.54.18.
The exploitation of this vulnerability reflects a broader trend of threat actors targeting internet-facing enterprise technologies. For example, Progress MOVEit Transfer experienced significant scanning and exploitation activity in 2025 involving CVE-2023-34362 and CVE-2023-36934, as well as the 2023 exploitation of CVE-2023-34362 by the Cl0p ransomware group for large-scale data theft and extortion. More recently, CISA confirmed the exploitation of SonicWall SMA1000 vulnerabilities, CVE-2026-15409 and CVE-2026-15410, by ransomware groups. Collectively, these incidents demonstrate the continued targeting of perimeter-facing enterprise technologies as high-value entry points into corporate environments.
What’s Notable and Unique
Public exploit research, observed exploitation attempts, and CISA KEV inclusion indicate that CVE-2026-8037 has progressed into an active operational threat, increasing urgency for organizations with exposed and unpatched LoadMaster systems.
Internet-facing infrastructure can be rapidly identified through automated scanning, enabling threat actors to quickly identify vulnerable systems and capitalize on newly disclosed vulnerabilities and publicly available exploit techniques.
Analyst Comments
CVE-2026-8037 is significant not only for its severity but also because it affects infrastructure positioned between the internet and critical enterprise applications. The combination of external exposure, unauthenticated exploitation, and public exploit research lowers the barrier for threat actors seeking initial access, and the broader threat landscape reinforces this concern. The exploitation of Progress MOVEit by Cl0p, continued scanning activity against MOVEit, and recent ransomware exploitation of SonicWall SMA1000 vulnerabilities demonstrate sustained adversarial interest in perimeter-facing enterprise technologies. These incidents indicate that such infrastructure should be treated as high-value assets within enterprise security programs.
Sources
Surge in MOVEit Transfer Scanning Could Signal Emerging Threat Activity
LoadMaster Critical Security Bulletin – June 2026 – (CVE-2026-8037, CVE-2026-33691)
Enterprise Tech In, Shell Out (Progress Kemp LoadMaster Uninitialized Heap to Pre-Auth RCE CVE-2026-8037)
CISA: SonicWall SMA1000 flaws now exploited by ransomware gangs
Podcast
Blockchain Unmasked: The Role of Cryptocurrency in Cybercrime and Threat Intelligence
In this episode of Bytes of Insight, host Vinny Sakore sits down with John Morrissey, Arete’s Director of Cryptocurrency Operations and Sanctions Compliance, and Trenton Howard, Arete’s Lead Threat Intelligence Consultant, to discuss cryptocurrency and blockchain technology. They explore the impact of cryptocurrency on both innovation and cybercrime, threat actors’ use of the blockchain for ransom payments, and Arete’s patent-pending Compliance and Sanctions Analysis Process.
Article
ClickFix Evolves in Server-Side Polymorphic Malware Delivery Campaigns
The ClickFix social engineering technique has significantly evolved from a relatively simple malware delivery mechanism into a highly sophisticated, evasive attack framework. Initially relying on straightforward PowerShell downloaders and disk-based payloads, the campaign now employs fileless execution, advanced obfuscation techniques, and server-side polymorphism to evade traditional security controls.
What’s Notable and Unique
ClickFix primarily relies on social engineering, as victims are presented with fake CAPTCHA verification pages that imitate trusted services such as Cloudflare or Google reCAPTCHA. Users are instructed to copy and execute a PowerShell command, believing they are completing a legitimate verification process. Instead, the command initiates the malware infection chain.
To bypass traditional security tools, threat actors transitioned to fileless techniques. Instead of downloading scripts directly to disk, newer variants execute malicious code entirely in memory. The most notable recent advancement in ClickFix is the adoption of server-side polymorphism. Unlike traditional malware that delivers a static payload, the threat actor's server dynamically generates unique payloads for each victim request. This approach undermines signature-based detection methods because each delivered payload appears unique, preventing defenders from relying solely on file hashes or static indicators.
The campaign was observed beginning around March 25, 2026, with a significant increase in activity thereafter, indicating that the techniques are proving effective against many organizations' defenses.
Analyst Comments
ClickFix social engineering campaigns continue to evolve in 2026, becoming more sophisticated and expanding across multiple operating systems. Organizations should focus on behavioral detection, browser isolation, endpoint monitoring, and user awareness training rather than relying solely on indicators such as hashes or blocklists. The campaign's use of fake CAPTCHA prompts also reinforces the importance of educating users never to execute commands from websites.
Sources
The Evolution of ClickFix: From Cleartext to Server Side Polymorphism



