Salesloft says Drift customer data thefts linked to March GitHub account hack

Lorenzo Franceschi-Bicchierai / techcrunch - The breach, now known to have begun in March, raises questions about why it took six months for Salesloft to detect the breach.

#cybersecurity #saas #dataprivacy #infosec

Salesloft: Hacker broke into systems in March through GitHub account

5 months / therecord

NEW: Salesloft said hackers accessed its GitHub account between March and June of this year. During that time, they were able to access data that later helped them steal information from several customers, such as Bugcrowd, Cloudflare, Google, Proofpoin

5 months / bsky / @lorenzofb.bsky.social / lorenzofb.bsky.social

The breach, now known to have begun in March, raises questions about why it took six months for Salesloft to detect the breach.

5 months / bsky / @techcrunch.com / techcrunch.com

How huge breach started: Drift attackers gained entry via a Salesloft GitHub account

5 months / theregister / Jessica Lyons

Salesloft says Drift customer data thefts linked to March GitHub account hack

5 months / techcrunch / Lorenzo Franceschi-Bicchierai

Salesloft: March GitHub repo breach led to Salesforce data theft attacks

5 months / bleepingcomputer / Bill Toulas

Back to Top / Monday, September 8, 2025, 1:21 pm / permalink 14055 / 6 stories in 5 months




Related Stories

Cisco Discloses Data Breach Following Sophisticated Vishing Attack / 7 months

Ahold Delhaize data breach exposes 2.2M users’ sensitive data / 8 months

Lee Enterprises faces significant data breach fallout / 9 months

Discord data breach vendor dispute clarified / 4 months

Insight Partners ransomware breach exposes thousands’ data / 5 months

Salesloft Drift Breach Exposes Customer Data Across Tech Firms / 6 months

Cloudflare breaches support data in Salesloft Drift incident / 6 months

NorthFeed Inc.

Disclaimer: The information provided on this website is intended for general informational purposes only. While we strive for accuracy, we do not guarantee the completeness or reliability of the content. Users are encouraged to verify all details independently. We accept no liability for errors, omissions, or any decisions made based on this information.