Federal prosecutors allege that MonsterCloud sold ransomware victims proprietary decryption services while secretly paying their attackers. Renee Dudley’s October 26 ProPublica report revisits the company’s promises after its chief executive, Zohar Pinhasi, was charged with wire fraud.
The timeline matters: the grand jury indicted Pinhasi on September 23, and the Justice Department announced his arraignment on October 7. October 26 is the reporting date, not the date prosecutors first brought the case.
Evidence status: criminal allegations, supported here by the charging announcement and ProPublica’s reporting. ProPublica says Pinhasi pleaded not guilty. The charges remain unproven.
Recovering files and explaining the method are separate obligations
According to prosecutors, MonsterCloud told prospective clients it could recover files without paying ransom, using advanced technology. The alleged method was to buy the attacker’s decryption key, attempt recovery and retain the remaining client fee.
The Justice Department gives one August 2023 example: an approximately $8,200 ransom payment followed by an approximately $150,000 client charge. It alleges more than $19 million in client charges and more than $8 million in ransom payments across the scheme. Those are prosecutors’ aggregate allegations, not verified profit figures.
Dudley connects the case to ProPublica’s 2019 investigation, which interviewed clients who believed MonsterCloud would avoid paying criminals. Her new report also examines paid endorsements. A familiar law-enforcement name in a testimonial does not demonstrate that a recovery method works as advertised.
The exposed group is organizations seeking help after ransomware has encrypted their files. No software version defines this risk. It arises when a distressed customer cannot verify what a recovery provider will do with its money, files and access.
Put the recovery method and spending authority in writing
The alleged failure suggests concrete procurement checks before handing over an incident:
- Ask how recovery will work. Distinguish restoration from backups, an independently available decryptor and a key obtained from the attacker. Require disclosure if the proposed method changes.
- Separate technical fees from third-party payments. Require an itemized quote and explicit authorization before any payment or negotiation on the organization’s behalf.
- Retain independent decision-making. Involve counsel and an accountable internal incident lead. The provider proposing a payment should not have sole authority to approve it.
- Define the access and evidence needed. Limit access to the agreed recovery task and preserve communications, invoices and recovery records for review.
- Test the recovery outcome. Validate restored files and application behavior. Keep containment, investigation and rebuilding in scope even if decryption succeeds.
These are defensive lessons from the alleged deception, not court-ordered controls or an endorsement of ransom payment. This case supplies no evidence that paying an attacker removes persistence or deletes stolen copies.
The earlier desk coverage of negotiator conflicts concerns separate people and proceedings. Here, the allegation is specifically undisclosed ransom payment behind a claim of proprietary decryption.
Caveat: The Justice Department presents the prosecution’s case. ProPublica reports the not-guilty plea and says its requests for a response went unanswered; neither source establishes a conviction.