> 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/screensaver-process-executed-from-users-or-temporary-folder.md).

# Screensaver process executed from Users or temporary folder

### Synopsis

| Field                | Value                                              |
| -------------------- | -------------------------------------------------- |
| Activation Period    | 14 Days                                            |
| Training Period      | 30 Days                                            |
| Test Period          | N/A (single event)                                 |
| Deduplication Period | 6 Hours                                            |
| Required Data        | XDR Agent                                          |
| ATT\&CK Tactic       | Persistence (TA0003)                               |
| ATT\&CK Technique    | Event Triggered Execution: Screensaver (T1546.002) |
| Severity             | Low                                                |

### Description

An executable file with a screensaver extension was executed from the Users or temp folder. This is not a common behavior for screensavers and may indicate a malicious file disguised as a screensaver in the Users or temp folder. It is recommended to further investigate the execution flow for malicious indicators.

### Attacker's Goals

Gain persistence by configuring a new screensaver.

### Investigative actions

Check whether the executing process (with the SCR extension) is benign and if this was a desired behavior as part of its normal execution flow.

### Variations

<details>

<summary>Screensaver process executed from Users or temporary folder by a scripting engine process</summary>

**Synopsis**

| Field             | Value                                              |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003)                               |
| ATT\&CK Technique | Event Triggered Execution: Screensaver (T1546.002) |
| Severity          | High                                               |

**Description**

An executable file with a screensaver extension was executed from the Users or temp folder by a scripting engine process. This is not a common behavior for screensavers and may indicate a malicious file disguised as a screensaver in the Users or temp folder. It is recommended to further investigate the execution flow for malicious indicators.

**Attacker's Goals**

Gain persistence by configuring a new screensaver.

**Investigative actions**

Check whether the executing process (with the SCR extension) is benign and if this was a desired behavior as part of its normal execution flow.

</details>


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/analytics-alerts/alerts-by-name/screensaver-process-executed-from-users-or-temporary-folder.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
