Threat reportMalwareTL-2026-1858
BINDCLOAK: Previously Undocumented 64-bit Modular Windows Backdoor Stealing User/Process Tokens for Privilege Escalation
BINDCLOAK is a previously undocumented 64-bit modular Windows backdoor (C++) that steals user and process tokens to escalate privileges via ImpersonateLoggedOnUser, DuplicateTokenEx, and LogonUserW. It is deployed as the stage-3 payload in an ISO-based multi-stage chain (TELESHIM > MIXEDKEY > BINDCLOAK) targeting Middle Eastern government entities with a focus on the energy sector.
Key facts
| Identifiers | TL-2026-1858 |
|---|---|
| Also known as | Operation BINDCLOAK, Middle East Energy Campaign |
| Severity | HIGH |
| Affected products | Microsoft Windows |
| Malware | PlugX |
| MITRE ATT&CK techniques | T1003 OS Credential Dumping, T1027 Obfuscated Files or Information, T1049 System Network Connections Discovery, T1053 Scheduled Task/Job, T1056 Input Capture, T1057 Process Discovery, T1082 System Information Discovery, T1095 Non-Application Layer Protocol, T1113 Screen Capture, T1119 Automated Collection, T1132 Data Encoding, T1480 Execution Guardrails and 7 more in the attack flow |
| Motivation | ESPIONAGE |
| Target sectors | government administration, energy, health, education, police - law enforcement |
| Target regions | Middle East, 143 - Central Asia |
| Detection rules | 9 (1 shown free) |
| Sources | 8 cited sources |
Detection coverage
As of 2026-08-04, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-1858 across Splunk SPL, Microsoft KQL and Sigma, covering 20 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: BINDCLOAK — Token Theft via LogonUserW/DuplicateTokenEx from Non-System Process
Detects the BINDCLOAK token-based privilege escalation technique: non-system processes calling LogonUserW with supplied credentials, DuplicateTokenEx with TOKEN_ASSIGN_PRIMARY flag, and ImpersonateLoggedOnUser APIs. BINDCLOAK uses these Windows APIs — particularly the COLLECT_USER_TOKEN and START_MODULE_WITH_USER_TOKEN commands — to escalate privileges by stealing user and process tokens.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1134, T1003.003, T1552.001
- Data sources: sysmon, windows_security, microsoft_defender_for_endpoint
- Severity: critical
- Confidence: high
Splunk SPL
index=sysmon sourcetype="XmlWinEventLog:Microsoft-Windows-Sysmon/Operational" EventCode=10 (TargetImage="*\\lsass.exe" OR CallTrace="*\\KERNELBASE.DLL*LogonUserW*" OR CallTrace="*\\KERNELBASE.DLL*DuplicateTokenEx*" OR CallTrace="*\\KERNELBASE.DLL*ImpersonateLoggedOnUser*")
| search (GrantedAccess="0x1F3FFF" OR GrantedAccess="0x1010" OR GrantedAccess="0x2" OR GrantedAccess="0x6")
| stats values(TargetImage) as targets, values(CallTrace) as traces, values(User) as users, dc(SourceImage) as source_count by ComputerName, SourceImage
| where NOT SourceImage IN ("*\\lsass.exe", "*\\winlogon.exe", "*\\services.exe", "*\\svchost.exe", "*\\LogonUI.exe", "*\\system32\\lsass.exe")
| eval alert_name="BINDCLOAK Token Theft — " . SourceImage
| eval mitre_technique="T1134"Microsoft KQL
let token_apis = dynamic(["LogonUserW", "DuplicateTokenEx", "ImpersonateLoggedOnUser"]);
DeviceEvents
| where Timestamp > ago(30d)
| where ActionType == "ApiCall"
| where AdditionalFields has_any ("LogonUserW", "DuplicateTokenEx", "ImpersonateLoggedOnUser")
| extend InitiatingProcessFileName = tostring(parse_json(AdditionalFields).InitiatingProcessFileName)
| extend APICalled = tostring(parse_json(AdditionalFields).ApiName)
| where InitiatingProcessFileName !in~ ("lsass.exe", "winlogon.exe", "services.exe", "svchost.exe", "LogonUI.exe")
| project Timestamp, DeviceName, InitiatingProcessFileName, APICalled, AdditionalFields
| summarize APICalls = make_set(APICalled) by DeviceName, InitiatingProcessFileName, bin(Timestamp, 1h)
| where array_size(APICalls) >= 2
| extend AlertName = strcat("BINDCLOAK Token Theft — ", InitiatingProcessFileName)
| extend MITRETechnique = "T1134"Sigma
title: BINDCLOAK Suspicious Token Manipulation by Non-System Process
id: b4d0e5f6-7a8b-4c9d-0e1f-2a3b4c5d6e7f
status: experimental
description: Detects non-system Windows processes calling LogonUserW, DuplicateTokenEx, or ImpersonateLoggedOnUser APIs for token theft and privilege escalation, characteristic of the BINDCLOAK backdoor's Commands module (0x1020) which implements COLLECT_USER_TOKEN and START_MODULE_WITH_USER_TOKEN operations for token-based privilege escalation.
references:
- https://www.zscaler.com/blogs/security-research/targeted-attack-government-entities-middle-east-part-2
- https://attack.mitre.org/techniques/T1134/
author: Threadlinqs Team
date: 2026-08-04
tags:
- attack.credential_access
- attack.privilege_escalation
- attack.t1134
- attack.t1134.001
- attack.t1003
- attack.tool.bindcloak
logsource:
category: process_access
product: windows
definition: Requires Sysmon Event ID 10 or similar process-access telemetry
detection:
selection:
EventID: 10
GrantedAccess:
- '0x1F3FFF'
- '0x1010'
- '0x6'
TargetImage|endswith: '\lsass.exe'
filter_legitimate:
SourceImage|startswith:
- 'C:\Windows\System32\'
- 'C:\Windows\SysWOW64\'
condition: selection and not filter_legitimate
falsepositives:
- Legitimate Windows processes performing token operations for background tasks
- Security software using token APIs for legitimate monitoring
level: critical
Known false positives:
- Legitimate credential management or password rotation tools calling LogonUserW
- Security monitoring software using OpenProcessToken on LSASS
Tuning notes: Tune by creating an exception list for known security vendors' process names. Correlate with the presence of other BINDCLOAK artifacts (scheduled tasks, specific DLLs). Consider alerting on ANY DuplicateTokenEx call from C:\programdata\ paths.
- BINDCLOAK — Suspicious Scheduled Task Creation for TELESHIM Persistence · unlock with TL Creds
- BINDCLOAK — Reflective Loading via RtlQueueWorkItem → LoadLibraryW from RWX Memory · unlock with TL Creds
- BINDCLOAK — TELESHIM Telegram Bot API C2 from Non-Browser Process · unlock with TL Creds
- BINDCLOAK — ISO Image Mount Triggering Malicious Process Chain · unlock with TL Creds
- BINDCLOAK — Environmental Keying Payload File in DSS Directory · unlock with TL Creds
- BINDCLOAK — Reconnaissance Commands by Unusual Process (TELESHIM Discovery Phase) · unlock with TL Creds
- BINDCLOAK — DLL Side-Loading via ASUSTek RegSchdTask.exe from Non-Standard Path · unlock with TL Creds
- BINDCLOAK — C2 TLS Connections to Known OctLurk/BINDCLOAK Infrastructure on ASN 14956 · unlock with TL Creds
Indicators of compromise
As of 2026-08-04, Threadlinqs Intelligence tracks 20 indicators of compromise for TL-2026-1858.
Sample indicators (3 of 20)
- IP address:
107.175.172[.]40 - Domain:
cert[.]hypersnet[.]com - File hash:
7a14a99d70d42d3f7bf72f843185fc07
Defanged, TLP:CLEAR. Full set of 20 indicators: unlock with TL Creds.
Technical analysis
Zscaler ThreatLabz assesses with high confidence that BINDCLOAK is a variant of the OctLurk backdoor operated by an East Asia-linked espionage actor that previously targeted Central Asia.
BINDCLOAK is a previously undocumented 64-bit modular Windows backdoor written in C++ that delivers privilege escalation through token theft rather than traditional exploit-based elevation. The malware is deployed as the final stage in a three-stage attack chain initiated through diplomatic-themed ISO file lures targeting Middle Eastern government entities, particularly in the energy sector.
The infection chain begins when a target opens an ISO file containing government-themed filenames such as 'Cooperation protocol for the exploration of petroleum and gas (English).img' or 'Agreement on the Establishment of Common Border Offices (English).img'. The ISO contains a legitimate ASUSTek RegSchdTask.exe binary alongside a malicious AsTaskSched.dll that is DLL side-loaded to execute TELESHIM, a 32-bit C++ backdoor that abuses the Telegram Bot API for command-and-control. TELESHIM performs extensive reconnaissance (net user, tasklist, ipconfig, netstat), uses heavy obfuscation (CFF/MBA/opaque predicates), and implements anti-analysis measures including CPUID-based hypervisor detection and a 1 GB I/O stress test designed to stall sandbox execution. It persists via a scheduled task named 'shimgen' running every 6 minutes.
Post-compromise, the threat actor deploys a legitimate GoPro binary alongside pthreadVC2.dll, which is actually MIXEDKEY — a 64-bit reflective loader. MIXEDKEY uses two-layer XOR decryption with environmental keying derived from the victim's C:\ volume serial number, ensuring the payload only decrypts on the intended target. MIXEDKEY reflectively loads the decrypted BINDCLOAK DLL into memory and invokes its curl_easy_escape export.
BINDCLOAK is a modular implant with two built-in modules (C2 module 0x1010 and Command module 0x1020) and a plugin architecture supporting reflective loading of additional DLLs delivered from the C2 server. Its core innovation is token-based privilege escalation: the Commands module (0x1020) implements COLLECT_USER_TOKEN (calls LogonUserW with supplied credentials to collect user token handles), GET_STATUS (enumerates processes via WTSEnumerateProcessesW with OpenProcessToken to inspect TOKEN_QUERY/TOKEN_DUPLICATE/TOKEN_ASSIGN_PRIMARY flags), START_MODULE_WITH_USER_TOKEN (calls DuplicateTokenEx with TOKEN_ASSIGN_PRIMARY to launch modules under a higher-privileged token), and START_MODULE_WITH_PROCESS_TOKEN (similar but using process tokens from running processes). This token abuse blends into normal Windows behavior, evading detection by appearing as legitimate impersonation.
BINDCLOAK communicates via TLS over TCP with a custom message-routing protocol. All messages use a 28-byte header followed by two variable-sized blob payloads. Beacon messages collect OS version (OSVERSIONINFOEX), computer name (GetComputerNameW), username (GetUserNameW), hostname (gethostname), local IP (GetAddrInfoW), and local time (GetLocalTime). Messages are triple-encrypted: zlib compression, followed by a 105-byte rolling XOR key constructed as a stack string, followed by an 83-byte random XOR key with random padding (14—41 bytes). The C2 infrastructure reuses an SSL certificate (serial 59fe1ef7707fe497d89f34505222862f, CN 107.175.172.40) across both BINDCLOAK (cert.hypersnet.com) and OctLurk (about.blsouqs.com) domains.
The plugin loader allocates RWX memory via VirtualAlloc, uses RtlQueueWorkItem to call LoadLibraryW for import resolution (evading EDR detection of LoadLibraryW calls from unbacked executable memory), and modifies PE headers to hinder static detection. Plugin module DLLs must export ins_ctl_db and oct_lk_col functions.
Zscaler ThreatLabz assesses with high confidence that BINDCLOAK is a variant of the OctLurk backdoor based on identical beacon message structures, the same encryption algorithm (zlib + double XOR), high XOR key similarity, shared infrastructure (SSL certificate reuse, Tucows registrar, Njalla name servers, ASN 14956), and operational overlaps (the actor pinged both BINDCLOAK and OctLurk C2 servers during post-compromise activity). Kaspersky GReAT separately documented OctLurk and a related backdoor (SilkLurk) targeting Central Asian governments and Syrian entities starting January 2025, attributed with medium confidence to a Chinese-speaking threat actor. The July 2026 campaign marks a notable geographic and sectoral expansion from Central Asian government targets to Middle Eastern energy sector entities.
MITRE ATT&CK techniques by tactic:
Credential Access
T1003 OS Credential Dumping; T1552 Unsecured Credentials
Defense Evasion
T1027 Obfuscated Files or Information; T1480 Execution Guardrails; T1497 Virtualization/Sandbox Evasion; T1620 Reflective Code Loading
Discovery
T1049 System Network Connections Discovery; T1057 Process Discovery; T1082 System Information Discovery
Persistence
Collection
T1056 Input Capture; T1113 Screen Capture; T1119 Automated Collection
Command and Control
T1095 Non-Application Layer Protocol; T1132 Data Encoding; T1573 Encrypted Channel
collection
Initial Access
stealth
Remediation
Immediate actions
- Block C2 domains cert.hypersnet.com, about.blsouqs.com, ssl.blsouqs.com, contacts.ftabnews.com at perimeter
- Block IP 107.175.172.40 at firewall
- Deploy YARA signatures for BINDCLOAK (MD5 7a14a99d70d42d3f7bf72f843185fc07), TELESHIM, and MIXEDKEY hashes
- Scan for scheduled tasks named 'shimgen' and 'Feedback' on Windows endpoints
Workarounds
- Restrict execution of ISO files from email/downloads to administrative approval
- Enable Windows Defender Attack Surface Reduction rules for DLL side-loading
- Audit scheduled tasks for creation of unrecognized tasks with frequent intervals
Longer-term hardening
- Monitor for abnormal token usage (ImpersonateLoggedOnUser, DuplicateTokenEx calls from non-system processes)
- Monitor for RtlQueueWorkItem calling LoadLibraryW from unbacked memory regions
- Hunt for unscheduled TLS connections to Tucows/Njalla-registered domains on ASN 14956
- Monitor Telegram Bot API traffic from non-browser processes
- Implement ISO file execution telemetry and DLL side-loading detection
Affected and fixed versions
- Microsoft — Windows
Vulnerable versions: All versions supporting ImpersonateLoggedOnUser
Timeline
- Threat actor registers C2 infrastructure including locked-ioc-13 and locked-ioc-15 via Tucows registrar with Njalla name servers on ASN 14956
- OctLurk/SilkLurk operation begins targeting Central Asian governments (Afghanistan, Kyrgyzstan, Tajikistan, Uzbekistan, Kazakhstan) and Syria, as documented by Kaspersky GReAT
- Diplomatic-themed ISO lures deployed targeting Middle Eastern energy sector entities, including petroleum and border-agreement themed filenames
- Current TELESHIM variant compiled (July 2026); two older variants previously compiled in 2025
- First observed post-compromise command execution in the Middle East campaign via TELESHIM backdoor, with reconnaissance and deployment of MIXEDKEY/BINDCLOAK
- Last day of observed post-compromise activity; actor verified connectivity to BINDCLOAK C2 (locked-ioc-12) and OctLurk C2 servers via ping commands
- Zscaler ThreatLabz publishes two-part analysis of the campaign; Kaspersky GReAT publishes OctLurk/SilkLurk report; Cybersecurity News publishes BINDCLOAK coverage
Sources cited
- Zscaler ThreatLabz — Targeted Attack on Government Entities in the Middle East (Part 1) zscaler.com · Research · 2026-08-04
- Zscaler ThreatLabz — Targeted Attack on Government Entities in the Middle East (Part 2) zscaler.com · Research · 2026-08-04
- OctLurk and SilkLurk: New Backdoors in Central Asia — Kaspersky Securelist Kaspersky Securelist · Research · 2026-08-04
- Zscaler ThreatLabz — Win64.Backdoor.BINDCLOAK threatlibrary.zscaler.com · Research · 2026-08-04
- Zscaler ThreatLabz — Win32.Backdoor.TELESHIM threatlibrary.zscaler.com · Research · 2026-08-04
- Zscaler ThreatLabz — Win64.Loader.MIXEDKEY threatlibrary.zscaler.com · Research · 2026-08-04
- Kazakhstan STS — TrustFall/MystRodX Infrastructure Overlap profitday.kz · Research · 2025-01-01
- BINDCLOAK Steals Windows Tokens — Cybersecurity News cybersecuritynews.com · News · 2026-08-04
Previous and next in malware
Drafted by the Threadlinqs research pipeline from 8 sources; published ; last updated —.