> 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/windows-installer-exploitation-for-local-privilege-escalation.md).

# Windows Installer exploitation for local privilege escalation

### Synopsis

| Field                | Value                                         |
| -------------------- | --------------------------------------------- |
| Activation Period    | 14 Days                                       |
| Training Period      | 30 Days                                       |
| Test Period          | N/A (single event)                            |
| Deduplication Period | 1 Day                                         |
| Required Data        | XDR Agent                                     |
| ATT\&CK Tactic       | Privilege Escalation (TA0004)                 |
| ATT\&CK Technique    | Exploitation for Privilege Escalation (T1068) |
| Severity             | Medium                                        |

### Description

The Windows installer (msiexec.exe) was likely exploited to run a malicious rollback script (.rbs file) instead of the original. Users should not be able to modify config.msi during the installation process, only SYSTEM should have access to it.

### Attacker's Goals

An attacker is attempting to gain SYSTEM privileges.

### Investigative actions

* Investigate the actor process SID and path and whether it's benign or normal for this host.
* This action is not common, but allowed on Windows versions older than Windows 8. On those systems, check the file reputation for both the CGO and OS actor executables that ran the installation.


---

# 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/windows-installer-exploitation-for-local-privilege-escalation.md?ask=<question>&goal=<user_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.