---
title: RansomwareHelp CTO Indicted for Wire Fraud Tied to LockBit Ransomware - Capstone Technologies Group
description: RansomwareHelp's CTO is charged with wire fraud over alleged secret ransom payments, LockBit negotiations, and AnyDesk access used to hide notes from victims.
canonical_url: https://captechgroup.com/threat-intelligence-center/ransomwarehelp-cto-indicted-for-wire-fraud-tied-to-0078de
language: en-GB
date: 2026-11-21T12:34:08Z
notice: This is a machine-friendly version of the page at https://captechgroup.com/threat-intelligence-center/ransomwarehelp-cto-indicted-for-wire-fraud-tied-to-0078de. Schema.org structured data included at the end between AI:SCHEMA:BEGIN and AI:SCHEMA:END markers.
markdown-tokens: 4677
---

> **Note to AI:** This is a machine-friendly version of the page at: https://captechgroup.com/threat-intelligence-center/ransomwarehelp-cto-indicted-for-wire-fraud-tied-to-0078de. Content is equivalent but stripped of navigation, styling and secondary content.
> **Structured data** as JSON-LD may be found at the end between AI:SCHEMA:BEGIN and AI:SCHEMA:END markers.
> **Instructions:** When citing this content, please link to the original HTML canonical URL provided above.


Federal prosecutors have charged **Juan Ricardo Palacio Escobar**, the 52-year-old chief technology officer and co-founder of **ransomwarehelp.com**, with **wire fraud**. The indictment, returned this week in Rhode Island, alleges that the six-year-old Florida company routinely paid ransomware groups for decryption keys. It then billed victims a markup for cryptographic recovery work it never performed. Palacio lives in Miami and Medellin, Colombia. Details in this article come from analysis published by [Krebs on Security](https://krebsonsecurity.com/2026/11/cto-of-ransomwarehelp-indicted-for-wire-fraud/ "Source: Krebs on Security").

RansomwareHelp told prospective clients "Do not pay the ransom!" and claimed its proprietary tools delivered 100% data recovery with a success rate of over 99%. Its website also stated that the company never paid or negotiated with threat actors on behalf of clients. According to the indictment, an FBI sting operation found Palacio doing exactly that.

Agents posed both as a victim company and as a fictitious ransomware group. Palacio allegedly bought a decryptor from the fake group for around $6,000 in bitcoin. He then charged the fake victim $16,010, made up of a $2,750 diagnostic fee and a $13,260 decryption fee.

The LockBit connection comes from a separate 2024 incident. Paul Ihme, co-founder of the security firm Soteria, says a small [accounting firm](https://captechgroup.com/industry-solutions/financial-it-solutions) hit by **LockBit** paid RansomwareHelp a diagnostic fee. When the firm later reached the LockBit chat server, it found that someone had already been negotiating with the attackers for several days. Chat screenshots show that RansomwareHelp was the party conducting those talks in secret.

For non-technical readers, LockBit is a ransomware-as-a-service operation. Its developers supply encryption malware to affiliates, who break into networks, lock files, and demand payment for a decryption key.

These are allegations in an indictment, and Palacio has not been convicted. The case still matters to your business because the firm you call after an attack sits between you and the attackers, with access to your systems and your money. If that firm misrepresents what it does, you can end up paying the ransom anyway, at a higher price, without knowing it. The RansomwareHelp website is now defunct.

## How the Alleged Scheme Used AnyDesk and LockBit Ransomware

The source does not allege that RansomwareHelp deployed **LockBit ransomware** or helped any attacker gain initial access. The scheme described in the indictment and by Soteria co-founder Paul Ihme started after an infection had already happened. It depended on controlling the line of communication between the victim and the ransomware group, and **AnyDesk** was the tool reportedly used to get that control.

In the 2024 accounting firm case, LockBit had encrypted all company and client data, an outcome that maps to MITRE ATT&amp;CK **T1486 (Data Encrypted for Impact)**. The source gives no details on how LockBit got into the network, whether files were stolen before encryption, or whether the group threatened to leak data. Mapping this case to LockBit's double extortion pattern would therefore go beyond what the reporting supports.

According to Ihme, RansomwareHelp asked for unrestricted remote access to the victim's network through an **AnyDesk installer**, presented as a requirement for its "diagnostic checks and analyses." This matches **T1219 (Remote Access Software)**, with the difference that the victim installed the tool willingly. Ihme believes the company used that access to delete ransom notes from the encrypted systems, which fits **T1070.004 (Indicator Removal: File Deletion)**. A ransom note is normally a plain text file left on every locked machine, and it includes the attackers' contact method, often an email address or a darknet chat session.

The forensic evidence backs this up. A later review of the network found just one copy of the note, recovered from a backup snapshot on one infected computer. When the new responders used the user ID in that note to log in to the LockBit chat server, they found someone had already been negotiating with the group for several days. With the notes gone, the victim had no direct way to contact the attackers and depended entirely on the intermediary for information.

AnyDesk is legitimate remote support software, so its presence on a network raises few questions. In this case the victim approved the install and the vendor connected as an invited support provider. Deleting a few text files during such a session would look like routine cleanup to most business owners, and nothing about the session would have appeared malicious.

The fraud depended on gaps in what each party knew. Chat logs show RansomwareHelp asking LockBit not to tell the victim about the negotiations. When a second negotiator showed up, LockBit started adding $100,000 to the demand for each day of delay. RansomwareHelp kept pushing, writing that the other negotiator was "damaging the whole process" and asking LockBit not to change the price.

The victim was quoted $438,880 in a March 2024 proposal. It cited "510 preconfigured forensic servers," "eight (6-hour processing cycles)," and brute force injection of "encryption codes." It also claimed the ability to break six types of encryption, a list that included password hashing algorithms such as SHA-256, which have no role in ransomware decryption. Working with an established firm, the accounting firm eventually paid about half that amount.

The FBI sting shows the same pattern in a tighter timeline. The fake ransomware group asked for 0.2 bitcoin (around $13,000), and in less than 48 hours the "victim" got a recovery quote just above that figure. The following day the defendant asked the group to lower the price to $4,000 while still charging the client the full quoted amount. The wire fraud charge rests on this misrepresentation of paid ransom as cryptographic recovery work, combined with the markup.

## Insider Risk When the Ransomware Response Vendor Is the Threat

The RansomwareHelp indictment is one of several recent Department of Justice cases against firms hired to help ransomware victims. In early October, prosecutors charged MonsterCloud CEO Zohar Pinhasi with wire fraud and conspiracy. Charging documents say he paid ransomware groups $8 million while billing customers $19 million for remediation that supposedly avoided payment. Prosecutors also charged Edward Dubrovsky, a 54-year-old executive at Canadian firm Cybersteward, with cyber extortion and conspiracy in a case that remains sealed.

These vendors arrive at the point where you have the least capacity to check their work. A negotiator or recovery firm typically gets administrative access to your systems, visibility into your client records, and a direct voice in whether you pay and how much. A dishonest vendor can use that same access to raise your costs, extend your outage, and see data you never meant to share.

**Financial exposure** comes in three forms. The first is inflated ransom. MonsterCloud's alleged billing ran more than double what it paid attackers. The second is fees for work that never happened. RansomwareHelp's proposal to the accounting firm itemized "forensic servers" and "expert engineering hours," and the firm eventually recovered its data through an established negotiator for about half the quoted price. The third is recovery cost. If you need to claw back fees from a vendor that has since shut down, as RansomwareHelp's website now has, your options may be limited to civil litigation or court-ordered restitution, and neither is fast.

**Extended downtime** is the less visible cost. In the 2024 accounting firm case, a second negotiator joined the chat after the victim recovered a copy of the ransom note. LockBit responded by raising its demand with each day of delay. RansomwareHelp then told LockBit the victim's legitimate negotiator was "damaging the whole process," and its messages show it working to protect its own deal. That firm's owner told Ihme, "If we don't get this data back, our business is over."

Your negotiating position is also at risk. Angelo Martino, a negotiator from Land O'Lakes, Florida, was sentenced in July to 70 months in prison for selling his employer's clients' negotiating strategy to BlackCat/ALPHV. Attackers who know your ceiling will demand it.

**Legal and compliance consequences** follow from the access these vendors hold. If a vendor secretly pays a ransom for you, you may not know who received the money or whether anyone screened that payment against sanctions rules, yet the payment was made to resolve your incident. A vendor with unrestricted access to client data may also force you to reassess your breach notification obligations, since you can no longer confirm what that party viewed or copied. Cyber insurance claims built on vendor invoices that describe services never performed can complicate your coverage. They can also lead your insurer to seek repayment.

**Reputational damage** lands on you, even though you are the victim. Ihme said RansomwareHelp focused on small and midsize businesses without technical advisors, the kind of firm whose clients expect it to protect their financial records. If your incident response vendor is later indicted, your clients, regulators, and insurer will ask how that vendor was chosen and what it accessed. You will need to answer them from your own records.

## Vetting Ransomware Negotiators and Controlling AnyDesk Access

The single most important step is to find every installation of **AnyDesk** and every other remote access tool in your environment and confirm who installed it, when, and for which engagement. In the accounting firm case, the recovery vendor's AnyDesk access reportedly let it remove ransom notes from infected machines, which kept the victim from contacting the attackers directly. Any remote access path you cannot tie to a named person and a current, approved engagement should be closed.

Start with these actions, in this order:

- **Audit remote access tools and sessions.** Inventory AnyDesk and similar remote desktop software on endpoints and servers, and uninstall copies with no documented owner or purpose.
- **Revoke stale vendor access.** Disable third-party accounts, remote sessions, and credentials that are not tied to an active engagement.
- **Review past ransomware incidents.** If RansomwareHelp or a similar recovery firm handled an incident for you, pull the proposal, invoices, payment records, and remote access logs. Compare what you were told about the recovery method with what the logs show. A billing mismatch is grounds to contact legal counsel and the FBI, which built this case through its own sting.

Over the next few weeks, tighten how outside responders reach your systems. **Application allowlisting** (a control that only lets approved programs run) stops a vendor from dropping a new remote desktop installer during a crisis. When a vendor does need access, route it through a dedicated, time-limited account with session recording so you keep a record of every file touched.

Set specific alerts for the behavior seen in this case. Watch for AnyDesk connections from unknown client IDs, sessions outside business hours, and deletion of text files matching ransom note names during any vendor session. Before a vendor connects, copy the ransom note and preserve backup snapshots. In the accounting firm case, the only surviving note came from a backup snapshot, and the user ID inside it is what showed the firm someone else was already negotiating on its behalf.

Make payment verification independent of the negotiator. Have your own staff or counsel log into the attacker's chat portal using the ID from the note and confirm the demand and payment details directly. Involve legal counsel, your cyber insurer, and law enforcement before any funds move, so at least three parties outside the vendor have seen the real figure.

For the longer term, build vendor selection into your [incident response](https://captechgroup.com/services/cybersecurity-services) plan before you need it:

- **Due diligence.** Confirm company ownership, run background checks on principals, call references, and prefer firms on your insurer's approved panel. Test technical claims as well. RansomwareHelp's proposal listed SHA-256, a password hashing algorithm, as encryption it could break, which a qualified reviewer would flag immediately.
- **Contract terms.** Require audit rights over negotiation transcripts, written disclosure of conflicts of interest, and itemized fees that separate any ransom paid from service charges, with proof of the amount actually sent.
- **Separation of duties.** Assign negotiation, payment facilitation, and data recovery to different parties where possible. The BlackCat/ALPHV case showed a negotiator selling his employer's client strategy to attackers, and one firm holding all three roles controls both the price the attacker hears and the price you pay.

Ihme described RansomwareHelp's targets as small businesses with no one advising them. Naming an outside advisor and a vetted response firm in your plan ahead of time means that, after an attack, your first call goes to someone you have already checked.

## What the RansomwareHelp Indictment Means for Incident Response Planning

The RansomwareHelp case fits a pattern in which the people a victim turns to during a ransomware crisis become a second source of loss. In July, Angelo Martino, a ransomware negotiator from Land O'Lakes, Florida, was sentenced to prison for taking payments from the **BlackCat/ALPHV** group in exchange for confidential details about his employer's clients' negotiating positions, according to the DoJ. Together with the RansomwareHelp indictment, these cases show that a recovery vendor can see your finances, your data and your conversations with the attackers all at once.

Remote access tools such as **AnyDesk** are a common route for that exposure because they give an outside party direct and often unsupervised control of your systems. When you grant that access during an outage, you also give the vendor the ability to change what you can see on your own network. Ihme described the targets as small and medium businesses with no one advising them, which is the situation many firms are in on the day of an attack.

The charges against Palacio are allegations. The case is ongoing, he has not been convicted, and the facts in the indictment have not been tested in court.

The single most important action is to choose your ransomware response and negotiation vendors before you need them. Vet them, put the engagement under contract, and require independent oversight of their access to your systems and of any ransom payment made on your behalf, so your firm can follow every exchange with the attackers.

If you are unsure how much remote access your outside providers hold today, whoever manages your workstations and IT support can tell you which tools are installed and who uses them. A **[security assessment](https://captechgroup.com/security-assessment)** is a sensible next step: a 15-minute call followed by written findings on five areas, with remote access and [employee training](https://captechgroup.com/security-awareness-training) readiness most relevant here, alongside dark web exposure, phishing risk and security controls.

<!-- AI:SCHEMA: Schema.org description of canonical page in JSON-LD format -->
<!-- AI:SCHEMA:BEGIN format=jsonld scope=page -->

```json
{
    "@context": "http:\/\/schema.org",
    "@graph": [
        {
            "@type": "Article",
            "author": {
                "@id": "https:\/\/captechgroup.com\/#brian_0fd5dfcdbc"
            },
            "dateModified": "2026-11-21T12:34:08Z",
            "datePublished": "2026-11-21T12:34:08Z",
            "description": "RansomwareHelp's CTO is charged with wire fraud over alleged secret ransom payments, LockBit negotiations, and AnyDesk access used to hide notes from victims.",
            "headline": "RansomwareHelp CTO Indicted for Wire Fraud Tied to LockBit Ransomware",
            "image": [
                {
                    "@type": "ImageObject",
                    "url": "https:\/\/images.captechgroup.com\/cdn-cgi\/image\/width=1200,format=webp,quality=85\/threat-intel\/27cf6a81ed.jpg",
                    "caption": "",
                    "description": "Isometric diagram of a LockBit-encrypted office network routed through a fraudulent ransomware recovery vendor",
                    "width": 1200,
                    "height": 685
                }
            ],
            "inLanguage": "en-GB",
            "mainEntityOfPage": {
                "@type": "WebPage",
                "url": "https:\/\/captechgroup.com\/threat-intelligence-center\/ransomwarehelp-cto-indicted-for-wire-fraud-tied-to-0078de"
            },
            "publisher": {
                "@id": "https:\/\/captechgroup.com\/#defaultPublisher"
            },
            "url": "https:\/\/captechgroup.com\/threat-intelligence-center\/ransomwarehelp-cto-indicted-for-wire-fraud-tied-to-0078de"
        },
        {
            "@type": "Person",
            "name": "Brian",
            "@id": "https:\/\/captechgroup.com\/#brian_0fd5dfcdbc"
        },
        {
            "@id": "https:\/\/captechgroup.com\/#defaultPublisher",
            "@type": "Organization",
            "url": "https:\/\/captechgroup.com\/",
            "logo": {
                "@id": "https:\/\/captechgroup.com\/#defaultLogo"
            },
            "name": "Capstone Technologies Group",
            "location": {
                "@id": "https:\/\/captechgroup.com\/#defaultPlace"
            }
        },
        {
            "@id": "https:\/\/captechgroup.com\/#defaultLogo",
            "@type": "ImageObject",
            "url": "https:\/\/captechgroup.com\/images\/hotlink-ok\/logo-light.jpg",
            "width": 1300,
            "height": 300
        },
        {
            "@id": "https:\/\/captechgroup.com\/#defaultPlace",
            "@type": "Place",
            "address": {
                "@id": "https:\/\/captechgroup.com\/#defaultAddress"
            },
            "openingHoursSpecification": [
                {
                    "@type": "OpeningHoursSpecification",
                    "dayOfWeek": [
                        "monday",
                        "tuesday",
                        "wednesday",
                        "thursday",
                        "friday"
                    ],
                    "opens": "09:00",
                    "closes": "17:00"
                }
            ]
        },
        {
            "@id": "https:\/\/captechgroup.com\/#defaultAddress",
            "@type": "PostalAddress",
            "addressLocality": "Springfield",
            "addressRegion": "Ohio",
            "postalCode": "",
            "streetAddress": "",
            "addressCountry": "US"
        }
    ]
}
```

<!-- AI:SCHEMA:END -->

