Payouts King Ransomware — BlackBasta-Affiliate RaaS Evades EDR via Direct System Calls, ntdll Export-Table Walking, and SetFileInformationByHandle Rename Evasion (Zscaler ThreatLabz)
Payouts King Ransomware (TL-2026-0692), also tracked as Payouts King RaaS, is a high-severity ransomware operation, first published 2026-06-06. It is attributed to Payouts King with medium confidence, affects Microsoft Windows, maps to 18 MITRE ATT&CK techniques (T1005, T1027, T1027.007), and is covered by 9 detection rules and 15 indicators of compromise.
Key facts for TL-2026-0692
- Threat ID
- TL-2026-0692
- Also known as
- Payouts King RaaS
- Severity
- HIGH
- Status
- ACTIVE
- Category
- RANSOMWARE
- First published
- 2026-06-06
- Last reviewed
- 2026-06-06
- Attribution
- Payouts King
- Attribution confidence
- MEDIUM
- Motivation
- FINANCIAL
- Target sectors
- manufacturing, healthcare, construction, financial, professional-services
- Target regions
- North America, Europe
- Detection rules
- 9
- Indicators of compromise
- 15
Malware and tooling in Payouts King Ransomware
Malware and tooling: payoutsking, TOX messenger contact
Zscaler ThreatLabz published a binary-level analysis of Payouts King, a data-theft-driven ransomware operation run by former BlackBasta affiliates (BlackBasta disbanded Feb 2025; Payouts King first observed April 2025). The payload evades AV/EDR by issuing low-level direct system calls — walking the ntdll export table for Zw-prefixed functions and resolving syscall stubs via a custom CRC32 (polynomial 0xBDC65592) rather than hooked Windows APIs. It targets 131 hardcoded checksum-matched AV/EDR processes, builds and XOR-decrypts strings on the stack at runtime, and renames encrypted files via SetFileInformationByHandle (FileRenameInfo) instead of MoveFile to bypass rename heuristics. Encryption is hybrid RSA-4096 + AES-256-CTR using statically linked OpenSSL, applied selectively to maximize impact and minimize detection.
How Payouts King Ransomware works
Payouts King is a double-extortion ransomware operation that ThreatLabz attributes to former BlackBasta affiliates. BlackBasta emerged in February 2022 as a Conti successor and operated until February 2025, when leaked internal chat logs forced the brand to disband. Its initial access brokers continued operations, and Payouts King first appeared in April 2025. By early 2026 the group had claimed 50+ named victims, with the United States the largest share followed by Germany, France, and Spain. Initial access mirrors historic BlackBasta tradecraft: email spam bombing, Microsoft Teams impersonation of IT help desk, and abuse of Quick Assist for remote access.
The core of this analysis is the Windows payload's EDR-evasion engineering. Rather than calling documented Windows APIs (which security products hook in user mode), Payouts King resolves and invokes native NT syscalls directly. At runtime it walks the loaded ntdll module's export table, enumerating function names beginning with the 'Zw' prefix, and computes a custom CRC32 checksum (polynomial 0xBDC65592, per-value FNV1 seed) for each name, matching against expected DWORD constants to locate the functions it needs — including ZwQueryInformationFile (0x806e69a7), ZwQueryInformationProcess (0x1993a634), ZwOpenProcess (0x58ad11ee), ZwTerminateProcess (0x469424d5), ZwOpenFile (0x28a29ebf), and ZwQuerySystemInformation (0xa0595508). This yields a private syscall table that bypasses user-mode API hooks.
Process termination uses the same checksum technique: the binary carries 131 hardcoded DWORD checksum values representing AV/EDR and security tooling. It enumerates running processes via ZwQuerySystemInformation, checksums each process name, and terminates matches via ZwOpenProcess + ZwTerminateProcess. Documented targets span CrowdStrike (csfalconservice.exe), SentinelOne (sentinelagent.exe, sentinelctl.exe, sentinelui.exe), Microsoft Defender (MsMpEng.exe, MsSense.exe), Kaspersky (avp.exe, avpui.exe), Norton, McAfee, Cylance, Cybereason, Deep Instinct, F-Secure, and 100+ additional products.
String obfuscation defeats static signatures and precomputed hash tables: strings and their XOR keys are stored as stack-based arrays of QWORDs, constructed and decrypted in-place at runtime, leaving no plaintext in the on-disk image. The custom CRC32 with unique FNV1 seeds per value further frustrates hash-database lookups.
Encryption is hybrid: a per-file pseudorandom 32-byte AES-256 key and 16-byte IV encrypt file data in CTR mode using statically linked OpenSSL; the per-file parameters are then RSA-4096-encrypted and appended as a 487-byte trailer. The encrypted trailer carries magic bytes 'CRPT' (0x50545243), an encryption-type field (0x825456 for AES), original/encrypted sizes, and a block count (1 = full encryption, 0xd = 13-block partial). Selective encryption: files matching a target extension list or under 10MB are fully encrypted; larger files are split into 13 blocks with ~50% of each block encrypted, controllable via the '-percent' CLI parameter. Executables and system artifacts (.exe, .dll, .sys, .bat, .lnk, .msi) and system directories (Windows, Program Files, Recovery, $Recycle.Bin) are excluded to preserve host stability.
Encrypted files receive the .ZWIAAW extension, with .esVnyj used as a temporary backup during processing. The ransom note readme_locker.txt is dropped to the desktop only when the '-note' CLI flag is supplied; it directs victims to a TOX contact and a Tor-hosted data leak site that publishes victim names with countdown timers and progressive data disclosure. Pre-encryption, the malware performs anti-recovery actions: shadow copy deletion, Windows event log clearing, and recycle bin emptying.
MITRE ATT&CK techniques used in TL-2026-0692
Collection
Defense Evasion
T1027 Obfuscated Files or Information; T1027.007 Dynamic API Resolution; T1036 Masquerading; T1070.004 Indicator Removal: File Deletion
Discovery
T1057 Process Discovery; T1082 System Information Discovery; T1083 File and Directory Discovery
Execution
command-and-control
Impact
T1486 Data Encrypted for Impact; T1489 Service Stop; T1490 Inhibit System Recovery
Initial Access
T1566 Phishing; T1566.003 Spearphishing via Service
Exfiltration
T1567 Exfiltration Over Web Service
defense-impairment
T1685 Disable or Modify Tools; T1685.005 Clear Windows Event Logs
Affected products and versions in Payouts King Ransomware
- Microsoft — Windows
Vulnerable versions: Windows 10; Windows 11; Windows Server 2016/2019/2022
Remediation for Payouts King Ransomware
Immediate actions
- Hunt for processes resolving syscalls by walking the ntdll export table (Zw* enumeration) and invoking direct syscalls from non-ntdll memory regions
- Alert on mass file renames via SetFileInformationByHandle/FileRenameInfo, especially to the .ZWIAAW or .esVnyj extensions
- Block and alert on vssadmin/wmic shadow copy deletion, wevtutil event-log clearing, and recycle bin emptying preceding bulk file modification
- Isolate hosts exhibiting termination of multiple AV/EDR processes in rapid succession
Workarounds
- Disable Quick Assist via policy to remove the observed remote-access vector
- Train help desk and users against Microsoft Teams IT-impersonation and email spam-bombing social engineering
Longer-term hardening
- Deploy EDR with kernel-level/ETW telemetry that detects direct syscall invocation independent of user-mode API hooks
- Enforce tamper protection and self-defense on AV/EDR agents to resist process termination
- Restrict and monitor Quick Assist and other remote-assistance tooling; disable where not required
- Implement application allow-listing and immutable/offline backups with tested restore
Timeline of Payouts King Ransomware
- BlackBasta ransomware emerges as a successor to Conti, rising to prominence over three years of operation.
- BlackBasta internal chat logs are leaked online; the group disbands and shutters its brand while affiliates continue operations.
- Payouts King ransomware first observed, operated by former BlackBasta affiliates as a data-theft-driven extortion operation.
- ThreatLabz observes ransomware activity consistent with prior BlackBasta initial access brokers (spam bombing, Teams impersonation, Quick Assist abuse).
- Payouts King claims 50+ named victims on its Tor data leak site; United States most-affected, followed by Germany, France, and Spain.
- Zscaler ThreatLabz publishes binary-level analysis detailing direct-syscall EDR evasion, 131-process kill list, stack-built string decryption, and SetFileInformationByHandle rename evasion.
Sources cited for Payouts King Ransomware
- Payouts King Takes Aim at the Ransomware Throne — Zscaler ThreatLabz
- Payouts King Ransomware Evades EDR With Obfuscation and Direct System Calls — Cyber Security News
- Payouts King Emerges: New Ransomware Operation Tied to Ex-BlackBasta Members — GBHackers
- Payouts King Ransomware Bypasses EDR via Obfuscation and Direct Syscalls — GBHackers
- Threat Actor Deep Dive: Payouts King — Surefire Cyber
- Payouts King Takes Aim at the Ransomware Throne — Security Boulevard
Threats related to Payouts King Ransomware
- Edgecution: Payouts King Initial Access Broker Deploys Malicious Microsoft Edge Extension with Embedded Python Backdoor
- GOLD ENCOUNTER / Payouts King Ransomware Campaign Targeting Business Managers: 351 Victims Across 334 Organizations
- Payouts King Ransomware Uses QEMU Virtual Machines to Bypass EDR and Endpoint Security Controls
- Payload Ransomware — Babuk-Derivative ChaCha20 + Curve25519 ECDH Per-File Encryption Targeting Windows and ESXi
Detection coverage for TL-2026-0692
As of 2026-06-06, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-0692 across Splunk SPL, Microsoft KQL and Sigma, covering 15 indicator(s) of compromise. The whole corpus is readable without an account; a free account unlocks full detection query text in Splunk SPL, Microsoft KQL and Sigma; paid tiers add raw indicator values, correlation and the MCP server. Threadlinqs MCP server · View plans.