1-minute read of a 5 min report

BINDCLOAK Duplicates Windows Tokens to Run Modules as Another User

By

1-minute read

What a defender needs to know

Zscaler has detailed how BINDCLOAK, a modular backdoor used against government entities in the Middle East, collects Windows user tokens, inventories reusable process tokens, and starts malware modules under a selected security identity. Zscaler says the campaign had a key focus on the energy vertical, reflected in diplomatic and energy-themed lures. The report concerns post-compromise behavior, not a Windows vulnerability affecting every endpoint.

The implant can validate supplied credentials with LogonUserW, retain successful user-token handles, enumerate processes and token rights, then duplicate a user or process token with DuplicateTokenEx. It uses ImpersonateLoggedOnUser so built-in or reflectively loaded plugin modules can run in that context. Zscaler dates most observed post-compromise activity to July 7 through July 9 and assesses with high confidence that BINDCLOAK is an OctLurk variant based on code and command-infrastructure overlap.

Hunt on affected hosts for process enumeration, token access, DuplicateTokenEx, changed user or integrity context, module execution, executable private memory, TLS to cert.hypersnet[.]com, and sample MD5 7a14a99d70d42d3f7bf72f843185fc07. Confirm the security context for each supplied credential, duplicated token, module, child process, outbound connection, and follow-on authentication event. Reset exposed credentials from clean systems and rebuild hosts where module or memory state cannot be accounted for, especially when volatile evidence was lost during containment or isolation.

BINDCLOAK makes the borrowed identity part of the scene. Rebuilding the host helps only after the touched security contexts have names.

Primary sources