CSuite Phishing Hijacks Microsoft 365 Sessions

A financially motivated phishing operation called CSuite is stealing Microsoft 365 sessions and installing legitimate remote-management software on victims' computers, turning a single successful phishing email into both account takeover and lasting remote control of the machine.

Key facts

  • What happened: ANY.RUN researchers traced the CSuite campaign across 351 sandbox analyses, with 51% of submissions from the United States

  • Who's targeted: Technology, manufacturing, government and consulting organizations in the US and Europe, with executives a focus

  • Two attack paths: Microsoft 365 credential and session theft, or installation of remote-management tools

  • The tools abused: ScreenConnect, Action1, Atera, Syncro and PDQ Connect — all legitimate software

  • Lure themes: Microsoft 365, Adobe, DocuSign, Zoom, Dropbox, SharePoint and OneDrive

  • Active since: February 2026, with related activity continuing through at least early September

What makes this campaign different?

It attacks the account and the computer, through the same operation.

One path pushes victims into credential-harvesting or device-code phishing flows designed to capture Microsoft 365 logins and active sessions. Device-code phishing abuses a legitimate sign-in method meant for devices without keyboards, tricking a user into approving the attacker's session.

Stealing an active session matters more than stealing a password. A session token is the proof your browser holds that you already logged in — so an attacker holding one can be inside a mailbox without ever knowing the password, and without triggering a multifactor prompt.

The second path delivers an archive, MSI, BAT or VBS file that installs legitimate remote-management software. In one ANY.RUN sandbox session, an Adobe-themed lure delivered a BAT file that elevated privileges and installed ScreenConnect.

Why is legitimate software being used as malware?

Because it doesn't look like malware. ScreenConnect, Atera, Syncro and PDQ Connect are real remote-monitoring and management tools — RMM software — used by IT departments and managed service providers to administer computers remotely.

Antivirus products do not flag them. Security teams see them in the environment every day. An attacker who installs one gets persistent remote control that survives the original phishing incident and blends into normal IT activity.

What does a successful CSuite compromise lead to?

Researchers list mailbox takeover, invoice and payment fraud, persistent remote access, follow-on phishing sent from a trusted account, and broader compromise across identity and endpoint systems.

The payment-fraud angle connects directly to business email compromise. An attacker inside an executive's mailbox can read real supplier conversations and insert a payment instruction at exactly the right moment.

One CSuite panel exposed records for 216 phishing victims, 29 captured Microsoft 365 sessions, 1,593 Adobe lure documents and 15,955 harvested email addresses. Roughly 60% of identified victims were US-based.

Why is this hard to clean up?

Because it shows up as three separate problems. The same operation can surface as a phishing alert, an anomalous Microsoft 365 sign-in, or an unexpected management-agent installation — and a team that handles only one has not finished.

Containment requires revoking sessions, investigating mailbox activity, removing unauthorized management tools and cleaning affected endpoints at the same time. Resetting the password alone does not end an active session or remove the installed software.

What should businesses do?

Four things, roughly in order of value.

Deploy phishing-resistant authentication — hardware keys or passkeys — for executives and finance staff first, since these resist both credential theft and session capture better than app-based codes.

Build an inventory of which remote-management tools your organization legitimately uses, then alert on any others appearing. If you do not use Atera, an Atera installation is an incident.

Treat an unexpected Microsoft 365 sign-in approval request as an attack in progress. If you did not initiate it, someone else did.

Train finance staff to verify payment changes by phone, because a mailbox takeover makes the fraudulent request come from a real, trusted address.