Rust Supply Chain Attack Puts Build-Time Malware in Crates with 245 Million Downloads

The Rust Project has deleted malicious versions of three widely used Rust crates from crates.io after a compromised maintainer account published releases that added a typosquatted dependency whose build script downloaded and executed a remote payload during compilation. The affected releases are arrayref 0.3.10, internment 0.8.7, and append-only-vec 0.1.9, all published from the same owner

Reported facts: A compromised maintainer account on crates.io published malicious versions of three widely used Rust crates (arrayref 0.3.10, internment 0.8.7, and append-only-vec 0.1.9), adding a typosquatted dependency whose build script fetched and executed a remote payload at compile time. The Rust Project later removed these versions after discovery. This incident demonstrates how build-time malware can be introduced into widely reused components without changes to application-level code, impacting potentially large downstream ecosystems. RealGround analysis: For AI/ML systems that rely on Rust-based tooling, libraries, or infrastructure (e.g., data pipelines, model-serving backends, or security agents), similar supply chain compromises could silently alter binaries that handle model artifacts or data, undermining integrity and enabling code execution paths that bypass traditional runtime controls. Organizations should strengthen SBOM practices, enforce strict dependency integrity checks (including maintainers’ account security and typosquat detection), and integrate AI supply chain reviews into broader software build governance to reduce the blast radius of such attacks.