Detect Right-to-Left Override in CrowdStrike LogScale
Adversaries may abuse the right-to-left override (RTLO or RLO) character (U+202E) to disguise a string and/or file name to make it appear benign. RTLO is a non-printing Unicode character that causes the text that follows it to be displayed in reverse. For example, a Windows screensaver executable named 'March 25 \u202Excod.scr' will display as 'March 25 rcs.docx'. Adversaries may abuse the RTLO character as a means of tricking a user into executing what they think is a benign file type. Use of the RTLO character has been seen in many targeted intrusion attempts and criminal activity.
MITRE ATT&CK
- Tactic
- Defense Evasion
- Technique
- T1036 Masquerading
- Sub-technique
- T1036.002 Right-to-Left Override
- Canonical reference
- https://attack.mitre.org/techniques/T1036/002/
LogScale Detection Query
#event_simpleName = /ProcessRollup2|SyntheticProcessRollup2|FileWritten|PeFileWritten/
| ImageFileName = /\xe2\x80\xae/ OR CommandLine = /\xe2\x80\xae/ OR TargetFileName = /\xe2\x80\xae/
| table([timestamp, ComputerName, UserName, #event_simpleName, ImageFileName, CommandLine, TargetFileName, SHA256HashData, MD5HashData])
| sort(timestamp, order=desc)Detects RTLO character (U+202E, UTF-8 bytes: \xe2\x80\xae) in Falcon process and file write telemetry. Queries ProcessRollup2, SyntheticProcessRollup2, FileWritten, and PeFileWritten events for the Unicode directional override marker in image filenames, command lines, and target filenames — identifying both execution-time RTLO abuse and RTLO-named file writes to disk.
Data Sources
Required Tables
False Positives & Tuning
- Authorized red team operators deploying RTLO-named lure files during sanctioned phishing simulations or physical intrusion exercises
- Multilingual enterprise endpoints in RTL-language markets where application installers legitimately produce bidirectional-named support files
- Endpoint detection validation frameworks that write RTLO test artifacts to confirm Falcon sensor coverage of this technique
Other platforms for T1036.002
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Create File with RTLO Character to Disguise Extension
Expected signal: Sysmon Event ID 11: FileCreate with TargetFilename containing the RTLO character (U+202E). The filename in logs will show the raw Unicode character.
- Test 2Create Executable Masquerading as PDF via RTLO
Expected signal: Sysmon Event ID 11: FileCreate with .scr extension disguised via RTLO. The file appears as 'invoice_2026rcs.pdf' in Explorer but is actually a screensaver executable.
- Test 3RTLO in Registry Value (Windows)
Expected signal: Sysmon Event ID 13: RegistryEvent (Value Set) with the RTLO character in the registry value name. Regedit.exe will display the reversed text but reg.exe will show the raw characters.
References (6)
- https://attack.mitre.org/techniques/T1036/002/
- https://resources.infosecinstitute.com/spoof-using-right-to-left-override-rtlo-technique-2/
- https://blog.trendmicro.com/trendlabs-security-intelligence/plead-targeted-attacks-against-taiwanese-government-agencies-2/
- https://securelist.com/zero-day-vulnerability-in-telegram/83800/
- https://github.com/redcanaryco/atomic-red-team/blob/master/atomics/T1036.002/T1036.002.md
- https://github.com/SigmaHQ/sigma/tree/master/rules/windows/file_event
Unlock Pro Content
Get the full detection package for T1036.002 including response playbook, investigation guide, and atomic red team tests.