What happened
Replaying the VEILDrive September 2024 intrusion
- 1
Teams chat, then remote control
Early September 2024; times not statedA compromised Microsoft 365 account of another organization messages four employees in Teams as IT support; one opens Quick Assist with the code the attacker sends and hands over the device.
- 2
Tools from another tenant's SharePoint
Early September 2024; times not statedA link in the chat to a password-protected archive in a third organization's SharePoint delivers a remote management tool, and a scheduled task created by hand keeps it running.
- 3
The Java implant
Early September 2024; times not statedA second archive sent through the same chat delivers a Java implant with its own runtime, and a Run key in the user's registry starts it at logon.
- 4
Command channels in Microsoft's cloud
Early September 2024; times not statedThe implant redeems hard-coded credentials of attacker-registered applications at Microsoft Entra ID and polls OneDrive files in the actor's tenants for commands, with a second channel to an Azure address.
The attacker held interactive and persistent control of one Org C device through a remote management tool and a Java implant with two command channels; containment was very rapid, with no sign of significant damage.
Where Microsoft Teams and Entra controls fit
Teams external access set to Block all external domains would have refused the chat from another organization's account, so the lure, the Quick Assist code and both archives would have had no channel. An allow list of partner domains narrows who can chat, but the report does not say whether the sending organization would have been on it. A tenant restrictions v2 policy that blocks all external tenants makes Microsoft Entra ID refuse sign-ins to other tenants that carry its signal, which your proxy or Global Secure Access adds to a device's sign-in traffic. The report does not say which network the device was on, and Microsoft's page does not name a refresh token request, so the policy narrows the implant's token path and is not shown to close it. Quick Assist, the scheduled task, the implant and its Run key sit on the device, and the socket to the Azure address leaves through the device's own network path: those belong to your endpoint and network controls. Check whether your tenant still allows external chat from all domains, the Teams default.
Could this have been prevented?
In hindsight, not as a whole. 1 control would have refused a step outright, and 2 controls would have limited one. 6 steps have no cloud-provider control. The counts below are control assessments, not attack stages: several can address the same step. The same replay with the controls in place before the incident shows where each phase would have been refused or bounded.
- 1
- Prevented
- 2
- Contained
- 6
- Not covered
How it could have been prevented
The same replay with the controls in place. Green marks where a step is refused, blue where it is bounded, and red where no control reaches it. Open a row to read the control, why it acts, and its caveat.
Replaying the VEILDrive September 2024 intrusion
1 · Teams chat, then remote control
1 Prevented1 Contained1 Not covered2 · Tools from another tenant's SharePoint
2 Not covered3 · The Java implant
2 Not covered4 · Command channels in Microsoft's cloud
1 Contained1 Not coveredKey facts
- Hunters Team AXON estimated that the campaign began in early August 2024; Org C, a US critical infrastructure entity, engaged the team in early September 2024 after an alert on a suspicious scheduled task
- A compromised user account of Org A, described as a potential previous victim, messaged four non-technical Org C employees one on one in Teams, posing as IT support; only one accepted the remote-access request, and how the Org A account was compromised was not stated
- The attacker sent a Quick Assist session code in the chat, which gave it interactive control of the device, then delivered a remote management tool in a password-protected archive from the SharePoint of a separate organization, Org B, and kept it running with a scheduled task created by hand
- A Java implant with a bundled runtime, started at logon by a Run key, carried a refresh token, a client ID and a client secret of applications the report lists as attacker-registered, and used Microsoft Graph to read and write command, flag and result files in OneDrive accounts of tenants supposedly owned by the actor
- The implant also received PowerShell commands over an HTTPS socket to an address in Azure's range that the report calls very likely an actor-owned virtual machine; it was unobfuscated yet evaded a top-tier EDR and every VirusTotal engine at the time
- Containment and eradication were very rapid, with no sign of significant damage; Team AXON reported the infrastructure to Microsoft and assessed a probable Russian origin, an assessment rather than an attribution
Sources
Every fact in this breakdown comes from the public reporting below. The replay is a model of that reporting, not a reconstruction of the environment it describes.
- 1.Unmasking VEILDrive: Threat Actors Exploit Microsoft Services for Command & ControlHunters (Team AXON) · Dec 10, 2024 · ResearchTeams lure, Quick Assist session, SharePoint-hosted archives, scheduled task and Run key, the Java implant, the Entra app credentials and the OneDrive channel, the Azure VM channel, detection and containment, recommendations
The estate in the replay is illustrative and drawn at the level of attack stages; the victim's real environment is not public. Verdicts describe what a control does when it is in place before the incident. They are not an assessment of the victim's security program.