AsyncRAT Injector libPK.dll Written to Public Folder (via file_event)

PremiumReviewedSigma · Medium · v1
Product
windows
Category
file_event
Author
HuntRule
Published
2026-09-01
Updated
2026-09-01

ATT&CK techniques

Priv Esc → Defense Evasion
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Persistence

  6. Defense Evasion

  7. Cred Access

  8. Discovery

  9. Lateral Movement

  10. Collection

  11. C2

  12. Exfiltration

  13. Impact

What it detects

This rule detects the native injector libPK.dll being written into the C users Public folder, a staging behavior of the AsyncRAT chain that later calls its Execute export to inject the payload. Adversaries leverage the shared Public directory to drop the injector where any user context can reach it.

Related detections9 linkedT1055 — drag to rearrange
Suspicious PowerShell Shellcode Loader via Function Pointer Delegate
Suspicious Named Pipe Created by Kazuar Backdoor for Interprocess Command Channel
Suspicious SmallTiger Backdoor DLL Load via Image Load
Suspicious svchost Execution With Anomalous Arguments via DeedRAT (via process_creation)
Suspicious Sang Loader Execution with Install or PassUAC Arguments
Suspicious GodRAT Shellcode Injection via Puppet Argument (via process_creation)
Suspicious Executable Execution From AppData Roaming msgui via Process Creation
Suspicious RuntimeBroker Network Connection via Loki Mythic Agent
Suspicious Network Connection from mspaint or msiexec (via network_connection)
AsyncRAT Injector libPK.dll Written to Public Folder (via file_event)
Pivot detection · T1055 · 9 related

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