Updated
Updated · InfoWorld · Aug 21
3 Malicious Rust Packages Hit crates.io, Exposing arrayref’s 245 Million Downloads to Build-Time Backdoor
Updated
Updated · InfoWorld · Aug 21

3 Malicious Rust Packages Hit crates.io, Exposing arrayref’s 245 Million Downloads to Build-Time Backdoor

3 articles · Updated · InfoWorld · Aug 21

Summary

  • Three tainted crates — arrayref@0.3.10, internment@0.8.7 and append-only-vec@0.1.9 — were uploaded to crates.io on Aug. 20, triggering malware automatically when affected projects were compiled.
  • A typosquatted dependency, proc-macro1, used Rust build scripts to fetch and run a second-stage payload, so developers did not need to call any package code for the infection to fire.
  • Wiz said the payload harvested system and browser data, could persist on Windows, macOS and Linux, and used fallback domain generation if its primary command-and-control infrastructure went down.
  • StepSecurity said arrayref alone has 245 million lifetime downloads, with the malicious versions exposed for roughly 86 to 107 minutes before deletion.
  • Wiz linked the infrastructure to recent DPRK-attributed supply-chain campaigns including Mastra and Axios, and urged teams to check Cargo.lock files and treat any machine that built the packages as compromised.

Insights

Could a brief 90-minute compromise of a popular Rust crate have already silently infected major blockchain and crypto ecosystems?
Why are state-linked hackers increasingly weaponizing the automated build processes of developer tools instead of targeting end-users directly?
If simply compiling code can trigger malware, is the implicit trust developers place in automated build scripts fundamentally broken?