The FBI has indicted the chief technology officer and co-founder of ransomwarehelp.com — a six-year-old Florida business that marketed itself as a data recovery specialist using "advanced cryptographic tools" — on wire fraud charges. According to the indictment, a sting operation revealed the company's entire business model: take a victim's money, pay the ransomware operators directly for the decryption key, pocket a markup, and tell the client their proprietary technology cracked the encryption.
This is not a novel scheme, but it is a consequential one. Every organization that engages a third-party "ransomware recovery" firm needs to understand what they may actually be purchasing: an unlicensed ransom negotiation service that exposes them to sanctions liability, funds criminal enterprises, and delivers zero forensic or recovery value.
If your incident response plan includes a line item for "external decryption services," this indictment is your forcing function to re-evaluate it.
What Actually Happened
RansomwareHelp presented itself to victims — often small and mid-sized businesses reeling from an active encryption event — as a technical recovery firm. Their marketing claimed advanced cryptographic capability to restore files without paying attackers. In reality, per the FBI's findings:
- The victim engaged RansomwareHelp and paid an inflated "recovery fee."
- The company contacted the ransomware operators through the standard negotiation channel — typically a Tor-based portal listed in the ransom note.
- They paid the ransom (in cryptocurrency) using the victim's funds, received the attacker's decryptor, and ran it.
- They represented this to the client as their own proprietary work and kept the difference.
No cryptanalysis. No exploit of a flaw in the ransomware's encryption implementation. No value-added forensics. Just a payment broker wearing a lab coat.
Why This Matters Beyond the Fraud
The wire fraud charge is about the deception. But the defensive implications for your organization run deeper:
OFAC sanctions exposure. The U.S. Treasury's Office of Foreign Assets Control has repeatedly warned (2020 advisory, updated 2021, and consistently enforced through 2026) that facilitating ransom payments to sanctioned entities — including several ransomware groups and their associated crypto wallets — can result in civil penalties even when the payer didn't know the counterparty was sanctioned. If your "recovery firm" pays a sanctioned actor on your behalf, you have not outsourced that liability. Civil liability for sanctions violations operates on strict liability — intent is not required.
You funded the next attack. Ransom payments directly finance ransomware-as-a-service operations, affiliate payouts, and initial access broker markets. Every payment — including ones laundered through a "recovery" markup — raises the cost curve for everyone.
You got no forensic value. Legitimate IR firms preserve evidence, identify the intrusion vector, scope the compromise, and verify eradication. A payment broker does none of this. Organizations that engaged firms like RansomwareHelp may have restored files while the attacker's persistence mechanisms, stolen credentials, and exfiltrated data remained entirely unaddressed. If you were a past customer of this firm, treat your "recovery" as an unclosed incident.
Deception during a crisis. The victims here were defrauded at their most vulnerable moment — mid-incident, under operational and regulatory pressure. The scheme worked because most organizations have no pre-incident criteria for vetting recovery vendors.
Technical Analysis: What the Attack Chain Actually Looked Like
There is no CVE here — the vulnerability is procedural. But the observable behaviors associated with this scheme map directly to detectable telemetry, because the firm's "work" was indistinguishable from a ransom payment negotiation:
- Tor connectivity from the victim environment or a consultant's machine. Ransomware negotiation portals are overwhelmingly hosted as Tor hidden services. The ransom note contains an .onion URL and a victim-specific ID.
- Access to the attacker negotiation portal using credentials from the ransom note.
- Cryptocurrency acquisition and transfer — typically Bitcoin or Monero — to the attacker's wallet address.
- Execution of the attacker-supplied decryptor on victim systems. This is a critical point: running an executable provided by the threat actor introduces a second-stage malware risk that legitimate recovery firms (doing real cryptographic work) would never accept.
- No reimaging, no credential reset, no root cause analysis — because the "firm" had no capability to perform them.
The exploitation status here is not theoretical: this fraud operated for approximately six years, meaning an unknown number of victim organizations currently believe they recovered cleanly from ransomware when they actually have an unscoped compromise and an unreported ransom payment.
Detection & Response
The detections below target the observable behaviors associated with covert ransom payment activity and the ransomware incident itself. These are useful both for detecting an in-progress incident and for hunting whether a third party conducted negotiation/payment activity from your environment during a past incident.
---
title: Tor Client Execution on Endpoint
description: Detects execution of Tor client software, which is commonly used to access ransomware negotiation portals hosted as hidden services. Tor has few legitimate uses in corporate environments.
references:
- https://krebsonsecurity.com/2026/11/cto-of-ransomwarehelp-indicted-for-wire-fraud/
- https://attack.mitre.org/techniques/T1090/003/
author: Security Arsenal
date: 2026/11/20
id: 8f3c2a71-4b6d-4e9f-a1c2-7d5e9b0f3a41
status: experimental
logsource:
category: process_creation
product: windows
detection:
selection_img:
Image|endswith:
- '\tor.exe'
- '\tor-browser\Browser\firefox.exe'
- '\start-tor-browser.exe'
selection_name:
OriginalFileName:
- 'tor.exe'
- 'Tor Browser'
condition: 1 of selection_*
falsepositives:
- Rare legitimate privacy or research use; investigate any hit in a corporate environment
level: high
---
title: Ransom Note File Creation on Endpoint
description: Detects creation of files matching common ransomware note naming conventions, indicating an active or recent encryption event that may trigger engagement of a third-party recovery firm.
references:
- https://krebsonsecurity.com/2026/11/cto-of-ransomwarehelp-indicted-for-wire-fraud/
- https://attack.mitre.org/techniques/T1486/
author: Security Arsenal
date: 2026/11/20
id: 2b7d9e14-6a3f-4c8b-b5e1-9f0a4c2d6e83
status: experimental
logsource:
category: file_event
product: windows
detection:
selection:
TargetFilename|contains:
- 'DECRYPT'
- 'RECOVER-FILES'
- 'HOW_TO_RESTORE'
- 'README_FOR_DECRYPT'
- 'RESTORE_FILES_INFO'
- 'READ_ME_TO_DECRYPT'
- 'HOW-TO-DECRYPT'
filter_ext:
TargetFilename|endswith:
- '.txt'
- '.hta'
- '.html'
condition: selection and filter_ext
falsepositives:
- Security tooling test artifacts; rare in practice
level: critical
---
title: Outbound Connection to Tor Network Ports
description: Detects network connections to well-known Tor directory and relay ports, consistent with a client bootstrapping into the Tor network to reach an attacker negotiation portal.
references:
- https://krebsonsecurity.com/2026/11/cto-of-ransomwarehelp-indicted-for-wire-fraud/
- https://attack.mitre.org/techniques/T1090/003/
author: Security Arsenal
date: 2026/11/20
id: 5e1a8c36-2f4b-4d7a-9c3e-1b8f6a0d4e92
status: experimental
logsource:
category: network_connection
product: windows
detection:
selection:
DestinationPort:
- 9001
- 9030
- 9050
- 9051
- 9150
Initiated: 'true'
filter_vpn_infra:
Image|endswith:
- '\openvpn.exe'
- '\wireguard.exe'
condition: selection and not filter_vpn_infra
falsepositives:
- Misconfigured proxy software; VPN tools using non-standard ports
level: high
The following KQL hunts for the same behaviors across Defender and Sysmon telemetry ingested into Sentinel — use it to hunt retroactively across any past incident window where a third-party firm was engaged:
// Hunt: Tor execution or Tor-network connections during a given window
// Scope the TimeGenerated range to your incident window or run across 90 days for retro-hunting
let TorPorts = dynamic([9001, 9030, 9050, 9051, 9150]);
let TorProc = dynamic(["tor.exe", "start-tor-browser.exe"]);
union isfuzzy=true
(DeviceNetworkEvents
| where TimeGenerated > ago(90d)
| where RemotePort in (TorPorts)
| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, RemoteIP, RemotePort),
(DeviceProcessEvents
| where TimeGenerated > ago(90d)
| where FileName has_any (TorProc) or ProcessCommandLine has_any ("tor.exe", "start-tor-browser", ".onion")
| project TimeGenerated, DeviceName, FileName, ProcessCommandLine, AccountName),
(SecurityEvent
| where TimeGenerated > ago(90d)
| where EventID == 4688
| where Process has "tor.exe" or CommandLine has_any (".onion", "start-tor-browser")
| project TimeGenerated, Computer, Process, CommandLine, Account)
| sort by TimeGenerated desc
For endpoint forensics — particularly validating what a third-party consultant actually executed on your systems during a past "recovery" engagement — Velociraptor can pull execution artifacts and ransom note indicators fleet-wide:
-- Hunt for Tor clients, attacker-supplied decryptors, and ransom notes
SELECT Pid, Name, CommandLine, Exe, Username, CreateTime
FROM pslist()
WHERE Name =~ '(?i)tor|start-tor-browser'
OR CommandLine =~ '(?i)\.onion|torbrowser'
-- Separately, sweep for ransom notes and suspicious decryptor executables
-- dropped during an incident window (adjust glob roots for your fleet)
SELECT FullPath, Size, Mtime
FROM glob(globs=[
'C:/Users/*/Desktop/*DECRYPT*',
'C:/Users/*/Desktop/*RECOVER*',
'C:/Users/*/Downloads/*decrypt*.exe',
'C:/Users/*/Downloads/*decryption*',
'C:/ProgramData/*decrypt*.exe'
])
The PowerShell script below performs a point-in-time verification on a Windows system: checks for ransom note artifacts, Tor installations, running Tor processes, and shadow copy status (ransomware routinely deletes VSS snapshots — intact shadows may also indicate files were restored by decryptor rather than recovered from backup):
#Requires -RunAsAdministrator
# Ransom payment / recovery-fraud artifact sweep - run per host or via your RMM
Write-Host "=== [1] Ransom note artifacts ===" -ForegroundColor Cyan
$notePaths = @("C:\Users", "C:\ProgramData", "D:\")
foreach ($p in $notePaths) {
if (Test-Path $p) {
Get-ChildItem -Path $p -Recurse -Include "*DECRYPT*","*RECOVER-FILES*","*HOW_TO_RESTORE*","*README_FOR_DECRYPT*" -ErrorAction SilentlyContinue |
Select-Object FullName, Length, CreationTime | Format-Table -AutoSize
}
}
Write-Host "=== [2] Tor presence (processes + installs) ===" -ForegroundColor Cyan
Get-Process -ErrorAction SilentlyContinue | Where-Object { $_.Name -match 'tor|firefox' -and $_.Path -match 'Tor' } |
Select-Object Name, Path, StartTime | Format-Table -AutoSize
Get-ChildItem -Path "C:\Users","C:\Program Files","C:\Program Files (x86)" -Recurse -Filter "tor.exe" -ErrorAction SilentlyContinue |
Select-Object FullName, CreationTime | Format-Table -AutoSize
Write-Host "=== [3] Outbound connections to Tor ports ===" -ForegroundColor Cyan
Get-NetTCPConnection -State Established -ErrorAction SilentlyContinue |
Where-Object { $_.RemotePort -in 9001,9030,9050,9051,9150 } |
Select-Object LocalAddress,RemoteAddress,RemotePort,OwningProcess,
@{N='Process';E={(Get-Process -Id $_.OwningProcess -ErrorAction SilentlyContinue).Name}} | Format-Table -AutoSize
Write-Host "=== [4] Shadow copy status ===" -ForegroundColor Cyan
vssadmin list shadows
Write-Host "(Empty output above = shadows were deleted, consistent with ransomware execution)" -ForegroundColor Yellow
Write-Host "=== [5] Recently executed suspect decryptors (prefetch) ===" -ForegroundColor Cyan
Get-ChildItem C:\Windows\Prefetch -ErrorAction SilentlyContinue |
Where-Object { $_.Name -match 'DECRYPT|RECOVER|TOR-' } |
Select-Object Name, LastWriteTime | Format-Table -AutoSize
Remediation and Defensive Actions
If you were a past customer of RansomwareHelp (or any firm whose methods you could not verify):
- Re-open the incident. Assume the original intrusion vector was never identified or closed. Scope for persistence: new local/domain accounts, unauthorized RMM tools, webshells, scheduled tasks, and credential theft indicators dating to the incident window.
- Consult counsel on payment disclosure. A ransom payment was likely made with your funds. Depending on the receiving wallet, OFAC reporting obligations and state breach/insurance notification requirements may apply. Do not wait to be asked.
- Review your cyber insurance policy. Many policies require insurer pre-approval of ransom payments and use of panel vendors. An undisclosed payment through a third party may affect coverage for both the original incident and future claims.
- Rotate all credentials that existed at the time of the incident — domain admin, service accounts, VPN, and SaaS — since exfiltration and credential harvesting almost certainly predated the encryption.
Pre-incident vendor vetting (do this now, not mid-crisis):
- Demand methodology disclosure in writing. Any firm claiming "proprietary decryption" should be able to explain — under NDA if needed — whether they exploit cryptographic flaws, work from known decryptors (e.g., via No More Ransom), or negotiate with attackers. If the answer is vague, the answer is negotiation.
- Check free decryptors first. No More Ransom, maintained by Europol and law enforcement partners, hosts free decryptors for dozens of ransomware families. Any legitimate firm starts here.
- Contractually prohibit ransom payment without written authorization. Your IR retainer and recovery contracts should explicitly state that no payment to threat actors may be made without your written, informed consent — including disclosure of the amount, the wallet address, and an OFAC screening result.
- Verify the firm. Check state business registrations, professional references from named clients, DFIR certifications on staff, and whether the firm is on your cyber insurer's panel. A firm that appeared overnight with a slick website is a red flag.
- Engage law enforcement early. Report to the FBI via IC3.gov and contact CISA — both provide free assistance, and FBI involvement sometimes yields decryptors from seized infrastructure. CISA's #StopRansomware guide remains the authoritative free playbook.
Hardening against the underlying threat:
- Tested, offline, immutable backups remain the only "decryption tool" you fully control. Follow 3-2-1 with at least one offline or immutable copy, and test restores quarterly — a backup you've never restored is a hypothesis.
- Block Tor at the network edge (known relay/bridge IPs are published and regularly updated) and alert on Tor process execution per the detections above.
- Restrict execution of unsigned executables via AppLocker or WDAC — this blunts both ransomware payloads and attacker-supplied "decryptors" that may carry secondary payloads.
The Bottom Line
This indictment is a reminder that the ransomware economy has a shadow service layer built on victim desperation. When an attacker holds your data hostage, anyone promising a fast, quiet, technical fix deserves scrutiny — because the fastest quiet fix is usually just paying, and paying is something you can be deceived into doing without ever knowing it happened.
Build your IR plan so that no vendor can make that decision — or conceal it — on your behalf.
Related Resources
Security Arsenal Incident Response Services AlertMonitor Platform Book a SOC Assessment incident-response Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.