> 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/conhost-exe-spawned-a-suspicious-cmd-process.md).
# Conhost.exe spawned a suspicious cmd process
### 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 | LOLBIN Execution Analytics |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | System Binary Proxy Execution (T1218) |
| Severity | Low |
### Description
Attackers may abuse the conhost process to execute malicious files and evade detection.
### Attacker's Goals
Investigate the processes being spawned on the host for malicious activities.
### Investigative actions
An adversary may use the conhost process to evade detection.
### Variations
Conhost.exe spawned a suspicious powershell encoded command
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | System Binary Proxy Execution (T1218) |
| Severity | High |
**Description**
Attackers may abuse the conhost process to execute malicious files and evade detection.
**Attacker's Goals**
Investigate the processes being spawned on the host for malicious activities.
**Investigative actions**
An adversary may use the conhost process to evade detection.
Conhost.exe spawned a suspicious scripting process with long command line
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | System Binary Proxy Execution (T1218) |
| Severity | Medium |
**Description**
Attackers may abuse the conhost process to execute malicious files and evade detection.
**Attacker's Goals**
Investigate the processes being spawned on the host for malicious activities.
**Investigative actions**
An adversary may use the conhost process to evade detection.
Conhost.exe spawned a suspicious child process
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | System Binary Proxy Execution (T1218) |
| Severity | Medium |
**Description**
Attackers may abuse the conhost process to execute malicious files and evade detection.
**Attacker's Goals**
Investigate the processes being spawned on the host for malicious activities.
**Investigative actions**
An adversary may use the conhost process to evade detection.
---
# 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/conhost-exe-spawned-a-suspicious-cmd-process.md?ask=&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.