# RUSTSEC-2026-0280: `greentic-setup-dev` 1.3.34027618345 was removed from crates.io due to containing malicious code

> A malicious Rust crate variant containing PolinRider malware was published to crates.io, executing code when opened in VS Code.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Sep 2026

## What is RUSTSEC-2026-0280?

RUSTSEC-2026-0280 is a vulnerability in greentic-setup-dev, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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

One malicious version was published on 2026-09-06, approximately 27 hours
before removal. This crate has no dependencies on crates.io. 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.

## Which versions are affected by RUSTSEC-2026-0280?

1 open source package ship an affected version, including greentic-setup-dev.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `greentic-setup-dev` | crates.io | From 1.3.34027618345 | 1.3.34027618346-0 |

## How do I fix RUSTSEC-2026-0280?

Upgrade greentic-setup-dev to 1.3.34027618346-0 or later.

## Is RUSTSEC-2026-0280 being exploited?

There is no known exploitation of RUSTSEC-2026-0280 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0280 and fix it if it is affected.

What it is: RUSTSEC-2026-0280 is a vulnerability in greentic-setup-dev, published on 7 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of RUSTSEC-2026-0280 in the wild and no public exploit code.

Affected packages and fixed versions:
- greentic-setup-dev (crates.io): affected from 1.3.34027618345; fixed in 1.3.34027618346-0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/RUSTSEC-2026-0280/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0280/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0280

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2026-0280/
Summaries are generated and may contain mistakes; the official description above is the record.