Reported BINDCLOAK Encrypted Payload File Event
Detects file telemetry for the exact encrypted payload filename shown in the attack-flow image. It covers the file IOC, not the decryption or reflective loading behavior.
- Product
- windows
- Category
- file_event
- Author
- HuntRule
- Published
- 2026-07-30
- Updated
- 2026-07-30
What it detects
Detects a Windows file event involving the reported encrypted payload filename used before BINDCLOAK loading.
Reporting behind it
Prerequisites and telemetry
Limitations
Generic file events do not prove whether the file was created, read, decrypted, or reflectively loaded unless the deployed sensor provides those action fields. The rule may also match defensive handling of the same sample name.
Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.
Unlock this rule to view and copy it
The detection logic is included with a plan. Everything else — context, mappings and implementation details — stays free on this page.
Signing in gives you 3 unlocks to spend on any rule in the library. No card, and they do not expire.
Also included
Unlocked rules convert on this page — to Splunk SPL or Splunk — Raw Index SPL or Microsoft Sentinel KQL or Microsoft Sentinel ASIM ASIM KQL or Microsoft Defender XDR KQL or Elastic Security KQL or Elastic Security Lucene or Elastic Security ES|QL or CrowdStrike Falcon CQL or SentinelOne PowerQuery or Palo Alto Cortex XDR XQL or Carbon Black Cloud Platform Search or Carbon Black EDR Process Search or Google Security Operations UDM Search or IBM QRadar AQL or Sumo Logic Cloud SIEM Rules expression or Rapid7 InsightIDR LEQL or Graylog Search or OpenSearch Lucene or OpenSearch PPL PPL or Grafana Loki LogQL or SQLite SQL or Zircolite SQLite — with the log-source profile the engine picked, the field map it used, and everything it could not express. Converting a rule you have unlocked costs no further credit.