RUSTSEC-2026-0081 json
`logtrace` was removed from crates.io for malicious code
published 7mo ago modified 7mo ago
- cvss
- —
- not scored
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
`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!
Is RUSTSEC-2026-0081 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| crates.io | logtrace | >=0.0.0-0 |
no fix listed |
References
-
crates.io
/crates/logtrace
package
-
rustsec.org
/advisories/RUSTSEC-2026-0081.html
advisory
Sources
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.