ServicesBlogPricingContactContact Now
Cyber Security5 min read

RansomwareHelp CTO Indicted in FBI Ransom-Payment Sting

RansomwareHelp CTO Indicted in FBI Ransom-Payment Sting

Introduction

A Florida company that marketed itself as an ethical alternative to paying ransomware gangs has been exposed as an alleged middleman for the very extortion it publicly condemned. The chief technology officer and co-founder of ransomwarehelp.com, 52-year-old Juan Ricardo Palacio Escobar of Miami and Medellin, Colombia, has been charged with wire fraud following an FBI sting operation, according to an indictment returned this week in Rhode Island.

The case matters well beyond one vendor. It describes a business model in which a so-called recovery firm allegedly negotiated with attackers behind the victim's back, bought a decryption key at one price, and invoiced the victim at a much higher one — while claiming that proprietary cryptography, not a ransom payment, had restored the data. For IT and security leaders who may hand incident response to an outside party under extreme pressure, the allegations are a reminder that the recovery market is largely unregulated and that vendor claims deserve scrutiny before network access is granted.

What the indictment alleges

According to the source material, ransomwarehelp.com operated for six years and advertised that its "advanced cryptographic tools" could restore 100 percent of data, servers and systems to their original format. The site told victims "Do not pay the ransom!" and claimed a success rate above 99 percent, more than 28 years of experience and a team of 80 experts in cryptography, cybersecurity, forensic analysis and reverse engineering. It also stated plainly: "We never promote, intermediate or pay ransom to threat actors on behalf of our clients."

The indictment describes a sting in which FBI investigators played two roles at once — a victim company that did not want to pay, and a fictitious ransomware group. The sequence, as summarized in the source material:

  • Agents posing as victims contacted RansomwareHelp with a phony ransom note and were told again that the company does not negotiate with or pay threat actors.
  • Palacio then allegedly approached the fake ransomware group and asked for the lowest possible price for a decryptor. The FBI quoted 0.2 bitcoin, roughly $13,000 at the time.
  • Less than 48 hours later, he allegedly told the agents acting as the victim that the diagnostic assessment had succeeded and that decryption would cost $13,260.
  • The next day, he allegedly asked the fictitious group to lower its demand to $4,000; the agreed price was around $6,000 in bitcoin.
  • The fake victim firm was billed $16,010, comprising a $2,750 diagnostic fee plus the full $13,260.

The charges are allegations. The source material does not include any public response from Palacio or the company, and no conviction has been reported.

A victim's account: the $438,880 proposal and the missing ransom notes

Paul Ihme, co-founder of the security firm Soteria, told KrebsOnSecurity about a 2024 case involving a small accounting firm whose company and client data had been locked by LockBit. The firm had already paid RansomwareHelp a diagnostic fee. Ihme said the recovery proposal that followed priced the work at $438,880 and described "professional configuration of forensic servers," "expert engineering hours of programming to configure decryption algorithms" and "eight (6-hour processing cycles) related to the decryption process." The document claimed the effort would draw on "510 preconfigured forensic servers of the maximum quantitative capacity located in different parts of the world," with programmers injecting encryption codes recovered through brute-force analysis.

Ihme also described how the engagement was conducted. RansomwareHelp insisted on unrestricted remote access to the victim's network to run diagnostics, delivered through an Anydesk remote desktop installer. In his assessment, part of the purpose was to delete copies of the ransomware notes the attackers had left behind. A review of the network found only a single copy, recovered from a backup snapshot; when the firm connected to the LockBit chat server using the user ID in that note, it found that someone had already been negotiating with the extortionists for several days. Screenshots described in the source show a 2024 conversation between LockBit and RansomwareHelp, in which the company asked the gang not to reveal its involvement to the victim.

Ransom notes are the victim's map back to the attacker: they identify the group and provide an email address or darknet chat portal. Removing them severs the victim's ability to verify claims, negotiate directly or compare offers — and, in this account, left the client dependent on the intermediary.

Grivyonx Expert Analysis

The most damaging detail here is not the markup; it is the alleged destruction of evidence and the severing of the victim's direct line to the attacker. A legitimate recovery partner should never need to erase artifacts from an infected estate. Insist on artifact preservation, read-only evidence handling and a written prohibition on attacker contact without your explicit consent. The pricing also deserves a sanity check: a proposal that quotes hundreds of thousands of dollars for "brute force" decryption of modern ransomware is describing something that does not work against strong per-file encryption, which is why real recovery usually depends on a leaked key, a flaw in the malware, or a backup. Finally, the sting shows how easily a firm's public pledge never to pay a ransom can coexist with private negotiation — so verify the claim contractually, not on the marketing page.

What security teams should do

  • Preserve the ransom notes. Before any remediation, capture every note, chat URL, user ID and sample of the encrypted files. Photograph screens, hash the files and store copies off-network.
  • Control remote access. Do not grant unrestricted remote desktop access to an outside firm. Use time-boxed, monitored, least-privilege sessions with logging you retain.
  • Demand transparency on attacker contact. Any negotiation, payment or key purchase should require written authorization and full disclosure of amounts actually paid.
  • Test the technical story. Ask how recovery works against the specific family involved, and require evidence — a decrypted test file — before large invoices.
  • Check references and structure. Verify corporate registration, named staff and prior case evidence. Claims of dozens of experts and decades of experience should be verifiable.
  • Keep your own backups and your own broker relationship. Recovery leverage comes from immutable backups and, where permitted, pre-arranged incident response and negotiation counsel.

Conclusion

The RansomwareHelp indictment is a case study in how pressure and opacity create room for exploitation. Organizations in the middle of an outage are poorly positioned to audit a vendor's claims, which is precisely why the checks above should be written into incident response plans and retainer agreements before an incident occurs. Whether the allegations are proven, the operational lesson stands: recovery work must be observable, evidence-preserving and priced against something a client can verify. Grivyonx works with security and engineering teams on AI-driven automation, DevSecOps and cloud security programs that reduce the blast radius of an attack and keep recovery decisions — and the evidence behind them — under the organization's own control.

  • #ransomware
  • #wire fraud
  • #FBI sting
  • #RansomwareHelp
  • #incident response
  • #LockBit
  • #cybercrime
Gourav Rajput

Gourav Rajput

Founder of Grivyonx Technologies