Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
Back to malware
MalwareRansomware

Payload Ransomware

Payload Ransomware is a Windows-focused file-encrypting ransomware observed by CYFIRMA in underground forums and described in a 2026-03-05 report. It appends the ".payload" extension to encrypted files and drops a ransom note named "RECOVER_payload.txt." The malware is described as operating as double-extortion ransomware, claiming data exfiltration and threatening public disclosure, and directs victims to a Tor-based negotiation portal while offering limited free decryption as proof.

Its behavior includes avoiding critical system directories and executable file types to preserve system stability, deleting shadow copies to inhibit recovery, clearing Windows event logs to reduce forensic visibility, disabling security monitoring via in-memory patching, terminating backup services and productivity applications, enumerating network shares to enable broader encryption impact, and using multi-threaded execution for speed. The report states it selects encryption routines based on processor capabilities and uses ChaCha20 for file encryption with Curve25519 for key exchange. It also relaunches itself in hidden mode and uses NTFS alternate data streams for self-deletion.

High-confidence ATT&CK mappings explicitly cited in the content include T1486 (Data Encrypted for Impact), T1490 (Inhibit System Recovery), and T1070.004 (File Deletion). A related detection analytic referenced in the content is a Sigma rule for shadow copy deletion using Windows utilities such as vssadmin, wmic, diskshadow, and wbadmin. No specific threat actor attribution, victim sector focus, or concrete IOCs beyond the ransom note filename and ".payload" extension are provided in the content.

Share:
For your environment

Hunt this family in your stack

Mallory pivots from this family to the IOCs, detections, and named campaigns that touch your stack, and pages you when something new lands.

MITRE ATT&CK

Techniques & procedures

28 distinct techniques documented for this family, organized by ATT&CK tactic.

Execution

4 techniques
T1059.003Windows Command ShellEvidence1

Here we have a very interesting command: /c vssadmin.exe delete shadows /all /quiet. The /c switch is very likely relevant to cmd.exe /c syntax that starts a command.

T1106Native APIEvidence2

It also uses direct Windows NT API calls rather than standard user-mode functions, helping it bypass security tools that monitor higher-level activity.

T1129Shared ModulesEvidence1

"Execution T1129 Shared Modules"

T1569System ServicesEvidence1

The binary stops services via the SCM API and kills processes via toolhelp snapshots.

Privilege Escalation

1 technique
T1055Process InjectionEvidence1

"Privilege Escalation T1055 Process Injection" and "Defense Evasion T1055 Process Injection"; also listed for FishMonger tradecraft.

Stealth

8 techniques
T1027.002Software PackingEvidence1

"Defense Evasion T1027.002 Obfuscated Files or Information: Software Packing"

T1027.007Dynamic API ResolutionEvidence1

This method is called Dynamic API resolution. The goal of this is to not show all the suspicious initial imports in the IAT, so it looks them up at runtime to evade detection.

T1055Process InjectionEvidence1

"Privilege Escalation T1055 Process Injection" and "Defense Evasion T1055 Process Injection"; also listed for FishMonger tradecraft.

T1070.001Clear Windows Event LogsEvidence3

Before encryption begins, it... clears Windows Event Logs... The ransomware loads the Windows event log API at runtime and clears every available channel, including Application, System, and Security logs.

T1070.004File DeletionEvidence4

Before encryption begins, it deletes Windows shadow copies...

T1202Indirect Command ExecutionEvidence1

"Defense Evasion T1202 Indirect Command Execution"

T1497.001System ChecksEvidence1

Anti-debugging reads /proc/self/status and checks TracerPid: for a non-zero value.

T1564.004NTFS File AttributesEvidence1

Alternate Data Streams - Adversaries may use NTFS file attributes to hide their malicious data in order to evade detection.

Discovery

6 techniques
T1057Process DiscoveryEvidence3

Here we have some process names. Usually, before the actual encryption it terminates processes related to documents, SQL databases to ensure everything can be encrypted properly.

T1082System Information DiscoveryEvidence2

The Linux build is a 39 KB stripped ELF targeting ESXi hypervisors. It links libxml2.so.2 and parses /etc/vmware/hostd/vmInventory.xml using XPath to locate VM disk paths for targeted encryption.

T1083File and Directory DiscoveryEvidence1

"Discovery T1083 File and Directory Discovery"

T1135Network Share DiscoveryEvidence1

The binary encrypts local and network drives, appends a 56-byte footer to each file, renames files with a .payload extension, drops a ransom note, and deletes its own executable.

T1497.001System ChecksEvidence1

Anti-debugging reads /proc/self/status and checks TracerPid: for a non-zero value.

T1614System Location DiscoveryEvidence1

"Discovery T1614 System Location Discovery"

Lateral Movement

1 technique
T1021.002SMB/Windows Admin SharesEvidence1

As mentioned from the strings before, it enumerates network drives to ensure lateral encryption across the network.

Collection

1 technique
T1074Data StagedEvidence1

"Collection T1074 Data Staged" and description of double-extortion with claimed exfiltration.

Command and Control

2 techniques
T1071Application Layer ProtocolEvidence1

"Command and Control T1071 Application Layer Protocol" and: "Victims are instructed to access a Tor-based portal to communicate with the attackers."

T1090ProxyEvidence1

"Command and Control T1090 Proxy" (also listed for FishMonger).

Exfiltration

1 technique
T1537Transfer Data to Cloud AccountEvidence1

The Payload Ransomware group claims to have hacked the Royal Bahrain Hospital (RBH) and stolen 110 GB of data.

Impact

3 techniques
T1486Data Encrypted for ImpactEvidence5

Payload ransomware targets Windows systems and appends the “.payload” extension to every file it encrypts. Victims are greeted with a ransom note called RECOVER_payload.txt... Files are encrypted in one-megabyte chunks, and a 56-byte footer is written to the end of every file when the process completes.

T1489Service StopEvidence3

This function essentially kills the services listed in the disassembler. Some examples are: Sophos AV Symantec AV 360 Safe Guard AV. It also kills backup services, not just AV's: Veeam Commvault StorageCraft Pointdev Acronis backup CA backup

T1490Inhibit System RecoveryEvidence4

Before encryption begins, it deletes Windows shadow copies... Combined with the deletion of all shadow copies before encryption begins, defenders are left with very little forensic evidence after an attack.

Other

3 techniques
T1562.001Disable or Modify ToolsEvidence4

Before encryption begins, it... patches event-tracing functions in memory... It terminates over 30 processes and stops more than 40 services before locking files, targeting everything from SQL databases to Veeam and Acronis backup solutions.

T1562Impair DefensesEvidence2

It also empties the recycle bin and optionally wipes all Windows event logs and patches ETW to blind EDR.

T1562.006Indicator BlockingEvidence1

"Defense Evasion T1562.006 Impair Defenses: Indicator Blocking"

INDICATORS OF COMPROMISE

IOCs tracked for this family

4 indicators attributed across vendor reports, sandbox runs, and researcher write-ups. Full values are available in Mallory.

View more in app
Network
2 tracked

IPs, domains, and DNS infrastructure linked to this family.

Hashes
2 tracked

File hashes (MD5, SHA-1, SHA-256) from samples and reports.

TypeValueLatest sighting
domain●●●●●●●●●●●●View more in app3 months ago
domain●●●●●●●●●●●●View more in app3 months ago
hash.sha256●●●●●●●●●●●●View more in app3 months ago
hash.sha256●●●●●●●●●●●●View more in app4 months ago
What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets match these IOCs, which detections are missing, which campaigns to expect next, and what to do in the next 30 minutes.
IOC matching4

Match every observed IP, domain, and hash against your live telemetry.

Threat actor attribution

Named campaigns wielding this family, with evidence pinned to each claim.

Exploited vulnerabilities

CVEs this family uses for access and lateral movement.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

MITRE ATT&CK mapping28

Every documented technique, ranked by evidence weight.

Researcher chatter

Reddit, Mastodon, and CTI community discussion around this family.