RUSTSEC-2026-0281: `greentic-setup` 1.3.1-dev.34027618345 was removed from crates.io due to containing malicious code

What to do

1. See which version you have: cargo tree -i greentic-setup (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p greentic-setup. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example greentic-setup = "1.3.1-dev.34027618345.0") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

A new version of the greentic-setup crate was published with a variant of the PolinRider malware included that would fire when a project depending on greentic-setup was opened in Visual Studio Code.

One malicious version was published on 2026-09-06, approximately 27 hours before removal. This crate is depended on by four other crates in the Greentic ecosystem, namely greentic-start, greentic-start-dev, greentic-operator, and greentic-operator-dev. We have no evidence that this crate version was downloaded by any actual users, but Greentic users should check their systems nonetheless.

Thanks to the Research Team at Nextron Systems GmbH for the report.

References

• Package: crates.io/crates/greentic-setup
• Advisory: rustsec.org/advisories/RUSTSEC-2026-0281.html

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.