1-minute read
What a defender needs to know
A compromised crates.io publishing account released [email protected], [email protected], and [email protected] with a dependency on the malicious proc-macro1 build script. A normal Cargo build automatically ran the downloader without requiring application code to call it. Rust removed the releases after 86 to 107 minutes and locked the account.
RustSec counted 2,285 downloads of [email protected]. That number does not establish 2,285 executions or compromised hosts. Most users retained older lockfile-pinned versions, and Rust has not quantified successful second-stage downloads or data loss.
Search Cargo.lock, dependency inventories, build logs, software bills of materials, and ~/.cargo/registry/cache for the three poisoned releases plus proc-macro1, proc-macro-en, aovine, arone, aronenao, and tinymember. The last unaffected versions are arrayref<=0.3.9, internment<=0.8.6, and append-only-vec<=0.1.8; RustSec lists no patched successors.
For a matching build, hunt for 23[.]254[.]165[.]112 on ports 9089 and 443, the newly reported 23[.]254[.]167[.]107 and 23[.]254[.]167[.]216, /49890878, /tmp/rust-setup, $HOME/.config/AzureKits, $HOME/.config/ServiceKit, MonoService, MonoXpc, the Windows rust-setup scripts, Cargo-linked wscript.exe or PowerShell, HKCU Run, systemd user services, and LaunchAgents. StepSecurity has not independently reproduced the new Linux-host observations. Isolate executed cases, rotate credentials available to the build host, and rebuild on a known-clean system. A clean fleet has no matching dependencies or cached crates, and every positive is resolved with process, file, network, persistence, credential, and rebuild evidence.