FireWood Backdoor Persistence Files in Hidden kde-root Directory (via file_event)

PremiumReviewedSigma · High · v1
Product
linux
Category
file_event
Author
HuntRule
Published
2026-08-21
Updated
2026-08-28

ATT&CK techniques

Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Priv Esc

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects creation of the FireWood backdoor working files inside a hidden .kde-root directory, where the Linux implant stores its loader and PID artifacts under either a system library path or a user home directory. The masquerade as KDE runtime files combined with the hidden directory reflects the backdoor establishing itself on the host.

Related detections9 linkedT1564.001 — drag to rearrange
Suspicious Executable Written to User Documents Subfolder (via file_event)
Suspicious Sobolan Staging Directory Creation in var tmp (via file_event)
Suspicious Attrib Hiding of Stealer Artifacts (via process_creation)
Suspicious perfctl Hidden IPC Directory Creation in tmp (via file_event)
Suspicious Executable Running From Fake Chrome User Profile Directory
Malicious Cryptominer Staging Files Dropped in tmp Directory
Suspicious Batch Script Unhiding Files via Attrib From Temp
Suspicious Hidden Directory configrc for Bandwidth SDK Abuse
macOS File Persistence from Atomic MacOS Stealer (helper file and LaunchDaemon plist)
FireWood Backdoor Persistence Files in Hidden kde-root Directory (via file_event)
Pivot detection · T1564.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.