Skip to content

Back to the catalog

Why EDR and proxy won’t save you from supply chain malware
aikido.devarticle

Why EDR and proxy won’t save you from supply chain malware

Aikido argues that EDR and corporate/remote proxies cannot catch supply chain malware because the malicious code executes with full trust inside legitimate package managers at install time. It walks through two real incidents: the March 2026 hijack of the axios maintainer's npm account (a new dependency's postinstall script dropped a cross-platform RAT and self-deleted, indistinguishable from a normal npm install), and a backdoor added to three versions of Microsoft's Python durabletask package that harvested credentials across AWS, Azure, GCP, Kubernetes, and HashiCorp Vault, propagated via SSM and kubectl exec, and triggered rm -rf / on machines with Israeli/Iranian locale settings. It concludes that this class of attack needs host-based, always-on, install-time protection rather than network-perimeter or behavioral-anomaly tooling — pitching Aikido's Device Protection product.

TL;DR Postinstall-script supply chain attacks (axios maintainer hijack, durabletask backdoor) look identical to legitimate installer behavior, so EDR and proxies structurally can't catch them.

Techniques named here

  • Malicious postinstall script
  • npm/package registry account hijack
  • Dependency injection / malicious dependency addition
  • Code injection into package source
  • Cloud credential harvesting
  • Lateral movement using victim credentials
  • Locale-conditional destructive payload
  • Proxy bypass

Threat actors named here

  • Unnamed attacker behind axios npm account hijack
  • Unnamed attacker behind durabletask backdoor