Crates.io security team warns of video call attacks on Rust maintainers

Adam Harvey and the crates security team have issued a warning, relayed by Simon Willison on his link blog on 17 September 2026, about an ongoing campaign targeting rust-lang members and owners of popular crates. The team says attackers are trying to compromise maintainers' devices and accounts in order to publish malware through them. The method: a video call is arranged under a plausible positive pretext, a job offer, a project, or a contract opportunity, and once the call is underway it is used to push the target toward one of two actions, installing something on their computer (the example given is a purportedly missing audio codec) or running a command that has been placed on their clipboard. The warning states that last month this exact trick already produced a successful supply chain attack against the array ref crate, among others not identified by name. Willison adds his own comment on why this matters structurally: almost any piece of software depends on open source, and that dependency chain is really a network of human beings, every person with publishing rights to any package in it is a potential point of entry. His suggested mitigation is dependency cooldowns, deliberately waiting a few days after a new package release before upgrading to it, so that if a release has been tampered with, someone else has a chance to spot it first.

Key facts

Adam Harvey and the crates.io security team warn of an ongoing campaign against rust-lang members and popular-crate owners.
The vector is a video call set up under a positive pretext (job, project, or contract) that is then used to get the target to install malware, such as a fake missing audio codec, or run a command from the clipboard.
Last month the same technique was already used in a successful supply chain attack against the array ref crate, among others.
The goal is to compromise maintainer devices and accounts in order to publish malware through them.
Simon Willison, relaying the warning, recommends dependency cooldowns, waiting a few days before adopting new package releases, as the best current defense.

Why it matters

Open source security usually gets discussed in terms of code review and automated scanning, but this warning describes attackers going after the humans instead: a maintainer tricked on a video call is a much shorter path into a package's publishing pipeline than finding and exploiting a bug in the code itself. The warning cites one supply chain attack that has already succeeded this way, against the array ref crate, so this is not a hypothetical risk being floated in advance.

Who it affects

Anyone with publishing rights to a crate in the Rust ecosystem, and by extension anyone whose software depends on those crates. Adam Harvey and the crates security team frame the target list as rust-lang members and owners of popular crates specifically. Simon Willison broadens the point to essentially all software, since almost everything depends on open source, and every person with publishing rights anywhere in that dependency network is a potential attack vector.

How to use it

Maintainers who get an unsolicited video call framed around a job, project, or contract opportunity should treat requests to install unfamiliar software, including anything billed as a missing codec, or to run a command copied to the clipboard, as a red flag rather than routine troubleshooting. Willison's suggested practical defense for consumers of packages, rather than maintainers, is a dependency cooldown: hold off adopting a newly released package version for a few days so a compromised release has a chance to be caught by someone else before it reaches your build.

How solid is it

The warning comes directly from Adam Harvey and the crates security team and is relayed, not authored, by Simon Willison, who adds his own separate commentary about the structural risk and the cooldown mitigation. The source does not give a specific date for last month's successful attack, does not name the other crates affected beyond array ref, and gives no technical detail on how the malware or the clipboard-command mechanism actually works, so the account should be read as a summary warning rather than a full incident report.

Risks and caveats

Key details are missing from the public warning as relayed here: no date for the attack beyond 'last month', no full list of affected crates, no description of what the malware does once installed, and no count of how many accounts or targets were affected. Adam Harvey's role or title beyond being named alongside the crates security team is also not stated.

“We believe that there is an ongoing campaign targeting rust-lang members and owners of popular crates that is attempting to compromise devices and accounts in order to use them to publish malware.”

— Adam Harvey and the crates security team, quoted by Simon Willison