Suspicious APT Or YUM Package Manager Hook Configuration Created

PremiumReviewedSigma · Medium · v1
Product
linux
Category
file_event
Author
HuntRule
Published
2026-09-16
Updated
2026-09-16

ATT&CK techniques

Persistence → Priv Esc
  1. Recon

  2. Resource Dev

  3. Initial Access

  4. Execution

  5. Defense Evasion

  6. Cred Access

  7. Discovery

  8. Lateral Movement

  9. Collection

  10. C2

  11. Exfiltration

  12. Impact

What it detects

This rule detects creation of configuration files in the APT or YUM package manager hook directories which adversaries abuse to execute arbitrary commands whenever the package manager runs. Planting a hook under apt.conf.d or the yum plugin configuration grants stealthy privileged persistence tied to routine system maintenance.

Related detections9 linkedT1546 — drag to rearrange
Suspicious Python Path Configuration Hook Persistence (via file_event)
Suspicious Zsh Persistence via zshrc_aliases Appended to Shell Startup (via process_creation)
Malicious UNC4841 Dropper Deployment to Boot Partition via mknod (via process_creation)
Suspicious NetworkManager Dispatcher Script Persistence
AdminSDHolder Permissions Changed for Persistence (via security)
Suspicious Persistence via Shell Script Dropped in profile.d Directory (via file_event)
Suspicious Command Processor AutoRun Persistence via Registry Set
Suspicious Python Site Hook or PTH File Written to Site-Packages via File Event
Suspicious MOTD Or Git Hook Script Creation For Linux Persistence
Suspicious APT Or YUM Package Manager Hook Configuration Created
Pivot detection · T1546 · 9 related

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