# RUSTSEC-2026-0171: `logflux` was removed from crates.io for malicious code

> A malicious Rust crate named logflux was published to crates.io, attempting to download and execute a payload on the user's machine.

- **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:** No
- **Published:** 3 Jun 2026

## What is RUSTSEC-2026-0171?

RUSTSEC-2026-0171 is a vulnerability in logflux, published on 3 Jun 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

The `logflux` crate attempted to download and run a malicious payload on the
user's machine.

The malicious crate had 1 version published on 2026-04-26, approximately 1
month before removal, and had no evidence of actual usage. This crate had no
dependencies on crates.io.

Thanks to Paweł Bis for discovering and reporting this crate!

This appears to have been part of a campaign targeting people applying for Rust
jobs. Please be careful with take-home assignments, especially if they ask you
to use specific dependencies.

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

1 open source package ship an affected version, including logflux.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `logflux` | crates.io | From 0.0.0-0 | None |

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

No fix has been published for RUSTSEC-2026-0171 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2026-0171 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0171 is a vulnerability in logflux, published on 3 Jun 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-0171 in the wild and no public exploit code.

Affected packages and fixed versions:
- logflux (crates.io): affected from 0.0.0-0; no fix listed

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-0171/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0171/index.md)
```

## Sources

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

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