A federal indictment accuses the co-founder and chief technology officer of RansomwareHelp of secretly paying ransomware operators while telling customers that his company did not pay ransoms. The case matters to small offices because choosing the wrong recovery company after an attack could expose systems to an untrusted remote operator and add thousands of dollars to an already costly emergency.
What happened
According to KrebsOnSecurity, federal prosecutors charged Juan Ricardo Palacio Escobar, 52, with wire fraud. He co-founded RansomwareHelp, a now-defunct Florida company that advertised proprietary cryptographic methods for recovering files without paying attackers.
The indictment alleges that the company instead negotiated with ransomware groups, bought their decryption tools and charged victims more than it paid. These are allegations, and the source does not report a conviction.
In an FBI sting, investigators posed both as a ransomware victim and as a ransomware gang. RansomwareHelp allegedly assured the supposed victim that it would not negotiate or pay a ransom, then contacted the fake gang and sought a lower price for a decryptor. The company ultimately billed the supposed victim $16,010, including a $2,750 diagnostic charge, while the agreed payment to the fake attackers was about $6,000 in bitcoin, according to the indictment described by KrebsOnSecurity.
The report also describes a separate small accounting firm that contacted RansomwareHelp after ransomware locked company and client data. A security professional involved in that case said RansomwareHelp proposed a recovery price of $438,880 and requested unrestricted remote access through AnyDesk. That account is separate from the criminal charge and comes from the security professional quoted by KrebsOnSecurity.
Who is affected
The immediate case concerns organizations that hired or considered hiring RansomwareHelp. The source does not disclose a complete customer list, the number of alleged victims or whether household customers were involved.
The broader warning applies to small offices facing ransomware without an established incident-response provider. Accounting practices and similar businesses may hold both internal files and customer information, creating intense pressure to restore access quickly. That urgency can make unsupported technical claims and large recovery bills harder to challenge.
What to do now
Preserve the ransom note and related records. Do not let a recovery vendor erase messages, invoices or communications. The security professional cited by KrebsOnSecurity believed remote access may have been requested partly so copies of ransom notes could be removed.
Ask for the recovery method in writing. Require the vendor to state whether it will contact the attackers, pay for a decryptor or use its own technical process. Save the answer with the contract and invoice.
Demand an itemized price before granting access. Ask what the diagnostic fee covers, what additional work is optional and whether any portion of the bill could be paid to the ransomware operator.
Limit remote access. Before installing AnyDesk or another remote-control tool, confirm exactly which computers the vendor needs, what permissions it requires and when access will be removed. Do not provide unrestricted access merely because the situation is urgent.
Get an independent technical review. Have a separate security professional examine unusually large recovery proposals or claims involving proprietary decryption systems. Small offices can also use CyberSec24’s cybersecurity basics for businesses under 10 people to prepare responsibilities and safeguards before an incident occurs.
Keep every payment and communication record. Retain contracts, cryptocurrency instructions, emails and chat messages. Those records can help establish what the vendor promised and what services it claimed to perform.
Sources
- CTO of ‘RansomwareHelp’ Indicted for Wire Fraud — Krebs on Security
Written by the CyberSec24 news desk with AI assistance, from the sources above. Spot an error? Tell us and we'll correct it.
