Did North Korean hackers launch the supply chain attack on arrayref?

- On August 20, attackers published malicious versions of three widely used Rust crates, led by arrayref.
- Wiz says the infrastructure overlaps with North Korean campaigns previously attributed by Microsoft and Mandiant.
- The machines of developers and CI operators who built Rust code during the exposure window may already be compromised.
Wiz says the supply chain attack that poisoned arrayref, a Rust package present in roughly three-quarters of environments running Rust, has drawn comparisons with recent North Korean operations.
The harmful update hid a backdoor that steals login information inside a code designed to run automatically when users compile projects. So, anyone who compiled a project on Thursday may now have exposed their computer and secrets.
Why is North Korea being blamed for the hack on arrayref?
Wiz researchers Rami McCarthy and Benjamin Read have published a report in which they noted that the arrayref payload beacons to a command-and-control path, /49890878, that also appears in the Mastra campaign.
Microsoft links the Mastra campaign to a North Korean hacking group it calls Sapphire Sleet.
The internet address (IP) used in the arrayref attack shares the same security certificate as another address used in Mastra. Also, a victim who reported suspicious activity flagged an IP that Google Cloud saw in the axios npm attack.
Mandiant says that the attack was done by a North Korean group called UNC1069. Both attacks used the same hosting company, Hostwinds.
The attack was hard to notice because it changed very little. Ilyas Makari, a security researcher from Aikido, found that the actual code inside the three Rust packages, arrayref, internment, and append-only-vec, was not altered. The only change was one new dependency added to each package’s list called proc-macro1.
This name is a misspelling of the popular proc-macro2 crate, which has over 154 million downloads. The fake crate even includes the real proc-macro2 code, so the software still builds and passes all tests.
The harmful part was hidden in the build script.
Cargo runs build scripts automatically at compile time, so, as the Rust Security Response Team spelled out in its advisory, merely compiling a project that pulled the bad version was enough to trigger the attack.
Once running, the second stage of the attack stole saved passwords from Chrome, Brave, and Edge browsers and installed itself so it would survive computer restarts on Windows, Mac, and Linux.
The largest Rust compromise by download count
Aikido stated that this attack is the biggest Rust crate compromise it has seen, measured by downloads, with arrayref, which is used in tools for Solana and Ethereum, sitting at about 244 million total downloads. The exposure was reportedly live for 86 minutes before deletion.
The team said Nextron Systems made the initial report. And once the attack was discovered, the team unyanked the clean versions and locked the maintainer’s account.
The Rust team said it does not believe the author acted maliciously, assessing instead that their machine or credentials were compromised.
Notably, Amazon disclosed on July 29 that it had linked a string of npm library compromises to a single DPRK-linked actor. TRM Labs also reported that North Korean groups accounted for about 76% of all crypto hack value in 2026 through April (roughly $577 million).
Black Hat researcher Vangelis Stykas has said he tracked North Korean hackers into 1,640 companies across 57 countries. He found that they often bait developers with fake job offers that install malware, similar to the poisoned build dependency in this case.
If you're reading this, you’re already ahead. Stay there with our newsletter.
FAQs
Which Rust crates were compromised?
Three legitimate crates from the same maintainer were poisoned: arrayref 0.3.10, internment 0.8.7 and append-only-vec 0.1.9, all of which added a malicious typosquat dependency called proc-macro1 and have since been deleted from crates.io.
Why do researchers suspect North Korea?
Wiz found that the attack's command-and-control path, IP issuer strings and Hostwinds infrastructure overlap with the Mastra and axios campaigns, which Microsoft and Mandiant have attributed to DPRK-linked actors.
What should developers who built the affected crates do?
Because the payload runs during cargo build, the Rust team and Wiz advise treating any workstation or CI runner that resolved a bad version as compromised, then rotating every reachable credential and resetting browser-stored logins.
Disclaimer. The information provided is not trading advice. Cryptopolitan.com holds no liability for any investments made based on the information provided on this page. We strongly recommend independent research and/or consultation with a qualified professional before making any investment decisions.

Hannah Collymore
Hannah is a writer and editor with nearly a decade of blog writing and event reporting experience in the crypto space. At Cryptopolitan, Hannah contributes to the news page, reporting and analyzing the latest developments in DeFi, RWA, crypto regulation, AI and frontier tech industries. She graduated from Arcadia university with a degree in Business Administration.







