kaganerkan pixel logo

kaganerkan

News · Nov 21, 2026

RansomwareHelp’s $438,880 Recovery Quote: What Would It Prove?

Brian Krebs identified RansomwareHelp as the Florida recovery business co-founded by Juan Ricardo Palacio Escobar, who faces a federal wire fraud charge. Krebs also published part of a proposal the company sent to an accounting firm in March 2024. The identification and the proposal are the news, not a new charge. Krebs’s story is dated November 20 in the United States; its publication feed puts it at 3:36 a.m. on November 21 in Istanbul.

What prosecutors allege

The Rhode Island federal indictment was filed November 18. On November 19, 404 Media, working with Court Watch, reported on the FBI operation. As Krebs notes, the earlier story named Palacio but not his company.

Investigators played both sides: one team posed as a victim that did not want to pay a ransom; the other posed as the attackers. According to Krebs’s account of the indictment, the company assured the supposed victim it would not pay. Prosecutors allege Palacio nevertheless agreed to pay the supposed attackers about $6,000 in bitcoin for a decryption tool and charged the supposed victim $16,010, including a $2,750 diagnostic fee. The alleged deception concerns what the customer was told it was buying, not just the difference between the two prices. An indictment is an accusation, not a finding of guilt.

What the accounting firm was offered

The $438,880 figure comes from a separate episode. Paul Ihme, co-founder of security firm Soteria, told Krebs that a small accounting firm sought help after LockBit ransomware locked its business and client data. It had paid RansomwareHelp a diagnostic fee. The proposal excerpt Krebs published described a recovery effort involving 510 forensic servers. That document records what the vendor offered; it does not establish that the servers were used or that the accounting firm paid the quoted price.

Ihme told Krebs that a ransom note recovered from a backup led to a chat where negotiations were already underway. He said the accounting firm ultimately hired another provider to negotiate and paid about half what RansomwareHelp had quoted. That is Ihme’s account to Krebs, not an outcome from the FBI operation.

Reconcile the invoice before calling the difference a markup

Start with the FBI operation, where Krebs reports both a customer charge and a negotiated key price. The $2,750 diagnostic fee is already in the $16,010. Subtract it once and the remaining charge is $13,260. Subtract the alleged key price of roughly $6,000 and about $7,260 remains in that part of the bill. Across the whole bill the difference is about $10,010: the diagnostic fee plus that remainder. Neither figure is net profit. The public figures do not itemize labor or other costs, and the key price itself is approximate.

Now try the same calculation on the accounting firm’s $438,880 quote. It cannot be done: the quoted total is not a settled invoice, the proposal excerpt does not establish what RansomwareHelp would have paid for a key, and the eventual payment Ihme describes went through a different provider. Dividing one firm’s quote by the other firm’s reported outcome may tell a buyer why it was worth getting a second offer. It does not establish the first firm’s margin.

A successful file restore answers only one of three questions

Imagine a vendor returns a readable copy of a payroll export you selected. Both an engineer using an independently developed decryptor and a broker using a purchased key could return the same file. Ask what evidence would distinguish those explanations before giving either vendor authority to proceed.

DecisionEvidence to requestWhat remains unproved
Does the method work?Have your application owner open a buyer-selected sample from an isolated copy and check a known record.One readable file does not establish key origin or recovery of the whole workload.
Is this a method we authorize?Require a written account of where the key or tool comes from, who supplies it, and whether anyone will contact or pay the attackers.A server count or a working sample does not show who supplied the key.
What are we paying for?Separate diagnosis, recovery labor and third-party charges; ask who receives each and what is owed if the restore fails.An expensive quote alone proves neither misconduct nor a viable recovery.

For the proposal’s 510-server claim, a useful follow-up is not “How powerful are they?” It is “What operation will those servers perform on our files, and what result from the diagnostic phase tells you that operation can succeed?” That turns a hardware inventory into a claim the buyer can evaluate. If the provider cannot disclose a proprietary method, record the limitation rather than treating a demonstration as proof of provenance.

A sign-off the incident lead can actually use

Copy the one-page recovery sign-off sheet into the incident record. It separates permission to examine copies from permission to restore production or involve a third party. If the method changes after diagnosis, pause at that boundary rather than letting the original purchase order stand in for a new decision.

Compiled with AI assistance from the linked reporting and court filing. The interviews and proposal reporting are Brian Krebs’s; no independent interview is claimed.