arrayref has 1 version on crates.io flagged in 1 incident we track. Only the exact versions listed below were named by the source advisories. arrayref is a legitimate package. Only the versions listed were malicious; other versions were not affected, but a lockfile that resolved to a listed version installed the payload.
If one is in your tree, treat the machine as compromised, not just out of date.
Version data comes from the public advisories cited on each incident page.
Check what you actually have installed with cargo tree -i arrayref.
Compromised maintainer accounts published arrayref@0.3.10 (244M downloads), internment@0.8.7, and append-only-vec@0.1.9 to crates.io. Each release added a single dependency line on typosquat crate proc-macro1, whose build.rs downloads and executes a platform-specific payload from 23.254.165.112:9089 during cargo build. Wiz attributes overlap to DPRK campaigns.
Treat the machine as compromisedUpgrading is not enough. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.
If arrayref is in your tree, these are worth checking too. They were published by the same campaign.
Version data comes from the public advisories cited on each incident page. We list only versions those advisories name and do not infer additional ones. Think this is wrong or incomplete? Tell us.
It is usually pulled in as a transitive dependency. We do not parse crates.io manifests yet, but the scanner checks npm and PyPI lockfiles and the incident write-ups list every affected package.