Federal prosecutors say the decryptor that landed in a Florida inbox came from the same crew that locked the files. ransomwarehelp.com, a six-year-old shop that advertised “advanced cryptographic tools,” bought the key, then billed victims a markup for recovery work that was never performed. Six years of that pitch is now a wire fraud indictment against the company’s CTO and co-founder. If your cybersecurity budget treats any caller with a working key as a lifeline, you are writing a second check to the people who already own your data.

Brian Krebs reported the FBI sting this week. The company sold a story cyber security teams want to hear during an outage: we can reverse this without you talking to criminals. Prosecutors say the actual workflow was pay the gang, take a cut, and invoice the victim. That is a productized lie sitting in the same market as real incident response.

The Markup Paid the Attackers Directly

Ransomware crews already publish a price. A middleman who buys their decryptor and resells it does not shrink your blast radius. They keep the attacker paid and hand you a professional-looking statement of work. You funded the next affiliate’s infrastructure with a line item that looks like consulting.

You may get a working key if the gang honors the sale. You also get a vendor who now knows your downtime, your backup posture, and how badly you need the lights. That vendor has every reason to keep the relationship quiet. Teams that do actual threat-protection leave artifacts: containment timestamps, hashes, memory images, a list of what they killed. A key-broker leaves an invoice and a story about proprietary crypto.

The contrast this week is ugly on purpose. SentinelOne’s recap notes an alleged 8-Digits Team affiliate facing 27 years. Operators who ran the encryption get decades. People who marked up the unlock sold “recovery” to the same class of victim, then charged for analysis hours that, prosecutors say, never happened.

“Advanced cryptographic tools” was the sales copy. Paying the attackers for a decryption key, prosecutors say, was the labor.

Defense in depth assumes the people you hire after a breach sit on your side of the wall. A recovery firm that funds the gang extends the campaign. Your firewall never sees that wire. Your threat detection never flags a decryptor that simply works. The failure lives in procurement under panic, and in a board that confuses “files opened” with “incident closed.”

A Live Incident Is When Cybersecurity Cold-Calls Start

West Virginia’s legislature learned the timing this week. A disruption that began Thursday was still chewing through legislative IT systems on Friday. A spokesperson said it stayed inside that environment, which sounds like relief until the phones start ringing.

West Virginia State Capitol building, where legislative IT systems were disrupted in a multi-day incident
West Virginia’s capitol. Legislative IT was still disrupted a day after the incident began, which is exactly when unsolicited recovery pitches tend to land.

Every hour of a public outage is advertising. Staff are tired. Legal is drafting. Someone with a credit card wants the files back before Monday. That is the window fake helpers live in. They do not need to brute-force your VPN. They wait for the headline, then offer a miracle at a markup.

The federal side of this story moved the same week. The U.S. Homeland Security Task Force stood up a Threat Disruption Center aimed at the crime networks behind scams and sextortion, with a mandate to warn victims sooner. Treat ransomware “decrypt specialists” who appear after the press release as part of that same economy. They harvest panic the way romance scammers harvest loneliness.

Homeland Security Task Force graphic for the new U.S. Threat Disruption Center targeting scam networks
Washington stood up a center to disrupt scam networks and warn victims sooner. Unsolicited ransomware “recovery” sits in that same victim-targeting business, even when the logo looks technical.

If your legislature, hospital, or plant is in the news, assume inbound recovery pitches are hostile until proven otherwise. Ask who they already had on retainer last quarter. If the answer is nobody in the building, you are the lead, not the client.

If You Cannot Name the Work, Stop the Wire

Panic is a control failure. Write the rules before the next encryption event, then enforce them when the caller is polite and the CFO is scared. Immediate actions if you are in an outage, or you just crawled out of one:

  • Freeze new recovery vendors. Money moves only to firms on a pre-approved retainer, or to counsel who already represents you.
  • Demand a written method. Who produced the key, whether a ransom was paid, which wallet, which affiliate brand, and what persistence they actually hunted.
  • Keep authority in-house. A decryptor is a restore tool. It is not permission to reset identity, disable logging, or declare the incident closed.
  • Snapshot first. Image a sample of encrypted hosts before anyone runs a vendor binary. You need a before-state if that “tool” also drops a backdoor.

After the files open, security hardening is the job, not the celebration. Rotate every credential the ransomware touched, including service accounts, VPN tokens, and backup software. Watch for brute-force against the same portals the original crew already mapped. If they sold you the key through a middleman, they still have the targeting data. Decrypt is not clean.

Keep a one-page test for retainers: named individuals who will join a call in hours, no subcontracting to unknown “crypto labs,” and a clause that paying a criminal group requires your written authorization. Review it annually with legal, the same way you review insurance. Tabletop the moment a stranger offers a key. If your playbook cannot survive a charming caller at 2 a.m., you will buy whatever they are selling.

You cannot patch greed. You can refuse to be the markup. The Florida indictment is a reminder that the invoice after ransomware is part of the crime unless you can explain, in writing, exactly what you bought.

Sources

Take Control of Your Server Security

Don't let brute-force attacks slow you down. Try IPBan Pro risk-free for 30 days.

Secure. Automated. Lightweight.

Stay up to date with the latest news, releases and more.

Take Control of Your Server Security

Don't let brute-force attacks slow you down. Try IPBan Pro risk-free for 30 days.

Secure. Automated. Lightweight.