RansomwareHelp CTO indicted on wire-fraud counts after FBI probe

High · Krebs on Security ·

Exploited

Key points

  • RansomwareHelp's CTO was indicted in 2026 on wire-fraud counts after an FBI undercover operation.
  • Prosecutors say the scheme lasted roughly six years and involved a Florida-based recovery business.
  • The executive allegedly paid extortion crews, added fees for victims, and falsely claimed data was restored.
  • The case highlights vendor-trust risks for organizations responding to ransomware.

The chief technology officer of RansomwareHelp, a firm that advertised data-recovery assistance through ransomwarehelp.com, has been indicted on wire-fraud counts in 2026 following an undercover FBI operation, federal authorities say. Prosecutors describe a scheme that ran for roughly six years and was operated through a Florida-based business.

Investigators allege the executive did more than help clients bounce back from extortion attacks. Authorities say he sent money to the attackers, then billed victims with an added fee on top of those costs. The indictment also accuses him of telling customers their files had been restored when that was not true, and of charging more than the work justified.

The people affected are organizations and individuals who sought emergency help after ransomware incidents, often while under intense pressure and poorly positioned to verify technical claims. The alleged conduct matters because recovery firms occupy a position of trust. When that trust is abused, victims may pay twice and still face data loss, while legitimate incident-response providers face added suspicion.

The FBI's use of an undercover operation signals that ransomware intermediaries and negotiators are now a focus of federal enforcement, not just the extortion crews themselves. For K-12 and government IT teams, the case is a reminder to vet recovery vendors, document chain-of-custody, and avoid relying on a single outside party during an incident. Watch for further court filings, any additional defendants, and federal guidance on selecting and supervising ransomware-response contractors.

What to do now

  1. Require a written scope, fee schedule, and disclosure of any third-party payments before engaging a ransomware-recovery vendor.
  2. Verify vendor references and credentials, and check for federal or state enforcement actions before granting access.
  3. Limit remote access and shared credentials until contracts and data-handling terms are reviewed; monitor all vendor sessions.
  4. Demand evidence of recovery, such as restored sample files, hashes, and logs, before approving invoices.
  5. Reconcile all charges against the contract and escalate unexplained markups to legal counsel and cyber insurer.
  6. Preserve emails, invoices, chat logs, and payment records, and report suspected fraud to the FBI IC3.
  7. Maintain tested internal backups and recovery plans to reduce dependence on outside negotiators during an incident.

Original source

Krebs on Security

Original AI-assisted analysis, sources cited. Verify with the vendor advisory before acting.

← All cyber news