VulnerabilityRUSTSEC-2026-0263 · tinymember
RUSTSEC-2026-0263: `tinymember` was removed from crates.io due to affiliation with malicious code
Short answerA security vulnerability in the tinymember crate: `tinymember` was removed from crates.io due to affiliation with malicious code. No severity score was published. No fixed version: replace the crate or remove the affected code path.
| Crate | tinymember |
|---|---|
| Type | Vulnerability |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2026-08-20 |
| Last changed | 2026-08-20 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i tinymember. - Avoid the affected API, or replace the crate.
Details from the advisory
While tinymember did not directly contain malicious code, it was owned by the same user as arone and aronenao, which contained suspicious build scripts.
This crate had 2 versions published on 2026-08-18 that had a total of 27 downloads. There were no crates depending on this crate on crates.io. The crate was removed from crates.io and the user account was locked.
References
- Package: crates.io/crates/tinymember
- Advisory: rustsec.org/advisories/RUSTSEC-2026-0263.html
- Web: blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayref
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Other advisories for tinymember
Up next
Same cratetinymember: security historyEvery advisory for this crate, and whether it is safe to use today.Read it next →Did this answer your question?