Google (2025): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Google disclosed the incident on 5 Aug 2025. What was exposed, as the sources state it: The update says a corporate Salesforce instance used to store contact information and related notes for small and medium businesses was affected; data retrieved was confined to basic and largely publicly available business information such as business names and contact details.
Open the ledger · Report a correction
- Disclosed
- 5 Aug 2025
- Incident window
- June 2025, as the update says
- Cloud or provider
- Salesforce
- What was exposed
- The update says a corporate Salesforce instance used to store contact information and related notes for small and medium businesses was affected; data retrieved was confined to basic and largely publicly available business information such as business names and contact details.
- How access was gained
- Google stated that the instance was impacted by UNC6040 activity described in the same post, which describes voice phishing in which employees are tricked into authorizing a malicious connected app or sharing credentials.
- Access path
- Stolen user credentials and session tokens; also Third-party access
- Kind of control that addresses it
- restrict who may authorize connected apps, require phishing-resistant multi-factor authentication and limit logins to known network ranges
In the words of the source
“In June, one of Google’s corporate Salesforce instances was impacted by similar UNC6040 activity described in this post.” (company statement, The Cost of a Call: From Voice Phishing to Data Extortion (Update, August 5))
Primary sources
- company statement: The Cost of a Call: From Voice Phishing to Data Extortion (Update, August 5), dated 5 Aug 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
Last reviewed 16 Nov 2026.