<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>pwn.watch: Salesforce incident updates</title>
  <link>https://pwn.watch/t/salesforce</link>
  <description>Live security incidents worldwide: CVEs, patch status, fixed versions, advisories and the posts that broke them.</description>
  <language>en</language>
  <lastBuildDate>Sun, 07 Sep 2025 00:00:00 GMT</lastBuildDate>
  <atom:link href="https://pwn.watch/t/salesforce/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>[high] Salesloft Drift OAuth tokens used to raid 700+ companies' Salesforce data (UNC6395)</title>
    <link>https://pwn.watch/i/salesloft-drift-oauth-salesforce-data-theft-2025</link>
    <guid isPermaLink="true">https://pwn.watch/i/salesloft-drift-oauth-salesforce-data-theft-2025</guid>
    <pubDate>Sun, 07 Sep 2025 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;Between August 8 and 18, 2025, UNC6395 used stolen OAuth tokens for the Salesloft Drift chatbot integration to bulk-export data from customers' Salesforce instances, hunting for AWS keys, Snowflake tokens, passwords and VPN credentials. Cloudflare, Palo Alto Networks, Zscaler and many others disclosed exposure. Salesforce pulled Drift from AppExchange.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; no-fix-needed · &lt;strong&gt;Fixed in:&lt;/strong&gt; Drift tokens revoked; rotate any secrets stored in Salesforce&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2025-09-02: Cloudflare details the impact on its Salesforce case data (&lt;a href=&quot;https://blog.cloudflare.com/response-to-salesloft-drift-incident/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-08-26: Google Threat Intelligence publishes UNC6395 findings (&lt;a href=&quot;https://cloud.google.com/blog/topics/threat-intelligence/data-theft-salesforce-instances-via-salesloft-drift&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-08-20: Salesloft and Salesforce revoke Drift access and refresh tokens; Drift pulled from AppExchange (&lt;a href=&quot;https://cloud.google.com/blog/topics/threat-intelligence/data-theft-salesforce-instances-via-salesloft-drift&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
  <item>
    <title>[high] Vishing campaign steals Salesforce data from Google and others (UNC6040 / ShinyHunters)</title>
    <link>https://pwn.watch/i/salesforce-vishing-data-theft-unc6040-2025</link>
    <guid isPermaLink="true">https://pwn.watch/i/salesforce-vishing-data-theft-unc6040-2025</guid>
    <pubDate>Sun, 31 Aug 2025 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;UNC6040 phoned employees posing as IT support and talked them into authorizing a modified Salesforce Data Loader app, then bulk-exported their Salesforce data. Google's own corporate Salesforce instance (prospective Ads customer contacts) was hit in June 2025. Extortion followed under the ShinyHunters name (UNC6240).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; no-fix-needed&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2025-08: Google confirms the breach exposed prospective Google Ads customers' contact info (&lt;a href=&quot;https://www.bleepingcomputer.com/news/security/google-confirms-data-breach-exposed-potential-google-ads-customers-info/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-06-04: Google Threat Intelligence describes UNC6040's vishing and Data Loader abuse (&lt;a href=&quot;https://cloud.google.com/blog/topics/threat-intelligence/voice-phishing-data-extortion&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-06: Google's corporate Salesforce instance breached by UNC6040 (&lt;a href=&quot;https://www.bleepingcomputer.com/news/security/google-suffers-data-breach-in-ongoing-salesforce-data-theft-attacks/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
</channel>
</rss>
