RUSTSEC-2026-0175: `onering` 1.4.1 was removed from crates.io for malicious code

What to do

1. See which version you have: cargo tree -i onering (it also shows which of your dependencies pulls it in).
2. Update within your version requirement: cargo update -p onering. If the fix is a newer major or minor than your requirement allows, raise it in Cargo.toml (for example onering = "1.4.2") or update the dependency that pulls it in.
3. Check again with cargo audit, or paste your Cargo.lock into our Cargo.toml checker.

Details from the advisory

A new version of the onering crate was published with code that attempted to exfiltrate both metadata and code from the project it was included within.

One malicious version was published on 2026-06-10, approximately six hours before removal. This crate has no dependencies on crates.io, and there is no evidence of actual usage of the compromised version.

Thanks to Charlie Eriksen for the report.

References

• Package: crates.io/crates/onering
• Advisory: rustsec.org/advisories/RUSTSEC-2026-0175.html

From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.