Nullify

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.

Home
›
Incidents
›
arrayref Rust Crates Supply Chain Attack: What Happened and How to Check Cargo.lock
Supply chain
Direct

arrayref Rust Crates Supply Chain Attack: What Happened and How to Check Cargo.lock

Malicious versions of arrayref, internment and append-only-vec added a build-time dependency that downloaded and ran a payload during cargo build.

Nullify Team
·
Disclosed
August 20, 2026
·
Updated
November 17, 2026

What happened in the arrayref crates attack?

In its analysis, StepSecurity says malicious versions of arrayref, internment and append-only-vec were published on August 20, 2026 from the legitimate droundy crates.io account. Each release added a single build-time dependency on an attacker-owned crate, proc-macro1, while leaving the library code unchanged. The Rust Security Response Team assessed the owner's machine or credentials as compromised.

Any cargo build or cargo update that resolved a poisoned version ran the dependency's build.rs, which downloaded a platform-specific binary with certificate validation disabled and launched it detached so the build still succeeded. crates.io deleted the versions and locked the accounts within roughly 90 to 107 minutes per crate. Because the versions were deleted rather than listed in an advisory, cargo audit won't flag them.

Which crates and versions are affected?

  • arrayref 0.3.10, internment 0.8.7 and append-only-vec 0.1.9, live between 07:11 and 09:25 UTC on August 20, 2026.
  • Attacker crates: proc-macro1 (1.0.107 weaponized), proc-macro-en, aovine, arone, aronenao and tinymember. The legitimate proc-macro2 is not affected.
  • Safe versions to pin: arrayref 0.3.9, internment 0.8.6, append-only-vec 0.1.8.

How to check if you're affected

  1. Search every Cargo.lock for arrayref 0.3.10, internment 0.8.7, append-only-vec 0.1.9, and proc-macro1 or proc-macro-en at any version.
  2. Search ~/.cargo/registry/cache, CI caches and any vendor/ directories for the deleted .crate files.
  3. Review CI jobs that ran between 07:11 and 09:25 UTC on August 20, 2026.
  4. Look for /tmp/rust-setup, rust-setup.ps1 or rust-setup-launch.vbs, and outbound connections to 23.254.165.112 and 23.254.167.107.

What to do now

  1. Pin arrayref =0.3.9, internment =0.8.6 and append-only-vec =0.1.8, then check the resolved lockfile.
  2. Treat machines and runners that built a poisoned version as compromised, and rotate SSH keys, cloud tokens, crates.io tokens, signing keys and CI secrets.
  3. Purge caches, rebuild vendor/ from clean sources and rebuild artifacts produced during the window.
  4. Commit Cargo.lock and build with --locked so new versions can't slip in unreviewed.

Why build-time dependencies are the soft spot

Rust's build.rs and procedural macros run arbitrary code on the machine that compiles them, before any test or scanner looks at the result. The arrayref releases didn't touch a line of library code; they only added a dependency, which is an easy change to miss in review. Watch for new build-time dependencies in lockfile diffs, keep caches and vendored crates under the same scrutiny as source, and give CI runners the least credential access they need.

Where Nullify fits

How Nullify Covers This Class of Attack

Direct
Supply Chain Attack

Nullify finds every repository and container image that pulls an affected package version and runs the upgrade as one campaign, scoped by CVE, package, repo or team, with owners, Slack escalation and SLA tracking. Your developers approve every merge.

Nullify can't tell you whether the payload ran on a given machine or runner. Use the checks above for that, then fix the dependency everywhere it appears.

Frequently Asked Questions

Which arrayref versions were malicious?

arrayref 0.3.10, internment 0.8.7 and append-only-vec 0.1.9, published August 20, 2026 and live for under two hours each. Pin arrayref 0.3.9, internment 0.8.6 and append-only-vec 0.1.8, and check your Cargo.lock.

Will cargo audit find the malicious arrayref crates?

No. StepSecurity notes the versions were deleted from crates.io rather than listed in an advisory, so cargo audit has nothing to match. Search Cargo.lock files, registry caches and vendor directories for the versions and the proc-macro1 crate directly.

What does the arrayref malware do?

The attacker crate's build script runs during cargo build, downloads a platform-specific binary and launches it in the background while the build succeeds. Treat any machine or CI runner that built a poisoned version as compromised and rotate its credentials.

Update Log

  • Nov 17, 2026: page published from the primary sources linked above.

Check your own code for the bug behind this incident

Nullify's AI harness finds, proves and fixes the same class of vulnerability in your code and dependencies, and hands your team a merge-ready pull request.