People search Salesforce data breach timeline because the brand sits on billions of accounts, credentials, and cloud workloads. BreachHistory indexes 2 Salesforce-linked incidents. This page maps every attested event through 2026 with internal links to canonical records.
Why Salesforce breach history matters
Salesforce operates in Software (United States). Across indexed rows, recurring themes include ransomware and extortion, credential theft and social engineering, cloud and database misconfiguration. Understanding the chronological pattern helps security teams, customers, and regulators separate confirmed disclosures from forum marketing.
Full timeline through 2026
2026 — ShinyHunters vishing wave against CRM tenants (platform context)
Cataloged incident. Throughout 2026, ShinyHunters and copycat actors exploited voice-phishing against employees to steal Microsoft Entra session tokens and bulk-export Salesforce CRM data from many tenants. Salesforce published security guidance and platform detections; individual victim counts (Charter 4.9M, Cisco ~3M marketing, McGraw Hill 13.5M emails, etc.) belong to each customer organization. BreachHistory indexes this contextual row under Salesforce with recordsAffected 0 to document the platform-wide campaign without double-co Exposed categories include Tenant-specific customer CRM data across Charter, Cisco, and hundreds of orgs—not a single Salesforce corporate DB leak. No attested victim count is published for this row yet. See the salesforce-shinyhunters-ecosystem 2026 r and canonical BreachHistory entry.
2018 — — Cloud behemoth Salesforce.com is warning customers…
Cataloged incident. Cloud behemoth Salesforce.com is warning customers about an API error that may have leaked data for some users of its Marketing Cloud offering. The issue was in play between June 4 to July 18, Exposed categories include Secrets. No attested victim count is published for this row yet. See the salesforce2018-vcdb1 and canonical BreachHistory entry.
Patterns and analysis
- Ransomware and extortion — appears across multiple Salesforce catalog entries; prioritize controls that address this class of failure.
- Credential theft and social engineering — appears across multiple Salesforce catalog entries; prioritize controls that address this class of failure.
- Cloud and database misconfiguration — appears across multiple Salesforce catalog entries; prioritize controls that address this class of failure.
- Record-count hygiene — BreachHistory indexes actor-cited figures separately from company-confirmed totals; read each row's technicalWriteup before treating counts as fact.
- 2026 monitoring — New disclosures roll into this timeline as they are verified or labeled unverified per catalog policy.
What to do if you may be affected
- Step 1: Enable phishing-resistant MFA on every account tied to this brand.
- Step 2: Use unique passwords and a password manager—breach rows often involve credential reuse.
- Step 3: Monitor official company breach notices and regulator filings, not dark-web downloads.
- Step 4: Bookmark the Salesforce company page for new 2026+ disclosures.
Canonical BreachHistory hub
Explore every indexed row: breachhistory.com/salesforce · Latest: salesforce-shinyhunters-ecosystem2026.
Sources: BreachHistory catalog (2 rows for Salesforce), company and regulator disclosures cited in individual breach records.