grid
Abstract circular gradient with concentric rings in blue, green, yellow, and red fading into black background.
5 min read

FBI Makes Another Arrest as Pressure on ShinyHunters Builds

ShinyHunters Arrest
Published on
October 12, 2026

Federal agents arrested another suspect on Friday over the theft of data from the FBI’s own recruitment platform. Director Kash Patel announced the ShinyHunters arrest on X, describing the man as a suspected co-conspirator of the group behind the FBIJobs.gov incident. He said the bureau had acted against the same network several times within days. Officials withheld his name, the location of the operation and the charges filed against him.

Later reporting identified him as a Canadian citizen taken into custody in Pennsylvania. Investigators treat him as a primary co-conspirator in the intrusion. The portal he allegedly helped breach ran on infrastructure managed by an outside vendor, not by the bureau itself. With this case, the ShinyHunters arrest wave now spans three countries in under amonth.

What the latest ShinyHunters arrest involves

Patel gave few specifics about the ShinyHunters arrest beyond the fact of the detention. He framed the operation as part of a push to dismantle what remains of the group, and promised continued work with partners abroad. Prosecutors have released neither a name nor a charge sheet. Court filings offer the only formal record, and most of it stays sealed.

What the bureau has confirmed is the origin of the exposure. Officials traced the incident to a contractor-managed platform that had skipped an available security update. One missing patch became a route onto government cloud infrastructure.

Timing matters here. Each ShinyHunters arrest since mid-September has followed quickly from the one before it. Investigators appear to be working through a connected set of identities rather than chasing isolated suspects. The pace suggests they are converting seized material into fresh leads.

How attackers reached the FBI jobs portal

The group claimed in September that it exploited an alleged zero-day flaw in Oracle PeopleSoft. From that foothold, the attackers moved laterally into FBI-managed AWS GovCloud infrastructure. A single application compromise turned into a far broader intrusion.

None of that required exotic tooling. The route runs through familiar weaknesses: an exposed enterprise application, a missed update, and trust between connected systems. Defenders meet the same chain in private-sector breaches every month.

What the stolen files contain

The threat actors put the haul at 2TB to 3TB. It covers current and former employees, job applicants and internal service records. Samples shared with reporters contained home addresses, Social Security numbers and sensitive job assignments. Medical and psychiatric records and details about employees’ family members also appeared.

An internal memo reportedly told staff the bureau assumed every employee had been affected. That assumption explains the intensity of the response. Exposed addresses and job assignments create physical safety risks for law enforcement personnel, so the standard fraud playbook falls short. The stakes help explain the urgency behind each ShinyHunters arrest since.

A month of ShinyHunters arrests across three jurisdictions

Dutch police opened the sequence on 15 September. They detained a 24-year-old Amsterdam man later identified as Pepijn van der Stap, known online as “Umbreon.” The group publicly rejected any link to him. Its main representative kept talking to journalists afterwards, which suggested van der Stap was not running that account.

Soon after, the FBI did something unusual in an open case. Cyber Division Assistant Director Brett Leatherman publicly invited remaining members to come forward. He warned that “arrests have a way of changing who is willing to talk.” That appeal landed between the first ShinyHunters arrest and the next one.

Jordanian authorities then detained a member known as “Rey,” identified as Saif al-Din Khader. He reportedly began helping the FBI and partner agencies locate others. Cooperation of that kind produces results fast, so the Pennsylvania operation fits the pattern. Every ShinyHunters arrest in this run has come from a different jurisdiction.

The ShinyHunters arrest that raised harder questions

Court records in the Eastern District of Pennsylvania name Edward Dubrovsky, a 54-year-old Canadian cybersecurity executive. Agents detained him at a conference in the state. A later order moved him to the Eastern District of Texas, where prosecutors filed charges. He remains in custody.

The docket lists conspiracy to threaten the confidentiality of information with intent to extort. It also lists Hobbs Act extortion counts. The complaint itself stays under seal, so the alleged conduct remains out of public view. Until a judge unseals it, the allegations remain unproven.

Dubrovsky co-founded a Canadian firm that negotiates ransom payments for breach victims, and he has worked with a second company in the same field. The FBI has not confirmed that he is the man in Patel’s announcement. The details line up all the same: a Canadian citizen, detained in Pennsylvania, on the same day. A ShinyHunters arrest reaching into the extortion-response industry would change how insurers and victims read the whole case.

Signs of strain inside the network

The group’s main public voice went quiet last Tuesday. That account had spoken with reporters for roughly two years and knew the operation’s attacks in detail. It has since disappeared. Another affiliate with direct knowledge of the FBI intrusion also closed a messaging account.

The group’s leak site dropped offline around the same time. A replacement appeared shortly after, so part of the operation still functions. Brand names like this one rarely die cleanly, because the label passes between loosely connected actors. Police have arrested people under the ShinyHunters banner since 2018 without retiring it.

Losing a long-standing public voice still costs an extortion crew real leverage. Pressure on victims depends on visibility and credible threats to publish. Silence weakens both, and every new ShinyHunters arrest gives the remaining operators another reason to distrust each other.

Why the case matters beyond federal systems

Bureau figures put ShinyHunters and associated actors at more than 140 breached organisations and over $70 million in extortion payments in the past year. Victims include Google, Cisco, Match Group and a long run of Salesforce customers. The group also rents out its capabilities to other criminals. At that scale, a single ShinyHunters arrest changes little on its own.

Most of the activity starts with people rather than software. Operators call employees and impersonate internal IT support. They walk targets into entering credentials and multi-factor codes on convincing phishing pages. Device code phishing has also let them capture Microsoft authentication tokens outright.

One working single sign-on session then opens Salesforce, Microsoft 365, Google Workspace, Slack, SAP and Zendesk. The FBI breach follows the same logic through a different door. Any organisation reviewing its exposure should start with vendor-managed systems and identity provider access, because those two gaps account for most of this group’s wins.

Where the investigation goes next

Patel committed the bureau to continued work against the remainder of the network. Every detention adds devices, chat archives and people with reasons to talk. No single ShinyHunters arrest produces that on its own, and the reported cooperation from Jordan may prove worth more than any individual case.

For defenders, the lesson sits in the breach rather than the enforcement response. A contractor skipped a patch. Attackers exploited it, and data on an entire federal workforce walked out the door. Arrests do not close that gap.

Subscribe to newsletter

Subscribe to receive the latest blog posts to your inbox every week.

By subscribing you agree to with our Privacy Policy.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.