> 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-unicode-character-detected-in-email.md).
# Suspicious Unicode character detected in email
### Synopsis
| Field | Value |
| -------------------- | ------------------------------------------- |
| Activation Period | 14 Days |
| Training Period | 30 Days |
| Test Period | N/A (single event) |
| Deduplication Period | 1 Day |
| Required Data | Microsoft 365 Emails |
| Detection Modules | Email |
| Detector Tags | Evasion, Phishing |
| ATT\&CK Tactic | Defense Evasion (TA0005) |
| ATT\&CK Technique | Masquerading (T1036), Impersonation (T1656) |
| Severity | Informational |
### Description
Unicode characters can be used for obfuscation, allowing malicious actors to disguise harmful intent, URLs or attachments By embedding non-printing Unicode characters, attackers can bypass security filters and evade detection mechanisms Such characters may also be used for phishing attempts that appear legitimate to both users and security systems.
### Attacker's Goals
Embedding suspicious Unicode characters in the email to appear legitimate, evade security filters and bypass detection mechanisms.
### Investigative actions
* Check the email address for any unusual spellings, missing letters, or unknown domains.
* If the message contains attachments or links, scrutinize them for any suspicious indications.
* Monitor further actions taken, such as file downloads or access to potentially malicious links.
### Variations
Phishing terms obfuscation using Unicode characters detected in email
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic | Defense Evasion (TA0005) |
| ATT\&CK Technique | Masquerading (T1036), Impersonation (T1656) |
| Severity | Low |
**Description**
Unicode characters can be used for obfuscation, allowing malicious actors to disguise harmful intent, URLs or attachments By embedding non-printing Unicode characters, attackers can bypass security filters and evade detection mechanisms Such characters may also be used for phishing attempts that appear legitimate to both users and security systems.
**Attacker's Goals**
Embedding suspicious Unicode characters in the email to appear legitimate, evade security filters and bypass detection mechanisms.
**Investigative actions**
* Check the email address for any unusual spellings, missing letters, or unknown domains.
* If the message contains attachments or links, scrutinize them for any suspicious indications.
* Monitor further actions taken, such as file downloads or access to potentially malicious links.
Words obfuscation using Unicode characters detected in email
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic | Defense Evasion (TA0005) |
| ATT\&CK Technique | Masquerading (T1036), Impersonation (T1656) |
| Severity | Informational |
**Description**
Unicode characters can be used for obfuscation, allowing malicious actors to disguise harmful intent, URLs or attachments By embedding non-printing Unicode characters, attackers can bypass security filters and evade detection mechanisms Such characters may also be used for phishing attempts that appear legitimate to both users and security systems.
**Attacker's Goals**
Embedding suspicious Unicode characters in the email to appear legitimate, evade security filters and bypass detection mechanisms.
**Investigative actions**
* Check the email address for any unusual spellings, missing letters, or unknown domains.
* If the message contains attachments or links, scrutinize them for any suspicious indications.
* Monitor further actions taken, such as file downloads or access to potentially malicious links.
Multiple suspicious Unicode characters detected in email
**Synopsis**
| Field | Value |
| ----------------- | ------------------------------------------- |
| ATT\&CK Tactic | Defense Evasion (TA0005) |
| ATT\&CK Technique | Masquerading (T1036), Impersonation (T1656) |
| Severity | Informational |
**Description**
Unicode characters can be used for obfuscation, allowing malicious actors to disguise harmful intent, URLs or attachments By embedding non-printing Unicode characters, attackers can bypass security filters and evade detection mechanisms Such characters may also be used for phishing attempts that appear legitimate to both users and security systems.
**Attacker's Goals**
Embedding suspicious Unicode characters in the email to appear legitimate, evade security filters and bypass detection mechanisms.
**Investigative actions**
* Check the email address for any unusual spellings, missing letters, or unknown domains.
* If the message contains attachments or links, scrutinize them for any suspicious indications.
* Monitor further actions taken, such as file downloads or access to potentially malicious links.
---
# 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-unicode-character-detected-in-email.md?ask=&goal=
```
`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.