> 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/a-process-connected-to-a-rare-external-host.md).
# A process connected to a rare external host
### 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 |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Application Layer Protocol (T1071) |
| Severity | Informational |
### Description
A process connected to an external host name or directly to an IP address, which is rarely connected to from the organization.
### Attacker's Goals
Beacon to C2 server and/or exfiltrate data.
### Investigative actions
Check whether the process was injected or otherwise subverted for malicious use.
### Variations
MSBuild process connected to a rare external host
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005), Command and Control (TA0011) |
| ATT\&CK Technique | Trusted Developer Utilities Proxy Execution: MSBuild (T1127.001), Application Layer Protocol (T1071) |
| Severity | High |
**Description**
MSBuild normally does not make any network connections. This unusual activity may be malicious since attackers can leverage MSBuild for code execution.
**Attacker's Goals**
Beacon to C2 server and/or exfiltrate data.
**Investigative actions**
Check if CGO actor process is not code developing tool (IDE) and whether the actor process subverted for malicious use.
MSBuild process connected to a rare external host
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------- |
| ATT\&CK Tactic | Stealth (TA0005) |
| ATT\&CK Technique | Trusted Developer Utilities Proxy Execution: MSBuild (T1127.001) |
| Severity | Medium |
**Description**
MSBuild normally does not make any network connections. This unusual activity may be malicious since attackers can leverage MSBuild for code execution.
**Attacker's Goals**
Beacon to C2 server and/or exfiltrate data.
**Investigative actions**
Check if CGO actor process is not code developing tool (IDE) and whether the actor process subverted for malicious use.
LOLBIN spawned by an Office executable connected to a rare external host
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Application Layer Protocol (T1071) |
| Severity | High |
**Description**
A LOLBIN run by an Office process connected to an external IP address or host, which is rarely connected to from the organization.
**Attacker's Goals**
Beacon to C2 server and/or exfiltrate data.
**Investigative actions**
Check whether the process was injected or otherwise subverted for malicious use.
A curl process connected to a rare external host
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Application Layer Protocol (T1071) |
| Severity | Informational |
**Description**
A process connected to an external host name or directly to an IP address, which is rarely connected to from the organization.
**Attacker's Goals**
Beacon to C2 server and/or exfiltrate data.
**Investigative actions**
Check whether the process was injected or otherwise subverted for malicious use.
VSCode extension process connected to a rare external host
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Application Layer Protocol (T1071) |
| Severity | Low |
**Description**
A VSCode extension connected to an external IP address or host, which is rarely connected to from the organization.
**Attacker's Goals**
Beacon to C2 server and/or exfiltrate data.
**Investigative actions**
Check whether the process was injected or otherwise subverted for malicious use.
UNIX LOLBIN process connected to a rare external host
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Application Layer Protocol (T1071) |
| Severity | Low |
**Description**
A UNIX LOLBIN connected to an external IP address or host, which is rarely connected to from the organization.
**Attacker's Goals**
Beacon to C2 server and/or exfiltrate data.
**Investigative actions**
Check whether the process was injected or otherwise subverted for malicious use.
---
# 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/a-process-connected-to-a-rare-external-host.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.