← Back to the blog
By Cyber Security Briefing · Thursday, October 29, 2026 · 5 min read

Ransomware Negotiator Charged in ShinyHunters Case Had Access to the Clients He Allegedly Betrayed

Hero image for the article “Ransomware Negotiator Charged in ShinyHunters Case Had Access to the Clients He Allegedly Betrayed”

Original illustration created for Cyber Security Briefing.

Sponsored
AI-Driven Interactive Websites

Edward Dubrovsky was arrested in Philadelphia on October 9, 2026, while attending the Cyber Risk Summit, according to Krebs on Security. He was not a hacker caught mid-intrusion. He was a ransomware negotiator — the person companies hire to sit across the table from extortion groups and talk the price down.

Federal prosecutors now allege he was also talking to the other side.

Who Got Arrested, and on What

Dubrovsky is a 54-year-old Canadian citizen, according to Reuters reporting dated October 13, and the author of a book titled Cyber Extortion Strategic Response, per Slashdot's October 11 report, which also identified him in the U.S. Bureau of Prisons system following his arrest. He held senior roles at Cypfer, a Canadian incident-response firm, and later at CyberSteward, a Toronto-based cybersecurity company, according to SecurityWeek's October 12 reporting and Bleeping Computer's October 10 account.

Court records in the Eastern District of Pennsylvania charge him with conspiracy to threaten to impair the confidentiality of information with intent to extort money, under 18 U.S.C. §§371 and 1030(a)(7)(B), plus Hobbs Act extortion, Bleeping Computer reported on October 10. The case has since moved to the Eastern District of Texas, where the underlying complaint remains sealed.

FBI Director Kash Patel confirmed the arrest of a "suspected co-conspirator" in the ShinyHunters attack on the bureau's own jobs portal, CNN reported on October 9. That breach, according to SecurityWeek's October 12 account, traced back to a contractor's failure to patch an Oracle PeopleSoft vulnerability on fbijobs.gov — a patch that had been available since May, according to Slashdot's October 11 reporting, which also named senior FBI cyber official Brett Leatherman as confirming the contractor had been removed. The Canadian Press reported the same day that the breach compromised personal data belonging to nearly all FBI employees.

The Role That Created the Access

Ransomware negotiation sits in an unusual spot in incident response. The negotiator is retained by the victim, but the job requires direct, sustained contact with the threat actor — reading their demands, probing their credibility, sometimes exchanging cryptocurrency on the client's behalf. CBC News reported on October 23 that Dubrovsky, in his role at Cypfer, had helped the city of Hamilton, Ontario, recover from a 2024 cyberattack.

The new allegation, per the same CBC report, is that Dubrovsky may have defrauded his own clients by working secretly with the threat actors he was hired to negotiate against. Hoodline reported on October 24 that prosecutors allege he engaged in untraceable cryptocurrency exchanges using Monero with criminal elements, and that a prosecutor identified as Anthony Carissimi, speaking in Philadelphia, claimed Dubrovsky was working on behalf of threat actors in dealings that involved his own business partners.

Dubrovsky's attorney, Tim Wright, told CBC that his client intends to fight the charges to clear his name.

What Investigators Say They Found

Krebs on Security reported on October 19 that federal investigators believe Dubrovsky may have helped operate "Shinywire," a now-defunct extortion site used to pressure ShinyHunters victims into paying. The evidence, according to that report, includes Signal messages recovered from a Dutch suspect, Pepijn van der Stap, that show frequent contact with Dubrovsky. Investigators allege those messages indicate Dubrovsky knew about the FBI data theft before it became public and did not alert authorities.

That sequence — a negotiator aware of an active breach against a federal agency, in contact with a suspect tied to the group responsible, before the breach surfaced publicly — is the detail security teams discussing the case on social media keep returning to. It is also the detail prosecutors have not yet laid out in an unsealed complaint; the Eastern District of Texas filing remains sealed, and what Dubrovsky knew and when is still an allegation, not an established finding.

Why This Sits Differently Than a Typical Insider Case

Reuters quoted security expert Claudio Popa's assessment on October 13 that ShinyHunters is one of the most prolific hacker groups currently active, and noted the FBI is pursuing multiple co-conspirators across different jurisdictions. That framing matters for how this case should be read inside security operations teams: Dubrovsky is one node in a larger group being worked, not a lone insider who went bad in isolation.

What distinguishes this from a standard insider-threat scenario is the nature of the access itself. A SOC analyst or a pen tester who turns malicious has to abuse a position of trust to reach an adversary. A ransomware negotiator's job is direct adversary contact — authorized, expected, and often conducted over channels the client organization cannot see into. Monero wallets, Signal threads, and direct negotiation calls are standard tooling for the role, not red flags on their own. That is precisely what makes the position hard to monitor: the activity that would be suspicious in any other security function is this function's normal workday.

What Changes for Vetting and Oversight

Organizations that retain outside negotiators, whether through an incident-response retainer or a one-off engagement during an active extortion event, typically verify the firm's credentials and references. Few build in independent verification of the negotiation itself — a second party reviewing payment flows, communication logs, or the negotiator's claimed back-channel intelligence about the threat actor.

The Dubrovsky case gives CISOs and incident-response leads a concrete reason to ask for that verification going forward. If a negotiator is advising on payment amount, timeline, or the threat actor's credibility, that advice is currently taken largely on trust, with the client organization in no position to independently confirm what was actually said to the other side.

None of the reporting to date establishes a broader pattern among negotiation firms; this is one individual, one set of charges, one case still working through a sealed complaint. But the structural exposure the case illustrates — a trusted third party with unsupervised contact with the adversary — predates Dubrovsky and will outlast this prosecution.

Dubrovsky has not entered a plea in the Eastern District of Texas matter as of the most recent reporting, and his attorney has said he intends to contest the charges.

Links Verified at Time of Publish.

Sources

This article was reported from the following sources.

  1. FBI Arrests Executive at Ransomware Negotiation Firm — Krebs on Security, 2026-10-09
  2. FBI arrests cybersecurity executive in major hack on agents' data — CNN Politics, 2026-10-09
  3. FBI arrests Canadian in ShinyHunters hack of the bureau's jobs portal — CityNews Winnipeg / The Canadian Press, 2026-10-09
  4. Cyber exec arrested in case allegedly tied to ShinyHunters hackers — Bleeping Computer, 2026-10-10
  5. Canadian ransomware negotiator arrested amid FBI hacker crackdown — Reuters / CP24, 2026-10-13
  6. Feds Suspect Ransom Negotiator Ran ShinyHunters Extortion Site — Krebs on Security, 2026-10-19
  7. Ransomware Response Expert Arrested in ShinyHunters FBI Hack Probe — SecurityWeek, 2026-10-12
  8. Canadian cybersecurity exec arrested by FBI accused of working with criminals to defraud his own clients — CBC News, 2026-10-23
  9. Cybersecurity Exec Accused of Extorting His Own Clients After FBI Arrest — Hoodline, 2026-10-24
  10. FBI Arrests Cybersecurity Executive Over Data Breach After Contractor Fails to Update Oracle HR Platform — Slashdot, 2026-10-11
Sponsored
Newsletters Automation & Hosting Platform

More from the blog