EXPLORE

Report

Threat Actor Spotlight: BlackSuit Ransomware

Arete Analysis

Tips

Download The Report

Executive Summary

Since May 2023, Arete’s Incident Response (IR) team has responded to multiple BlackSuit ransomware engagements against organizations in the healthcare, financial services, manufacturing, professional services, public service, entertainment, and retail sectors. This spotlight explores the ransomware behavior observed, statistics from IR engagements, and background information on the threat actor. Finally, we discuss security recommendations to better defend against this evolving cyber threat and mitigate the risk of financial and reputational losses arising from these incidents.

Incident Response Data on BlackSuit Ransomware

The information below is based on BlackSuit incidents investigated by Arete since May 2023. Our IR and teams work together to analyze key data points during every ransomware engagement and form real-time threat actor (TA) insights.

  • Arete has investigated dozens of engagements involving BlackSuit.

  • We have been extremely successful in negotiating discounted ransoms with this TA.

  • The highest observed ransom demand is around $18 million.

  • The average initial demand is around $2.5 million.

  • The average ransom payment facilitated is around $500,000.

  • Commonly observed methods of intrusions include remote desktop protocol (RDP), virtual private network (VPN), and firewall vulnerabilities.

  • Tools observed during the investigations include CobaltStrike, WinRAR, PUTTY, Rclone, Advanced IP Scanner, Network Scanner, Mimikatz, and GMER.

  • A commonly observed ransom note filename is readme.blacksuit.txt.

  • In some instances, backups were encrypted or deleted, while in others, backups were used for restoration.

Background

The information about the BlackSuit threat actor group in this section was shared in Arete’s 2024 Q1 Crimeware Report.

The most notable newcomer in Q1 was BlackSuit, the third most active group of Q1. Although Arete first observed BlackSuit ransomware operating in May 2023, it only accounted for less than a half percent of the total engagements in 2023. The group significantly increased its activity in Q1 2024, and there were more BlackSuit engagements in February 2024 alone than in all of 2023. BlackSuit operates as a private group without affiliates, targeting both Windows and Linux users and utilizing a double extortion method of stealing and encrypting sensitive data on a victim’s network.

BlackSuit: A Continuation of Royal Ransomware?

The BlackSuit ransomware payload has significant code overlap with Royal ransomware, and the Cybersecurity and Infrastructure Security Agency (CISA) and the FBI believe BlackSuit to likely be a rebranding or spinoff variant of Royal. While BlackSuit could be using the same developer or code with slight modifications, Arete also observed language used by BlackSuit in ransom negotiations identical to previous engagements with Royal, which lends to the assessment that the group might be a rebrand or offshoot. Regardless, BlackSuit’s emergence demonstrates that although names may change, threat actors will find ways to adapt and evolve their operations.

Figure 1. Language from two separate BlackSuit TOR chats (Source: Arete)

Figure 2. Identical language from two separate Royal TOR chats (Source: Arete)

Technical Analysis

Malware analysis revealed that BlackSuit ransomware:

  • Supports multiple command-line arguments.

  • Encrypts files on the system and mounted shares.

  • Adds the following extension to encrypted files: .blacksuit (e.g., file.docx.blacksuit).

  • Creates a ransom note with the following filename: readme.blacksuit.txt.

  • Self-identifies the group as BlackSuit in the ransom note.

  • References a data leak site in the ransom note that, when accessed, self-identifies the group as BlackSuit.

  • Kills a list of processes and services.

  • Maintains a list of whitelisted files and directories to make sure it will not render the system unusable, preventing recovery when running a decryptor.

  • Attempts to prevent system recovery by deleting the system’s volume shadow copies.

  • Creates the following mutex during execution: WLm87eV1oNRx6P3E4Cy9.

Execution Pattern/Arguments

BlackSuit ransomware needs command line arguments to execute and encrypt files in the system. Command line arguments supported:

Command line argument
Description

-id [32-byte characters]

Ransomware ID

-size

Invoked with drag and drop

-ep

Number that represents the percentage of the file that will be encrypted

-path [target_directory_path]

Used to specify a target directory to encrypt

-localonly

Encrypt only the local system

-networkonly

Encrypt only shared volumes/directory

-aavm

Encrypt all files

The ransomware will not execute in the system without the “–id” argument followed by a 32-character value that is unique in each engagement and present in the ransom note TOR URL. Portion of the data in the ransom note that contains the ID:

All your files will be decrypted, your data will be reset, your systems will stay in safe. Contact us through TOR browser using the link:

http://c7jpc6h2ccrdwmhofuij7kz6sr2fg2ndtbvvqy4fse23cf7m2e5hvqid[.]onion/?id=[32-characters]

Execution of ransomware to encrypt files:

blacksuit.exe -id [32-characters]

The ransomware developer coded the logic to allow configuration of the 32-character value in the command line during execution. This same victim-specific 32-character string value is then added to the ransom note URL used for negotiations. Due to this implementation in the ransomware code, threat researchers can execute the ransomware without knowing the 32-character string value, as any value of this type can be used to execute the malicious code. In analyzing Royal ransomware samples, Arete found a similarity in that any 32-character value can be supplied to execute the ransomware, and the value is also added to the ransom note TOR chat URL.

Example of how the ransom note content looks with a randomly supplied string (e.g., blacksuit.exe -id 7777777777777777777777777777777):

All your files will be decrypted, your data will be reset, your systems will stay in safe. Contact us through TOR browser using the link:

http://c7jpc6h2ccrdwmhofuij7kz6sr2fg2ndtbvvqy4fse23cf7m2e5hvqid[.]onion/?id=77777777777777777777777777777777777777


Obfuscated Files or Information: Software Packing

Most of the strings in the ransomware are encoded. The encoded strings are hardcoded and decoded at runtime. Every encoded string has its own decoding loop:

Figure 3. Encoded strings hardcoded

Figure 4. String decoding loop


Some relevant strings decoded in memory:

Global\\\WLm87eV1oNRx6P3E4Cy9
readme.blacksuit.txt
\windows\
svchost.exe
explorer.exe
-size
cmd.exe /c vssadmin delete shadows /all /quiet

-ep
-path
-localonly
-networkonly
-aavm
Microsoft Enhanced RSA and AES Cryptographic Provider


Obfuscated Files or Information: Dynamic API Resolution

To avoid static or other defensive analysis, the ransomware uses dynamic API resolution to conceal malware characteristics and functionality. The ransomware initially decrypts DLL names, then loads the APIs. Hardcoded encoded DLL names are shown below:

Figure 5. Encoded DLL names

Figure 6. DLL name decoding loop

DLL names decoded at runtime:

shell32.dll
user32.dll
advapi32.dll
ws2_32.dll
shlwapi.dll

rstrtmgr.dll
ntdll.dll
Crypt32.dll
iphlpapi.dll


Stop Services and Processes

Before file encryption, the ransomware terminates a list of known running processes and services to encrypt as many files as possible. BlackSuit ransomware utilizes the Windows Restart Manager to terminate any process using files other than explorer.exe or a critical process.

Sequence of Windows Restart Manager APIs used by the ransomware:

RmStartSession

Starts the Restart Manager session.

RmRegisterResources

Registers resources, in this case the targeted filename

RmGetList

Determine which processes or services are using the registered resource (file)

RmShutdown

Shuts down any identified process or service using the registered resource

RmEndSession

Closes the Restart Manager session.

The ransomware also uses Windows native CreateToolhelp32Snapshot, Process32FirstW, and Process32NextW APIs to enumerate processes in the system.


File and Directory Exclusions

The ransomware excludes system-related files and folders, ransomware-related files, and whitelisted extensions during encryption.

Excluded file extensions:

.com .ani .scr .drv .hta .rom .bin .msc .ps1 .shs .adv .msu .prf .bat .idx .mpa .cmd .msi .mod .ocx .ics .386 .sys .rtp .wpx .msp .cab .ldf .lnk .cur .nls .hlp .key .ico .exe .icns .lock .theme .diagpkg .diagcab .nomedia .diagcfg .msstyles .themepack .blacksuit .deskthemepack

Excluded files and directories:

“msocache”, “intel”, “$recycle.bin”, “windows”, “windows.old”, “mozilla firefox”, “$WinREAgent”, “boot”, “google”, “perflogs”, “system volume information”, “appdata”, “tor browser”, “$windows.~ws”, “application data”, “$windows.~bt”, “mozilla”, “readme.blacksuit.txt”


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.

With the CreateProcessW function, the ransomware deletes volume shadow copies before file encryption by executing the following command:

cmd.exe /c vssadmin delete shadows /all /quiet

Code in the ransomware showing this operation (the EAX register contains the kernel32.CreateProcessW address):

Figure 7. Create process call to delete volume shadow copies


System Network Connections Discovery

BlackSuit ransomware can enumerate network-mounted shares by scanning the network interfaces.

Data Encrypted for Impact

The ransomware initially finds available drives and loads the files one by one using the Windows API FindFirstFileW and FindNextFileW. It then uses OpenSSL AES keys to encrypt the files and adds the extension .blacksuit to the encrypted file name.

Figure 8. Windows native CryptEncrypt API call to encrypt the data


Public key:

—–BEGIN RSA PUBLIC KEY—–

MIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIICCgKCAgEA+O9FGkh466oxay/9u//rycLpGqFwcUSQIy0d27cnpRqq1W4De/boeoJC/HJqkr3WaEqr2JHgjSQcMimTxy8d3NLJT7M3uTVaxXD3Bck83ns5S/WhiF5tQGHtAGetGv8gXYSq/bm6HAlWBMBaOvv4of7ov7/cTAl1pwwgnaYzws4q6C9Q5zwmcU7DFcOohyVqBu/2svUlvtfMJGzYVeUJSUF6E2NMhClxddDLr32wCuoZ567uMBLQB2e5DUTkplR1OdVeyWyxhAXJSjQ5T9LpwuUHNm89nuo25slwlUx2m5a2k6wn2husXhXj+NRN/c2F3zh2qkcgs318XY8es1r3UgIBdCYMMGKsZ0DxKJZ1fq4nU93c+aP0qFBawmYhgIZq6MBYrG23LGbJPZvcC8pkyJrT51ygthCVPtpThqlthdqzqnV+7gPaf/XRwHeLkqawPhe1omd9m7gSuFwIREUe2MW1qZ7p3Nzhf8ZF4/YN7PSN1m6Ve5HS1MgnR9cbj655Jt3lqgW6rillrP+DbdrnjYo7yz2CsxSL3vKVtzcDzsbEFPkAFDyfSrYVxMYCEUJ8jHlctrNo+UiuZTT0O9dbwoGfCSrg8w+V0h8pYaiGnVwwGGkQbLgBAvz+iOOyElbZDLEPJxZ1+ipYzADufQSh8RHh/nXpWirlzQNH7oqrA0fUCAwEAAQ==

—–END RSA PUBLIC KEY—–

The ransomware encrypts files, adds the .blacksuit extension at the end of the encrypted files, and adds the following bytes at the end of the file (“??” represents variable bytes):

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ?? 00 00 00 ??

00 00 00

Figure 9. “.blacksuit” extension added to the encrypted files

Figure 10. Padding bytes in encrypted files


Upon successful execution, the ransomware creates ransom notes with the file name readme.blacksuit.txt.

Figure 11. Screenshot of BlackSuit ransom note


Modify Registry

The ransomware did not perform any registry key modification.

Mutex

The mutex is the fundamental tool for managing shared resources between multiple threads or processes. Typically, ransomware uses a mutex to avoid reinfecting the victim system and causing multiple layers of encryption. The ransomware creates the following mutex value: “WLm87eV1oNRx6P3E4Cy9”.

Figure 12. 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.

Indicators of Compromise

Indicator
Type
Context

f1684fb118d4d8fc56653fcc49e12a659b64c4459ba037fa94f21783235cc6ba
dede96fd44c0f78eb79ceb63b898874e8922efc59d8bfb9f86505b1992bc00a3
79ab73a0e9dd8eac045c00fd1bd172a7f359588901f93c83e6740157eb21e7df
d96ff4b3e188f7ff96ed28c1381a6318dd76bb1fbd6ca02c6ab0236e1c7f35aa

SHA256 hash

BlackSuit ransomware

C:\readme.blacksuit.txt

File path

BlackSuit ransom note

.blacksuit

Extension

Encrypted files extension

vssadmin delete shadows /all /quiet

Process

Volume Shadow Copy deletion

WLm87eV1oNRx6P3E4Cy9

Mutex

Mutex value object created by the BlackSuit ransomware

Any 32-character string

Password

Command line argument needed to properly execute the ransomware. The ransomware developer doesn’t validate it

c7jpc6h2ccrdwmhofuij7kz6sr2fg2ndtbvvqy4fse23cf7m2e5hvqid [.]onion
weg7sdx54bevnvulapqu6bpzwztryeflq3s23tegbmnhkbpqz637f2yd[.]onion

URL

TA data leak site (DLS)


Data Leak Site

The ransom note contains a data leak site (DLS) that displayed the following page, self-identifying the group as BlackSuit:

Figure 13. TOR DLS: c7jpc6h2ccrdwmhofuij7kz6sr2fg2ndtbvvqy4fse23cf7m2e5hvqid[.]onion

Figure 14. TOR DLS: weg7sdx54bevnvulapqu6bpzwztryeflq3s23tegbmnhkbpqz637f2yd[.]onion


Detection Mechanisms

Custom Detections and Blocking with Arete’s Arete Bloktd℠


Yara


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 provides data-driven cybersecurity solutions to transform your response to emerging cyber threats. Learn more.


References

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 
net1 start vss 
net start vss 
vssadmin.exe delete shadows /all /quiet 
net stop vss 
net1 stop vss 
wmic service where name='vss' call ChangeStartMode Disabled 

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.
Encrypted files have new extension.

-- Compromising and sensitive data

We have downloaded compromising and sensitive data from your system/network.
Our group cooperates with the mass media.
If you refuse to communicate with us and we do not come to an agreement, your data will be reviewed and published on our blog and on the media page (https://wikileaks2.site/)

Blog links:
http://kbsqoivihgdmwczmxkbovk7ss2dcynitwhhfu5yw725dboqo5kthfaad[.]onion
http://ijzn3sicrcy7guixkzjkib4ukbiilwc3xhnmby4mcbccnsd7j2rekvqd[.]onion

Data includes:
- Employees personal data, CVs, DL , SSN.
- Complete network map including credentials for local and remote services.
- Financial information including clients data, bills, budgets, annual reports, bank statements.
- Complete datagrams/schemas/drawings for manufacturing in solidworks format
- And more...

-- Warning

1) If you modify files - our decrypt software won't able to recover data
2) If you use third party software - you can damage/modify files (see item 1)
3) You need cipher key / our decrypt software to restore you files.
4) The police or authorities will not be able to help you get the cipher key. We encourage you to consider your decisions.

-- Recovery

1) Download tor browser: https://www.torproject[.]org/download/
2) Go to domain
3) Enter credentials

Please note that communication with us is only possible via the website in the Tor browser, which is specified in this note.
All other means of communication are not real and may be created by third parties, if such were not provided in this note or on the website specified in this note.

-- Credentials

Extension: XXXXXXXXXX
Domain: [removed_by_analyst]
login: [removed_by_analyst]
password: [removed_by_analyst]

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
"cmd" /C fsutil behavior set SymlinkEvaluation R2L:1 

Indicators of Compromise

Indicator

Type

Context

8d608d85e4785592857988c0cd749881a5e888e49e30b80ea90d214792547135

f910b2a6d84d0677cda9aefabfa4a45863ba51a8831588e3b527e8e1d3a9927c

650a03c40c45eef3590058c37de8ea2e978c9c69f289390b2ab89be3910549fb

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
"cmd" /C net stop vss
"cmd" /C wmic service where name='vss' call
ChangeStartMode Disabled

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 
"cmd" /C fsutil behavior set SymlinkEvaluation R2L: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
http://ijzn3sicrcy7guixkzjkib4ukbiilwc3xhnmby4mcbccnsd7j2rekvqd[.]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$"]
white_symlink_dirs: []
white_symlink_subdirs: ["ClusterStorage"]
process_black_list: ["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"]

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(.*?)"]
accounts: []
step: 0
skip: 0
fast: 0
n: 0
p: 1
company_id: "XXXXXXXXXX"
=== END EMBEDDED CONFIGURATION ===

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 Ransomware

endpoint.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
{
    meta:
        author = "areteir.com"
        description = "Arete Bloktd detected the Qilin ransomware executable."
        target = "Windows systems"
        file_type = "exe"
        copyright = "Copyright © 2026 by Arete Advisors, LLC."
        distribution = "No re-distribution without Arete Advisors, LLC consent."
       

    strings:
        $str1 = "public_rsa_pem" ascii nocase
        $str2 = "private_rsa_pem" ascii nocase
        $str3 = "directory_black_list" ascii nocase
        $str4 = "file_black_list" ascii nocase
        $str5 = "file_pattern_black_list" ascii nocase
        $str6 = "process_black_list" ascii nocase
        $str7 = "win_services_black_list" ascii nocase
        $str8 = "company_id" ascii nocase
        $str9 = "accounts" ascii nocase
        $api1 = "BCryptGenRandom" fullword
        $api2 = "CreateToolhelp32Snapshot" fullword
        $api3 = "FindFirstFileW" fullword
        $api4 = "FindNextFileW" fullword
 

    condition:
        ( (uint16(0) == 0x5A4D) and (uint32(uint32(0x3C)) == 0x00004550) ) and
        (((7 of ($str*)) and (all of ($api*))) or (all of ($str*)))
}

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