Search This Blog

Powered by Blogger.

Blog Archive

Labels

Footer About

Footer About

Labels

Showing posts with label Drift OAuth token hack. Show all posts

Russian Hackers Use Exchange Zero-Day in Email Attacks

 



Russia-aligned cyberespionage group Laundry Bear, also tracked as Void Blizzard and TA488, is exploiting a Microsoft Exchange Outlook Web Access (OWA) vulnerability to deploy a browser-based backdoor capable of maintaining access to victims' mailboxes even after credentials are changed or systems are reimaged.

Email security firm Proofpoint said it observed the campaign targeting government organizations in the US and Europe, as well as telecommunications, financial, hospitality and aerospace organizations. The activity uses OWAReaper, a sophisticated backdoor delivered through malicious emails exploiting CVE-2026-42897.

CVE-2026-42897 is a cross-site scripting vulnerability caused by inadequate HTML sanitization in OWA. A specially crafted email can contain malicious JavaScript that executes when the recipient opens the message in OWA. Proofpoint calls the technique a "half-click" exploit because opening the email can be enough to trigger the attack, without requiring the victim to click a link or open an attachment. Microsoft disclosed the vulnerability on May 14, 2026, and confirmed active exploitation.

Proofpoint found that infrastructure associated with the campaign had been established as early as March, nearly two months before Microsoft's disclosure, suggesting TA488 may have exploited the vulnerability as a zero-day. The group used ordinary-looking subjects concerning supply chains, research updates, tourism, gas markets and other industry-related information, making the messages less likely to be treated as malicious.

The emails contained JavaScript loaders and Base64-encoded payload fragments hidden within URLs associated with social-media-style icons. Once triggered, the code assembled and executed the OWAReaper payload.

OWAReaper operates entirely within the OWA reading pane. It can collect the victim's email address, username and Outlook configuration, while also attempting to capture credentials by creating invisible DOM elements that allow the browser's autofill mechanism to populate usernames and passwords.

The backdoor's most concerning capability is its persistence. It searches for Outlook add-ins with "ReadWriteMailbox" permissions and can use the "GetClientAccessToken" operation to obtain OAuth tokens. It then abuses Exchange's "UpdateFolder" operation to grant Owner-level permissions to the "Default" user across the victim's mail folders.

Because these permissions are stored server-side, changing the victim's password or reinstalling the compromised computer does not necessarily remove the attacker's access. OWAReaper also enables browser caching and places a malicious iframe into messages stored in OWA's offline IndexedDB database, allowing the payload to execute again when a poisoned message is opened from the cache.

The malware uses multiple channels for command and control. It periodically searches GitHub commit messages for encrypted commands containing the victim's email address and can also receive commands through specially formatted emails stored in OWA's cache.

For data theft, OWAReaper primarily uses HTTPS with encrypted URI paths that can be routed through image CDN services. It also has a direct-server fallback and a DNS-based exfiltration mechanism that encrypts and Base32-encodes stolen data before transmitting it through DNS queries.

Proofpoint linked OWAReaper to TA488 based on behavioral similarities with ZimReaper, malware previously used by the group against Zimbra email servers. In that campaign, TA488 exploited another XSS flaw, CVE-2025-66376, to steal emails, passwords, application passcodes and two-factor authentication codes.

The latest campaign therefore represents an evolution of the group's "half-click" approach, shifting from compromising individual webmail sessions toward establishing persistent access within the victim's mailbox environment.

Microsoft has since released security updates addressing CVE-2026-42897. The July 2026 Exchange Server update states that the code fix is available, while organizations that previously applied Microsoft's mitigation must follow Microsoft's guidance to remove it after installing the update. The vulnerability affects on-premises Exchange Server deployments, while Exchange Online is not affected.

Proofpoint has published indicators of compromise for the campaign, including malicious domains and the HTML message body containing the exploit and OWAReaper payload. Organizations using affected on-premises Exchange deployments should therefore investigate not only compromised endpoints, but also mailbox permissions, OAuth tokens and OWA browser storage when responding to suspected exploitation.

ShinyHunters Claims Theft of 1.5 Billion Salesforce Records Using Compromised Drift OAuth Tokens

 




The ShinyHunters extortion group has allegedly stolen more than 1.5 billion Salesforce records from 760 companies after exploiting compromised Salesloft Drift OAuth tokens.

Over the past year, cybercriminals have been targeting Salesforce customers through social engineering tactics and malicious OAuth apps, enabling unauthorized access to Salesforce environments and mass data downloads. The stolen information is later used to pressure organizations into paying ransoms to prevent public leaks.

These campaigns have been linked to members of ShinyHunters, Scattered Spider, and Lapsus$, who are now referring to themselves as "Scattered Lapsus$ Hunters." Google tracks these operations under the names UNC6040 and UNC6395.

In March, one of the attackers infiltrated Salesloft’s GitHub repository, which stored private source code. ShinyHunters told BleepingComputer that they leveraged the TruffleHog security tool to uncover OAuth tokens hidden in the code. These tokens gave them access to both the Salesloft Drift platform—used to sync Drift AI chat agents with Salesforce—and Drift Email, which manages CRM email communications and marketing automation.

Using the stolen OAuth tokens, attackers exfiltrated around 1.5 billion records from key Salesforce object tables: Account, Contact, Case, Opportunity, and User. The stolen datasets included:

  • 250 million Account records

  • 579 million Contact records

  • 171 million Opportunity records

  • 60 million User records

  • 459 million Case records

The Case table, in particular, contained sensitive customer support ticket details, potentially exposing confidential information from tech company clients.

As proof, attackers shared a file listing Salesloft’s breached GitHub source code folders. While Salesloft did not respond to inquiries, a source confirmed the figures are accurate.

According to Google Threat Intelligence (Mandiant), attackers searched the stolen Case data for credentials, authentication tokens, and access keys to pivot into additional environments.
"After the data was exfiltrated, the actor searched through the data to look for secrets that could be potentially used to compromise victim environments," Google explained.
"GTIG observed UNC6395 targeting sensitive credentials such as Amazon Web Services (AWS) access keys (AKIA), passwords, and Snowflake-related access tokens."

The massive breach impacted numerous companies, including Google, Cloudflare, Zscaler, Tenable, CyberArk, Elastic, BeyondTrust, Proofpoint, JFrog, Nutanix, Qualys, Rubrik, Cato Networks, and Palo Alto Networks.

The FBI has since issued an advisory warning about the UNC6040 and UNC6395 groups, sharing indicators of compromise (IOCs) to help organizations defend against similar attacks.

Despite announcing they would “go dark” on Telegram, the attackers later claimed to have accessed Google’s Law Enforcement Request System (LERS) and the FBI eCheck platform. Google later confirmed, "We have identified that a fraudulent account was created in our system for law enforcement requests and have disabled the account. No requests were made with this fraudulent account, and no data was accessed."

Although the group suggested they were retiring, ReliaQuest researchers noted that in July 2025, they shifted focus toward financial institutions, making it likely these campaigns will continue.

To defend against such threats, Salesforce urges customers to enforce strong security measures, including multi-factor authentication (MFA), applying the principle of least privilege, and carefully vetting connected applications.