Loading...

The chief technology officer and co-founder of RansomwareHelp, a Florida-based firm that marketed itself as a ransomware decryption specialist, has been charged with wire fraud. An FBI sting operation revealed that the company, which publicly urged victims not to pay ransoms, was secretly negotiating with threat actors and charging clients a significant markup on the decryption keys it purchased.
According to an indictment returned in Rhode Island, Juan Ricardo Palacio Escobar, a 52-year-old co-founder of the six-year-old Florida business, routinely paid ransomware groups for decryption keys and then billed victims well above the amount he secretly paid the attackers. The company’s website, RansomwareHelp, claimed to use "advanced cryptographic tools" to restore 100 percent of data without paying extortion demands, boasting of a 99% success rate and a team of 80 experts. It explicitly stated, "We never promote, intermediate or pay ransom to threat actors on behalf of our clients."
The FBI posed as both a ransomware victim and a fictitious ransomware group to test the company. When investigators acting as victims provided a phony ransom note, RansomwareHelp reiterated its no-payment policy. However, Palacio soon contacted the fake ransomware group, requesting the lowest possible price for a decryptor. The FBI quoted 0.2 bitcoin (approximately $13,000). Less than 48 hours later, Palacio told the fake victim that the decryption cost would be $13,260. In a subsequent transaction, Palacio negotiated the ransom down to around $6,000 in bitcoin but charged the FBI’s fake victim firm $16,010, including a $2,750 diagnostic fee.
Paul Ihme, co-founder of security firm Soteria, told KrebsOnSecurity about a 2024 incident involving a small accounting firm hit by Lockbit ransomware. RansomwareHelp proposed a $438,880 recovery fee, citing "510 preconfigured forensic servers" and "brute force processes." Ihme noted that the firm insisted on unrestricted remote access via AnyDesk, which he believes was used to delete ransom notes from the victim’s network to prevent the victim from contacting the attackers directly. Chat logs showed RansomwareHelp negotiating with Lockbit while pleading with the group not to reveal their involvement to the victim. The accounting firm eventually hired a different firm and paid half of what RansomwareHelp had quoted.
This indictment exposes a critical vulnerability in the incident response ecosystem for small and mid-sized businesses (SMBs). Many SMBs lack in-house security expertise and are desperate for help during a breach, making them prime targets for predatory firms that exploit technical jargon to justify exorbitant fees. The fact that RansomwareHelp targeted non-technical businesses with farcical claims—such as using SHA-256 password hashing algorithms to break encryption—highlights the urgent need for due diligence. For your company, this means that the first vendor you call after a ransomware attack may not have your best interests at heart. Trusting a vendor that promises "no ransom payment" without verifying their methodology can lead to higher costs, data loss, or further compromise if they are actually negotiating behind your back. The legal risk here is not just financial; it is operational, as unauthorized remote access by a third party during an active incident can destroy forensic evidence and complicate recovery.
Recent nationwide outages and Nvidia chip smuggling scandals highlight emerging operational and compliance risks for small businesses.

Anthropic has completed a massive IPO raising $81.3 billion, but governance experts question whether its Long-Term Benefit Trust can effectively enforce AI safety.

An exploitation of Optimizely, a widely used A/B testing platform, resulted in malware being served to visitors of at least 178 prominent websites. This incident underscores critical vulnerabilities inherent in extensive reliance on third-party JavaScript.

A nationwide study finds school cellphone bans add up to two weeks of learning, and researchers see the Meta settlement as a chance to measure out‑of‑school phone use.

Comments1
This case underscores the importance of rigorous third‑party risk assessments and transparent cost structures in cyber‑recovery services—CFOs should demand audited proof of key acquisition costs before authorizing any decryption spend. It also raises a red flag for cyber‑insurance underwriting: policies may need clearer exclusions for vendor‑mediated ransom payments that lack documented compliance. How are you advising clients to embed contractual safeguards that prevent hidden mark‑ups and potential fraud?
I’m urging clients to embed mandatory audit clauses that obligate vendors to disclose itemised cost breakdowns and provide third‑party verification of any decryption‑related expenses, coupled with escrow‑based payment triggers and clear indemnity provisions for undisclosed mark‑ups. Additionally, insurers should require contractual warranties that any ransom‑payment pathway be pre‑approved by an independent compliance officer and that any breach of those warranties triggers an automatic policy exclusion.