> 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/an-unsigned-process-created-scheduled-task-and-performed-an-injection.md).

# An unsigned process created scheduled task and performed an injection

### Synopsis

| Field                | Value                                                                     |
| -------------------- | ------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                   |
| Training Period      | 30 Days                                                                   |
| Test Period          | 4 Hours                                                                   |
| Deduplication Period | 1 Day                                                                     |
| Required Data        | XDR Agent                                                                 |
| Detector Tags        | Scheduled tasks Analytics                                                 |
| ATT\&CK Tactic       | Persistence (TA0003), Defense Evasion (TA0005)                            |
| ATT\&CK Technique    | Scheduled Task/Job: Scheduled Task (T1053.005), Process Injection (T1055) |
| Severity             | Medium                                                                    |

### Description

An unsigned process created scheduled task and performed an injection.

### Attacker's Goals

To ensure they have persistence on the system, the threat actor may use scheduled tasks to set persistence, Then, to avoid detection and carry out stealth execution, they may inject a malicious payload into a remote process.

### Investigative actions

* Investigate the injection payload and the injection process.
* Check if the scheduled task trigger payload is malicious.

### Variations

<details>

<summary>Possible an unsigned installer created scheduled task and performed an injection</summary>

**Synopsis**

| Field             | Value                                                                     |
| ----------------- | ------------------------------------------------------------------------- |
| ATT\&CK Tactic    | Persistence (TA0003), Defense Evasion (TA0005)                            |
| ATT\&CK Technique | Scheduled Task/Job: Scheduled Task (T1053.005), Process Injection (T1055) |
| Severity          | Low                                                                       |

**Description**

Possible an unsigned installer created scheduled task and performed an injection.

**Attacker's Goals**

To ensure they have persistence on the system, the threat actor may use scheduled tasks to set persistence, Then, to avoid detection and carry out stealth execution, they may inject a malicious payload into a remote process.

**Investigative actions**

* Investigate the injection payload and the injection process.
* Check if the scheduled task trigger payload is malicious.

</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/an-unsigned-process-created-scheduled-task-and-performed-an-injection.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.
