greentic-setup
Affected
- introduced
1.3.1-dev.34027618345, fixed1.3.1-dev.34027618345.0(semver)
Fixed versions
1.3.1-dev.34027618345.0
Fix
- Fixed version
1.3.1-dev.34027618345.0cargo update -p greentic-setup --precise 1.3.1-dev.34027618345.0
Advisory
Also known as: None
greentic-setup 1.3.1-dev.34027618345 was removed from crates.io due to containing malicious code
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.
Not rated by the source.
1.3.1-dev.34027618345, fixed 1.3.1-dev.34027618345.0 (semver)1.3.1-dev.34027618345.0
1.3.1-dev.34027618345.0cargo update -p greentic-setup --precise 1.3.1-dev.34027618345.0Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: RustSec Advisory Database · CC0-1.0