Salesforce customers (multiple organizations) (2025): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Salesforce customers (multiple organizations) disclosed the incident on 12 Mar 2025. What was exposed, as the sources state it: Data exfiltrated from customer Salesforce accounts through a connected app; counts not public. The ledger reads the access path as stolen user credentials and session tokens with third-party access.
Open the ledger · Report a correction
- Disclosed
- 12 Mar 2025
- Incident window
- not public
- Cloud or provider
- Salesforce
- What was exposed
- Data exfiltrated from customer Salesforce accounts through a connected app; counts not public
- How access was gained
- Salesforce stated threat actors impersonated IT support by phone, luring customers' employees and third-party support workers to phishing pages to steal credentials and MFA tokens, or to add a malicious connected app.
- Access path
- Stolen user credentials and session tokens; also Third-party access
- Kind of control that addresses it
- restrict logins to known network ranges, require phishing-resistant MFA, and limit who may authorize connected apps
In the words of the source
“Once the threat actor gains access to a customer’s Salesforce account or adds a connected app, they use the connected app to exfiltrate data.” (provider post mortem, Protect Your Salesforce Environment from Social Engineering Threats)
Primary sources
- provider post mortem: Protect Your Salesforce Environment from Social Engineering Threats, dated 12 Mar 2025
If a field is wrong or a newer primary source exists, write to the editor with the entry name in the subject.
Related pages
Sources
- Protect Your Salesforce Environment from Social Engineering Threats, read 16 Nov 2026
Last reviewed 16 Nov 2026.