> 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-heavy-allocation-of-compute-resources-possible-mining-activity.md).

# Suspicious heavy allocation of compute resources - possible mining activity

### Synopsis

| Field                | Value                                                                                                   |
| -------------------- | ------------------------------------------------------------------------------------------------------- |
| Activation Period    | 14 Days                                                                                                 |
| Training Period      | 30 Days                                                                                                 |
| Test Period          | N/A (single event)                                                                                      |
| Deduplication Period | 5 Days                                                                                                  |
| Required Data        | <p>Requires one of the following data sources:<br>AWS Audit Log OR Azure Audit Log OR Gcp Audit Log</p> |
| Detection Modules    | Cloud                                                                                                   |
| ATT\&CK Tactic       | Impact (TA0040), Initial Access (TA0001)                                                                |
| ATT\&CK Technique    | Resource Hijacking (T1496), Valid Accounts (T1078)                                                      |
| Severity             | Medium                                                                                                  |

### Description

An identity allocated an unusual heavy compute resource, suspected as mining activity. Heavy machines normally have a high amount of CPU cores or attached with GPU, which are targeted by adversaries to mine Cryptocurrency.

### Attacker's Goals

Leverage cloud compute resources to earn virtual currency.

### Investigative actions

* Check the identity created resources and its legitimacy.
* Look for any unusual behavior originated from the suspected identity, and check if they're compromised, e.g. access key, service account, etc.

### Variations

<details>

<summary>Suspicious heavy allocation of compute resources - possible mining activity</summary>

**Synopsis**

| Field             | Value                                              |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic    | Impact (TA0040), Initial Access (TA0001)           |
| ATT\&CK Technique | Resource Hijacking (T1496), Valid Accounts (T1078) |
| Severity          | Low                                                |

**Description**

An identity allocated an unusual heavy compute resource, suspected as mining activity. Heavy machines normally have a high amount of CPU cores or attached with GPU, which are targeted by adversaries to mine Cryptocurrency.

**Attacker's Goals**

Leverage cloud compute resources to earn virtual currency.

**Investigative actions**

* Check the identity created resources and its legitimacy.
* Look for any unusual behavior originated from the suspected identity, and check if they're compromised, e.g. access key, service account, etc.

</details>

<details>

<summary>Suspicious heavy allocation of compute resources - possible mining activity</summary>

**Synopsis**

| Field             | Value                                              |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic    | Impact (TA0040), Initial Access (TA0001)           |
| ATT\&CK Technique | Resource Hijacking (T1496), Valid Accounts (T1078) |
| Severity          | High                                               |

**Description**

An identity allocated an unusual heavy compute resource, suspected as mining activity. Heavy machines normally have a high amount of CPU cores or attached with GPU, which are targeted by adversaries to mine Cryptocurrency.

**Attacker's Goals**

Leverage cloud compute resources to earn virtual currency.

**Investigative actions**

* Check the identity created resources and its legitimacy.
* Look for any unusual behavior originated from the suspected identity, and check if they're compromised, e.g. access key, service account, etc.

</details>

<details>

<summary>Suspicious heavy allocation of compute resources - possible mining activity</summary>

**Synopsis**

| Field             | Value                                              |
| ----------------- | -------------------------------------------------- |
| ATT\&CK Tactic    | Impact (TA0040), Initial Access (TA0001)           |
| ATT\&CK Technique | Resource Hijacking (T1496), Valid Accounts (T1078) |
| Severity          | Medium                                             |

**Description**

An identity allocated an unusual heavy compute resource, suspected as mining activity. Heavy machines normally have a high amount of CPU cores or attached with GPU, which are targeted by adversaries to mine Cryptocurrency.

**Attacker's Goals**

Leverage cloud compute resources to earn virtual currency.

**Investigative actions**

* Check the identity created resources and its legitimacy.
* Look for any unusual behavior originated from the suspected identity, and check if they're compromised, e.g. access key, service account, etc.

</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/suspicious-heavy-allocation-of-compute-resources-possible-mining-activity.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.
