# RUSTSEC-2026-0081: `logtrace` was removed from crates.io for malicious code

> A malicious Rust crate named logtrace was published to crates.io, potentially allowing remote code execution via a Remote Access Trojan.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Apr 2026

## What is RUSTSEC-2026-0081?

RUSTSEC-2026-0081 is a vulnerability in logtrace, published on 5 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

`logtrace` appeared to be downloading a RAT.

The malicious crate had 2 versions published on 2026-04-01 that had a total of 30 downloads. There
were no crates depending on this crate on crates.io.

Thanks to [Socket.dev](https://socket.dev/) for detecting and reporting this to the crates.io team!

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

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


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

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

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

## Is RUSTSEC-2026-0081 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: RUSTSEC-2026-0081 is a vulnerability in logtrace, published on 5 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of RUSTSEC-2026-0081 in the wild and no public exploit code.

Affected packages and fixed versions:
- logtrace (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-0081/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0081/index.md)
```

## Sources

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

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