Culture

Security Team Warns of Attacks on Rust Package Maintainers

The crates.io security team has warned that an ongoing social engineering campaign is targeting prominent Rust developers to compromise their devices and inject malware into popular packages.

Simon Willison2 days agoCulture
Illustration generated for this story

The crates.io security team and researcher Adam Harvey have issued an urgent warning regarding an active cyberespionage campaign targeting members of the Rust project and owners of widely used crates. Attackers are using sophisticated social engineering tactics to compromise the personal devices and accounts of these developers, aiming to leverage their publishing credentials to distribute malicious software through the open-source ecosystem.

According to the warning, the threat actors initiate contact under positive pretexts, such as job offers, project collaborations, or contract opportunities. Once they establish rapport, they schedule a video call with the target. During or prior to the meeting, the attackers attempt to trick the developer into executing malicious commands. Common vectors include convincing the victim to install a fake audio codec required for the call or manipulating them into running commands copied to their clipboard.

This social engineering technique has already yielded successful compromises. Last month, attackers managed to execute a supply chain attack against the array ref crate, among other packages, by hijacking developer credentials. The incident highlights the growing risk of human-centric vectors in software supply chains, where any developer with publishing rights to a dependency becomes a high-value target.

For software practitioners and security teams, this development underscores the fragility of relying on immediate open-source updates. Experts recommend implementing dependency cooldown periods, which involve waiting several days before upgrading to newly released package versions. This delay provides the security community with a window to detect and report compromised releases before they are widely integrated into production environments.

This is our own summary of reporting by Simon Willison

More in Culture