


Perceptive Security
SOC/SIEM Consultancy

Russian Hackers Exploit Microsoft OWA Flaw to Keep Mailbox Access After Credential Rotation
Published:
30 July 2026 at 09:40:48
Alert date:
30 July 2026 at 10:03:15
Source:
thehackernews.com
Email & Messaging, Zero-Day Vulnerabilities, Ransomware & Malware, Identity & Access, Data Breach & Exfiltration, Web Technologies
Russian threat actors previously linked to Zimbra vulnerability exploitation have shifted to targeting Microsoft Outlook Web Access (OWA). The campaign began on July 22, 2026, and targets U.S. and European government entities, as well as telecommunications, financial, hospitality, and aerospace sectors. The attackers are exploiting a flaw in OWA to maintain persistent mailbox access even after victim organizations rotate their credentials. This technique allows the threat actors to sustain access despite defensive measures typically used to evict unauthorized users. The activity represents a continuation and escalation of Russian state-sponsored cyber espionage targeting Western institutions and critical sectors.
Technical details
The Russian threat actor TA488 (Laundry Bear) has been exploiting CVE-2026-42897, a cross-site scripting (XSS) vulnerability (CVSS 8.1) in Microsoft Outlook Web Access (OWA), active since July 22, 2026. The attack chain uses 'half-click' exploits where simply opening/viewing a phishing email triggers compromise — no user interaction such as clicking links or opening attachments is required. Emails are sent from compromised accounts and adversary-controlled Proton Mail addresses, using generic lures (supply chain analyses, research updates, tourism/gas market metrics) to avoid suspicion. The exploit leverages the onload= event handler to parse the email body, assemble a Base64 fragment, and execute encoded JavaScript. Exploit trigger and payload blobs are hidden in social media icon HTML, with next-stage payload data stored after '#' symbols. The payload deployed is OWAReaper, a JavaScript browser-based implant that: (1) executes within the OWA reading pane; (2) uses Outlook APIs to rewrite the email on the Exchange server and remove exploit content; (3) disables OWA pop-ups and right-click; (4) creates a unique session key; (5) gathers target email address, username, and Outlook settings; (6) creates invisible DOM input elements to capture OWA saved credentials via browser autofill; (7) writes an encrypted version of itself and a decryption wrapper into browser localStorage for persistence across OWA tab opens; (8) checks for Outlook add-ins with ReadWriteMailbox permissions to steal OAuth tokens and grants itself Owner-level permissions to the Default user on every mail folder, allowing complete mailbox access to any authenticated user in the organization — this persistence is server-side and survives credential rotation and full device re-imaging; (9) creates a second persistence method by injecting a hidden iframe into messages stored in OWA's offline IndexedDB message cache, re-infecting upon opening cached emails. C2 uses two methods: querying GitHub's Commit Search API every 24 hours for commit messages containing the target's email address (commands encrypted with a hard-coded key and per-session AES key), and parsing inbound emails from TA488 operators with structure {target_email_address}{space}{Base64text} from IndexedDB. Supported commands include 'code' (replace OWAReaper toolkit), 'domn' (rotate C2 servers), and 'cmnd' (execute arbitrary JavaScript via eval()). Data exfiltration uses AES-CTR encrypted URI paths over HTTPS; fallback is DNS label tunneling within DNS queries to an actor-controlled domain. Infrastructure was created as early as March 2026, two months before Microsoft's disclosure of CVE-2026-42897, suggesting possible zero-day exploitation. OWAReaper is an evolution of the ZimReaper malware previously used against Zimbra (CVE-2025-66376), sharing significant source code and behavioral overlaps.
Mitigation steps:
1. Apply Microsoft's patch for CVE-2026-42897 immediately on all on-premises Microsoft Exchange/OWA deployments. 2. Audit Exchange server mailbox folder permissions for unauthorized Owner-level permissions granted to the 'Default' user on any mail folders, and remove them — credential rotation and device re-imaging alone will NOT evict the actor due to server-side persistence. 3. Review and audit installed Outlook add-ins with ReadWriteMailbox permissions for legitimacy; remove unauthorized or suspicious add-ins. 4. Inspect OWA offline IndexedDB message caches and stored emails for hidden iframes or suspicious content. 5. Clear browser localStorage on affected user endpoints to remove the encrypted OWAReaper persistence mechanism. 6. Monitor for unusual OAuth token activity and unauthorized mailbox delegation or permission changes on Exchange. 7. Block or monitor outbound DNS queries exhibiting DNS label tunneling patterns to unknown or suspicious domains. 8. Monitor outbound HTTPS traffic for AES-CTR encrypted URI path patterns to unknown actor-controlled domains. 9. Monitor GitHub API queries originating from internal systems, specifically to the Commit Search API. 10. Implement email security controls to flag or quarantine emails from Proton Mail accounts or other free webmail providers impersonating internal or trusted senders. 11. Educate users that simply opening/previewing an email can trigger compromise with this exploit class; consider disabling the reading pane in OWA temporarily until patched. 12. Hunt for the presence of OWAReaper and ZimReaper JavaScript implants across endpoints and webmail environments. 13. Correlate inbound emails with the {target_email_address}{space}{Base64text} structure in mailbox stores as a potential C2 indicator. 14. Review and restrict Outlook add-in permissions, particularly ReadWriteMailbox, to only trusted and necessary add-ins.
Affected products:
Microsoft Outlook Web Access (OWA)
Microsoft Exchange Server (on-premises)
Zimbra Classic UI (CVE-2025-66376
patched)
Related links:
https://www.proofpoint.com/us/blog/threat-insight/cleaning-out-inboxes-ta488-comes-outlook-another-half-click-exploit
https://thehackernews.com/2026/05/on-prem-microsoft-exchange-server-cve.html
https://thehackernews.com/2026/07/fake-notepad-plugin-delivers.html
https://developer.mozilla.org/en-US/docs/Web/API/Window/load_event
Related CVE's:
Related threat actors:
IOC's:
Malware: OWAReaper (JavaScript browser-based implant), Malware: ZimReaper (JavaScript payload, Zimbra-targeting predecessor), C2 method: GitHub Commit Search API queries containing target email addresses, C2 method: Inbound emails with structure {target_email_address}{space}{Base64text} in IndexedDB, Data exfiltration: AES-CTR encrypted URI paths over HTTPS to actor-controlled domain, Data exfiltration fallback: DNS label tunneling to actor-controlled domain, Email sender infrastructure: adversary-controlled Proton Mail accounts, Email sender infrastructure: previously compromised email accounts, Persistence: OWAReaper stored encrypted in browser localStorage, Persistence: hidden iframe injected into OWA offline IndexedDB message cache, Persistence: Owner-level permissions granted to Default user on Exchange mail folders, Campaign infrastructure creation date: March 2026, Campaign active date: July 22, 2026
This article was created with the assistance of AI technology by Perceptive.
