> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/azure-vm-extension-abuse-attempt.md).
# Azure VM extension abuse attempt
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Azure Audit Log |
| Detection Modules | Cloud |
| ATT\&CK Tactic | Execution (TA0002), Persistence (TA0003), Defense Impairment (TA0112) |
| ATT\&CK Technique | Cloud Administration Command (T1651), Command and Scripting Interpreter: Cloud API (T1059.009), Account Manipulation (T1098), Disable or Modify Tools (T1685) |
| Severity | Informational |
### Description
A suspicious Azure VM extension operation was detected. Attackers can use CustomScriptExtension to execute arbitrary scripts on VMs, VMAccessExtension to reset local passwords for persistence, or delete the IaaSAntimalware extension to disable antimalware protection and evade detection.
### Attacker's Goals
* Execute arbitrary code on VMs without network access (CustomScriptExtension).
* Gain persistent access by resetting local admin passwords (VMAccessExtension).
* Disable antimalware to deploy malware undetected (IaaSAntimalware deletion).
### Investigative actions
* Identify the extension type involved (CustomScriptExtension, VMAccessExtension, IaaSAntimalware).
* For CustomScriptExtension: review the script payload executed on the VM.
* For VMAccessExtension: check if local admin credentials were reset and audit subsequent logins.
* For IaaSAntimalware deletion: verify the virtual machine audit log after the extension was removed.
* Verify whether the identity performing the operation is authorized to manage VM extensions.
* Check for correlated suspicious activity such as new role assignments or lateral movement.
### Variations
Unusual azure VM extension abuse
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Execution (TA0002), Persistence (TA0003), Defense Impairment (TA0112) |
| ATT\&CK Technique | Cloud Administration Command (T1651), Command and Scripting Interpreter: Cloud API (T1059.009), Account Manipulation (T1098), Disable or Modify Tools (T1685) |
| Severity | Low |
**Description**
A suspicious Azure VM extension operation was detected. Attackers can use CustomScriptExtension to execute arbitrary scripts on VMs, VMAccessExtension to reset local passwords for persistence, or delete the IaaSAntimalware extension to disable antimalware protection and evade detection.
**Attacker's Goals**
* Execute arbitrary code on VMs without network access (CustomScriptExtension).
* Gain persistent access by resetting local admin passwords (VMAccessExtension).
* Disable antimalware to deploy malware undetected (IaaSAntimalware deletion).
**Investigative actions**
* Identify the extension type involved (CustomScriptExtension, VMAccessExtension, IaaSAntimalware).
* For CustomScriptExtension: review the script payload executed on the VM.
* For VMAccessExtension: check if local admin credentials were reset and audit subsequent logins.
* For IaaSAntimalware deletion: verify the virtual machine audit log after the extension was removed.
* Verify whether the identity performing the operation is authorized to manage VM extensions.
* Check for correlated suspicious activity such as new role assignments or lateral movement.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/azure-vm-extension-abuse-attempt.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.