Suspicious Whisper Backdoor Log File in Windows Temp

PremiumReviewedSigma · High · v1
Product
windows
Category
file_event
Author
HuntRule
Published
2026-09-23
Updated
2026-09-23

ATT&CK techniques

C2
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Defense Evasion

  8. Cred Access

  9. Discovery

  10. Lateral Movement

  11. Collection

  12. Exfiltration

  13. Impact

What it detects

This rule detects creation of a file named WindowsEventLogs.txt in C:\Windows\Temp, the hardcoded log location written by the Whisper backdoor used by the BladedFeline group. The filename masquerades as legitimate event log data while actually storing attacker command output and activity records.

Related detections9 linkedT1071.001 — drag to rearrange
Suspicious Lunar Backdoor State File Creation via File System
Malicious OilRig OAuth Application Sign-In via Azure (via azure)
Malicious FIN7 DiceLoader C2 via Placeholder User-Agent (via proxy)
Malicious D3f@ck Loader C2 via Java User-Agent Ready Beacon (via proxy)
Suspicious AddInProcess32 Outbound Connection after Process Hollowing
Suspicious microsoftedgeupdatecore Outbound Connection from Wrong Path
Suspicious RegAsm or AppLaunch Outbound Connection after Injection
Malicious FakeBat Distribution Domain Lookup (via dns_query)
Suspicious Modification of Windows Hosts File
Suspicious Whisper Backdoor Log File in Windows Temp
Pivot detection · T1071.001 · 9 related

Detection content is published as a reviewed draft. Tune thresholds and exclusions against your own telemetry before enabling this rule for alerting.