RansomwareHelp co-founder charged over secret ransom payments

RansomwareHelp co-founder charged over secret ransom payments

Add CyberWorldOpsto your preferred sources on Google
RansomwareHelp co-founder charged over secret ransom payments
Ransomware

Illustrative image generated with AI

The co-founder and chief technology officer of RansomwareHelp has been charged with wire fraud over allegations that he secretly paid ransomware attackers while selling clients a service that promised recovery without ransom payments. KrebsOnSecurity reported that an FBI sting operation underpins the case against Juan Ricardo Palacio Escobar, raising questions for businesses that trusted the Florida company’s claims of proprietary decryption technology.

Palacio, 52, of Miami and Medellin, Colombia, was named in an indictment returned in Rhode Island during the week of the November 21 report. The allegations concern how the six-year-old business represented its recovery services and charged clients; they remain allegations, not findings of guilt.

RansomwareHelp’s now-defunct website urged victims not to pay ransoms and explicitly denied negotiating with attackers or paying them on clients’ behalf. It advertised complete restoration of data, servers and systems, a success rate above 99%, more than 28 years of experience and a team of 80 specialists. Prosecutors allege that Palacio instead bought decryption keys—tools used to unlock encrypted files—from ransomware groups and charged clients substantially more.

The FBI posed as both sides of an attack

As described by KrebsOnSecurity, investigators impersonated both a ransomware victim and a fictitious ransomware group. Agents acting as the victim supplied RansomwareHelp with a fabricated ransom note and said they did not want to pay the attackers. The company reiterated its policy against negotiations and ransom payments.

Prosecutors allege that Palacio then contacted the FBI-controlled ransomware group and asked for its lowest price for a decryptor. Investigators quoted 0.2 bitcoin, worth around $13,000 at the time. Less than 48 hours later, Palacio allegedly told the supposed victim that a diagnostic assessment had succeeded and that decryption would cost $13,260.

The following day, he allegedly asked the fictitious attackers to accept $4,000. The indictment puts the agreed payment at approximately $6,000 in bitcoin, while the FBI’s fake victim company was charged $16,010: a $2,750 diagnostic fee plus the $13,260 recovery fee.

An accounting firm’s recovery proposal

KrebsOnSecurity also reported an earlier case described by Paul Ihme, co-founder of security company Soteria. Ihme said a small accounting firm approached him in 2024 after paying RansomwareHelp a diagnostic fee following a LockBit infection that encrypted its company and client data.

RansomwareHelp’s March 2024 proposal quoted $438,880 for recovery. It described forensic-server configuration, programming work to configure decryption algorithms and eight six-hour processing cycles. The proposal claimed the company would reverse-engineer the encryption using 510 preconfigured forensic servers around the world and randomly inject extracted encryption codes through brute force processes, which try possible values repeatedly.

Ihme questioned those technical claims. For example, the proposal said the company could break six types of encryption but listed password-hashing algorithms such as SHA-256. Hashing produces a fixed digital fingerprint of data; it is a different operation from the encryption that locks files.

Ihme said RansomwareHelp demanded unrestricted remote access to the accounting firm’s network through an AnyDesk installer. He believed the company used that access partly to remove ransom notes and prevent the victim from seeing its negotiations with LockBit.

Ransom notes typically identify the attackers and provide contact details, and attackers commonly leave copies on each encrypted system. Ihme said his review found only one copy, recovered from a backup snapshot on an infected computer. Using its credentials to enter LockBit’s chat service, his team found negotiations already underway for several days.

KrebsOnSecurity reported that the chats showed RansomwareHelp asking LockBit to conceal its involvement from the victim. LockBit became frustrated with the negotiations and threatened to increase the demand by $100,000 for each additional day of delay.

The accounting firm ultimately followed Ihme’s advice and hired a more established security firm to negotiate a payment. Ihme said it paid half of RansomwareHelp’s proposed charge. The chats showed RansomwareHelp continuing to seek a deal even after another negotiator was clearly acting for the victim.

Ihme described RansomwareHelp’s customers as primarily small and medium-sized businesses with limited technical knowledge, facing urgent pressure to restore their operations.

Recovery promises and ransom payments

The case follows other proceedings involving recovery providers and negotiators: KrebsOnSecurity reported that Cybersteward executive Edward Dubrovsky, 54, faces cyber extortion and conspiracy charges in a sealed case; the Justice Department announced on October 7 that MonsterCloud’s Zohar Pinhasi, 50, faces two wire fraud counts and a conspiracy count over allegations that he secretly paid more than $8 million in ransoms while charging clients more than $19 million; and a July 9 department announcement detailed Angelo Martino’s 70-month prison sentence for helping BlackCat attackers extort victims, including by selling confidential client negotiating information and participating in additional attacks.

For organizations seeking recovery, payment does not guarantee restoration or an end to the compromise. In its MonsterCloud announcement, the Justice Department cited joint FBI and Cybersecurity and Infrastructure Security Agency guidance advising against paying ransoms: payment does not ensure that files will be decrypted, systems or data will cease to be compromised, or stolen information will remain unpublished.

The FBI advises ransomware victims to contact their local field office or file a report at ic3.gov.

Read next

Sources

Back to home

Latest Cybersecurity News

All cybersecurity news →