arrayref 0.3.10, internment 0.8.7 and append-only-vec 0.1.9 on crates.io added a dependency that downloaded and ran a program on 20 August 2026.
Each release added a dependency named proc-macro1. That crate downloaded and ran a program from a remote server when the project compiled.
What happened
Attackers took over publishing for three popular Rust crates and released one new version of each.
- The new versions added a dependency on
proc-macro1, which imitates the realproc-macro2crate. - Its
build.rsfile runs during compilation, with no import in your source. - The script rebuilds a server address from Base64 fragments and turns off TLS certificate checks.
- It downloads a payload for the operating system and runs it.
- The second stage lists Chromium browser logins, sets up persistence and waits for remote commands.
The releases went up within minutes of each other at about 07:29 UTC on 20 August 2026.
Affected versions
arrayref0.3.10. Last clean version: 0.3.9.internment0.8.7. Last clean version: 0.8.6.append-only-vec0.1.9. Last clean version: 0.1.8.proc-macro11.0.107, the malicious dependency. The attackers deleted it from the registry.- Other attacker crates in the reports:
proc-macro-en,aovine,arone,aronenaoandtinymember. JFrog reports that the last four carried no remote payload.
Indicators of compromise
- Payload host:
23.254.165.112:9089. Command servers:23.254.165.112:443and23.254.167.107:443. - Download paths:
/rust-crate_0.1.0(Linux x86-64),/rust-crate_0.2.0(Windows),/rust-crate_0.3.0(macOS x86-64),/rust-crate_0.4.0(macOS ARM64). - Beacon path:
/49890878. - Files:
/tmp/rust-setup,%TEMP%\rust-setup.ps1,%TEMP%\rust-setup-launch.vbs. - Persistence: HKCU Run key (Windows), systemd user service (Linux), LaunchAgent (macOS).
- SHA-256 of
arrayref-0.3.10.crate:25ad700976873c76af785cb99b33c48db7df8b81f21d1e9e06b3676b9a9373ae. - SHA-256 of
proc-macro1-1.0.107.crate:61198155da51b838772eecf5bfaac6cbc4dcc388dccc56658fc28a8e831b34d4.
How to check
Search every Cargo.lock for the bad versions and the malicious crate names.
grep -rnE "proc-macro1|proc-macro-en|name = \"(arrayref|internment|append-only-vec)\"" --include=Cargo.lock . -A1
On Linux or macOS, look for the payload.
ls -l /tmp/rust-setup
What to do now
- Pin
arrayref0.3.9,internment0.8.6 andappend-only-vec0.1.8. Remove anyproc-macro1entry and regenerateCargo.lock. - If a bad version compiled on a machine, treat the host as compromised.
- Rotate every credential the build environment can read. Reset passwords stored in browsers.
- Delete the payload files and persistence entries above. Block the IP addresses above.
Frequently asked questions
How widely used is arrayref?
JFrog reports about 245 million downloads for arrayref alone.
How did the attackers get publishing access?
The Rust Security Response Team determined that the maintainer's machine or credentials were compromised, as reported by Wiz.
Who is behind the attack?
Wiz reports substantial overlap with North Korean campaigns, such as the same /49890878 beacon path used in an earlier campaign.
Sources
Send this page to the person who looks after AI at your company.