Skip to content
Cloud Security Breaches

JumpCloud (2023): what the sources say about the cloud incident

JumpCloud disclosed the incident on 12 Jul 2023. What was exposed, as the sources state it: The company stated fewer than 5 customers and fewer than 10 devices were impacted, out of more than 200,000 organizations on the platform, and that all impacted customers were notified directly.

Open the ledger · Report a correction

Disclosed
12 Jul 2023
Incident window
June 22 to July 2023 (the company: spear-phishing on June 22, anomalous activity found June 27, customer impact found July 5)
Cloud or provider
JumpCloud
What was exposed
The company stated fewer than 5 customers and fewer than 10 devices were impacted, out of more than 200,000 organizations on the platform, and that all impacted customers were notified directly.
How access was gained
The company stated it traced anomalous activity on an internal orchestration system to a spear-phishing campaign on June 22, which gave unauthorized access to a specific area of its infrastructure. It later found unusual activity in the commands framework for a small set of customers, and stated the attack vector was data injection into its commands framework.
Access path
Stolen user credentials and session tokens; also Cross-tenant access
Kind of control that addresses it
require phishing-resistant authentication for staff with access to orchestration systems, and isolate customer command execution from internal tooling

In the words of the source

“On June 27 at 15:13 UTC we discovered anomalous activity on an internal orchestration system which we traced back to a sophisticated spear-phishing campaign perpetrated by the threat actor on June 22.” (company statement, [Security Update] Incident Details (JumpCloud blog))

Primary sources

If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.

Sources

  1. [Security Update] Incident Details (JumpCloud blog), read 16 Nov 2026

Last reviewed 16 Nov 2026.