Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 6 November 2026.
- Which products and versions are affected?
- shinchina (crates.io) 0.0.0-0, SEMVER:introduced=0.0.0-0.
- Is there a fix for This vulnerability?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run shinchina (crates.io) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The shinchina Rust crate contained code that attempted to send telemetry from the build environment to an arbitrary remote URL, representing a supply-chain attack vector. The crate had no upstream dependencies on crates.io, and was published once in version 0.0.0-0 on 2025-03-01 before removal. No patched versions exist; removal from the registry is the only remediation.
Affected products
- crates.io shinchina 0.0.0-0
Timeline
- 2026-11-06: disclosed: Malicious code detected and advisory published
- 2025-03-01: other: Malicious version 0.0.0-0 published to crates.io
- 2026-11-10: other: Advisory issued; crate removed from crates.io