> 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/suspicious-docker-image-download-from-an-unusual-repository.md).

# Suspicious docker image download from an unusual repository

### 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                                   |
| Detector Tags        | Kubernetes - AGENT, Containers              |
| ATT\&CK Tactic       | Execution (TA0002)                          |
| ATT\&CK Technique    | User Execution: Malicious Image (T1204.003) |
| Severity             | Informational                               |

### Description

The agent has pulled a docker image from a repository for the first time.

### Attacker's Goals

Adversaries may rely on a user running a malicious image to facilitate execution.

### Investigative actions

* Scan the docker image that was pulled.
* Check the repository designation.
* Check on which other agents the docker image is being used.

### Variations

<details>

<summary>Suspicious docker image download from an unrecognized registry</summary>

**Synopsis**

| Field             | Value                                       |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002)                          |
| ATT\&CK Technique | User Execution: Malicious Image (T1204.003) |
| Severity          | Low                                         |

**Description**

The agent has pulled a docker image from a registry that has never been used in the organization.

**Attacker's Goals**

Adversaries may rely on a user running a malicious image to facilitate execution.

**Investigative actions**

* Scan the docker image that was pulled.
* Check the repository designation.
* Check on which other agents the docker image is being used.

</details>

<details>

<summary>Suspicious docker image download from an unrecognized repository</summary>

**Synopsis**

| Field             | Value                                       |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic    | Execution (TA0002)                          |
| ATT\&CK Technique | User Execution: Malicious Image (T1204.003) |
| Severity          | Low                                         |

**Description**

The agent has pulled a docker image from a repository that has never been used in the organization.

**Attacker's Goals**

Adversaries may rely on a user running a malicious image to facilitate execution.

**Investigative actions**

* Scan the docker image that was pulled.
* Check the repository designation.
* Check on which other agents the docker image is being used.

</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 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/suspicious-docker-image-download-from-an-unusual-repository.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.
