> 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/abnormal-network-communication-through-tor-using-an-uncommon-port.md).
# Abnormal network communication through TOR using an uncommon port
### 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), Non-Standard Port (T1571) |
| Severity | Low |
### Description
Suspicious connection from a known TOR IP to an uncommon port.
### Attacker's Goals
Attackers might use TOR IP combined with random ports.to hide C2 inbound communication from inside a host.
### Investigative actions
Investigate the network configuration related to the participating port. Investigate processes that were listening to that port.
### Variations
Abnormal network communication through TOR using an uncommon port and App-id
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Application Layer Protocol (T1071), Non-Standard Port (T1571) |
| Severity | Low |
**Description**
Suspicious connection from a known TOR IP to an uncommon port and App-id.
**Attacker's Goals**
Attackers might use TOR IP combined with random ports.to hide C2 inbound communication from inside a host.
**Investigative actions**
Investigate the network configuration related to the participating port. Investigate processes that were listening to that port.
Abnormal network communication through TOR using a suspicious port
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------------------------- |
| ATT\&CK Tactic | Command and Control (TA0011) |
| ATT\&CK Technique | Application Layer Protocol (T1071), Non-Standard Port (T1571) |
| Severity | Low |
**Description**
Suspicious connection from a known TOR IP to an uncommon potential C2 communication port.
**Attacker's Goals**
Attackers might use TOR IP combined with random ports.to hide C2 inbound communication from inside a host.
**Investigative actions**
Investigate the network configuration related to the participating port. Investigate processes that were listening to that port.
---
# 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/abnormal-network-communication-through-tor-using-an-uncommon-port.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.