Mixpanel (2025): what the sources say about the cloud incident
Facts read 16 Nov 2026. Page reviewed 16 Nov 2026.
Mixpanel disclosed the incident on 27 Nov 2025. What was exposed, as the sources state it: not public. The ledger reads the access path as stolen user credentials and session tokens. The cloud or provider involved: Mixpanel. Every field rests on the primary sources listed below.
Open the ledger · Report a correction
- Disclosed
- 27 Nov 2025
- Incident window
- from November 8, 2025
- Cloud or provider
- Mixpanel
- What was exposed
- not public
- How access was gained
- The company stated it detected a smishing campaign on November 8, 2025, and took steps to contain unauthorized access and secure impacted user accounts; it revoked sessions and rotated compromised credentials for impacted accounts.
- Access path
- Stolen user credentials and session tokens
- Kind of control that addresses it
- require phishing-resistant multi-factor authentication for staff accounts and revoke sessions on any report of credential phishing
In the words of the source
“On November 8th, 2025, Mixpanel detected a smishing campaign and promptly executed our incident response processes.” (company statement, Our response to a recent security incident)
Primary sources
- company statement: Our response to a recent security incident, dated 27 Nov 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
- Our response to a recent security incident, read 16 Nov 2026
Last reviewed 16 Nov 2026.