Post
The compromised crate depended on a fake proc-macro1 crate from a typosquatted maintainer. proc-macro1 in turn had a malicious build.rs file which downloaded an unknown payload. That payload remains running afterwards, and connects to 23.254.165.112. More is not yet known about it.
Other popular crates that were compromised at the same time were internment and append-only-vec which also had their dependency changed to the malicious proc-macro1 crate.
1 repost2 likes
There is now a post from the crates.io security team about this as well blog.rust-lang.org/2026/08/20/s...
blog.rust-lang.orgSupply chain attack on arrayref | Rust BlogEmpowering everyone to build reliable and efficient software.