> 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/potential-ntlm-relay-attack.md).
# Potential NTLM Relay Attack
### Synopsis
| Field | Value |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | 10 Minutes |
| Deduplication Period | 1 Day |
| Required Data | XDR Agent |
| Detection Modules | Identity Analytics |
| ATT\&CK Tactic | Credential Access (TA0006), Lateral Movement (TA0008) |
| ATT\&CK Technique | Adversary-in-the-Middle: Name Resolution Poisoning and SMB Relay (T1557.001), Use Alternate Authentication Material: Pass the Hash (T1550.002) |
| Severity | Informational |
### Description
Multiple NTLM authentications were made to the same workstation and user from different IPs. This might indicate a potential NTLM Relay attack.
### Attacker's Goals
The attacker is attempting a man-in-the-middle NTLM relay attack to intercept authentication attempts and move laterally within an environment.
### Investigative actions
* Ensure that the alerted host is not a NAT device or proxy that replicates or forwards network traffic as part of its expected operational behavior.
* Check if the workstation supports weak, outdated versions of NTLM.
* Check for network activity to and from the suspicious IP address and workstation, to verify if they were compromised.
* Check for process activity to and from the suspicious IP address to verify if it was compromised.
* Check for changes in the network configurations, including indicators of poisoning attacks.
* Monitor closely the actions of the potentially compromised user account for any anomalous behavior.
### Variations
NTLM Relay Attack using a sensitive user and a vulnerable package
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Lateral Movement (TA0008) |
| ATT\&CK Technique | Adversary-in-the-Middle: Name Resolution Poisoning and SMB Relay (T1557.001), Use Alternate Authentication Material: Pass the Hash (T1550.002) |
| Severity | Medium |
**Description**
Multiple NTLM authentications were made to the same workstation and sensitive user from different IPs using a vulnerable NTLM package. This might indicate a potential NTLM Relay attack.
**Attacker's Goals**
The attacker is attempting a man-in-the-middle NTLM relay attack to intercept authentication attempts and move laterally within an environment.
**Investigative actions**
* Ensure that the alerted host is not a NAT device or proxy that replicates or forwards network traffic as part of its expected operational behavior.
* Check if the workstation supports weak, outdated versions of NTLM.
* Check for network activity to and from the suspicious IP address and workstation, to verify if they were compromised.
* Check for process activity to and from the suspicious IP address to verify if it was compromised.
* Check for changes in the network configurations, including indicators of poisoning attacks.
* Monitor closely the actions of the potentially compromised user account for any anomalous behavior.
Potential NTLM Relay Attack using a vulnerable package
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Lateral Movement (TA0008) |
| ATT\&CK Technique | Adversary-in-the-Middle: Name Resolution Poisoning and SMB Relay (T1557.001), Use Alternate Authentication Material: Pass the Hash (T1550.002) |
| Severity | Low |
**Description**
Multiple NTLM authentications were made to the same workstation and user from different IPs using a vulnerable NTLM package. This might indicate a potential NTLM Relay attack.
**Attacker's Goals**
The attacker is attempting a man-in-the-middle NTLM relay attack to intercept authentication attempts and move laterally within an environment.
**Investigative actions**
* Ensure that the alerted host is not a NAT device or proxy that replicates or forwards network traffic as part of its expected operational behavior.
* Check if the workstation supports weak, outdated versions of NTLM.
* Check for network activity to and from the suspicious IP address and workstation, to verify if they were compromised.
* Check for process activity to and from the suspicious IP address to verify if it was compromised.
* Check for changes in the network configurations, including indicators of poisoning attacks.
* Monitor closely the actions of the potentially compromised user account for any anomalous behavior.
Potential NTLM Relay Attack using a sensitive user
**Synopsis**
| Field | Value |
| ----------------- | ---------------------------------------------------------------------------------------------------------------------------------------------- |
| ATT\&CK Tactic | Credential Access (TA0006), Lateral Movement (TA0008) |
| ATT\&CK Technique | Adversary-in-the-Middle: Name Resolution Poisoning and SMB Relay (T1557.001), Use Alternate Authentication Material: Pass the Hash (T1550.002) |
| Severity | Low |
**Description**
Multiple NTLM authentications were made to the same workstation and sensitive user from different IPs. This might indicate a potential NTLM Relay attack.
**Attacker's Goals**
The attacker is attempting a man-in-the-middle NTLM relay attack to intercept authentication attempts and move laterally within an environment.
**Investigative actions**
* Ensure that the alerted host is not a NAT device or proxy that replicates or forwards network traffic as part of its expected operational behavior.
* Check if the workstation supports weak, outdated versions of NTLM.
* Check for network activity to and from the suspicious IP address and workstation, to verify if they were compromised.
* Check for process activity to and from the suspicious IP address to verify if it was compromised.
* Check for changes in the network configurations, including indicators of poisoning attacks.
* Monitor closely the actions of the potentially compromised user account for any anomalous behavior.
---
# 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/potential-ntlm-relay-attack.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.