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?

top_level_crate (crates.io) SEMVER:introduced=0.0.0-0; Unknown Top Level Crate 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.

Check whether you run top_level_crate (crates.io) or Unknown Top Level Crate 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.

top_level_crate malicious code with telemetry exfiltration

Severity: info · Published 2026-11-06

A Rust library package named top_level_crate was discovered to contain malicious code designed to exfiltrate telemetry and environment data during the build process. The package was published on crates.io in March 2025 and remained undetected for approximately 20 months before removal. While there was no evidence of widespread usage, any project that included this dependency could have had sensitive build environment information intercepted.

Vendors: crates.io, Unknown.

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?: top_level_crate (crates.io) SEMVER:introduced=0.0.0-0; Unknown Top Level Crate 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 top_level_crate (crates.io) or Unknown Top Level Crate 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 top_level_crate library contained malicious code that attempted to send telemetry from the build environment to an arbitrary external URL during compilation. The attack vector is supply chain compromise via dependency injection: any Rust project that explicitly added this package to its Cargo.toml would execute the malicious code at build time. The advisory indicates no patched versions exist and the crate has been permanently removed from crates.io.

Affected products

<unknown> top_level_crate 0.0.0

Timeline

2025-03-01: other: Malicious version 0.0.0 published to crates.io
2026-11-06: disclosed: Vulnerability reported; crate removed from crates.io
2026-11-10: advisory: RUSTSEC-2026-0467 advisory issued

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.