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 9 November 2026.

Which products and versions are affected?

env-test-guard (crates.io) SEMVER:introduced=0.0.0-0; Env-Test-Guard 0.0.0 (all versions).

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 with local access, in a software library.

Check whether you run env-test-guard (crates.io) or Env-Test-Guard 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.

env-test-guard malicious code in Rust crate

Severity: info · Published 2026-11-09

A Rust library package named env-test-guard was published on crates.io containing malicious code designed to steal environment variables—such as API keys and credentials—and send them to an attacker's server. The malicious versions remained available for eight months before discovery and removal, though there was no evidence the package was widely used.

Vendors: crates.io.

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 9 November 2026.
Which products and versions are affected?: env-test-guard (crates.io) SEMVER:introduced=0.0.0-0; Env-Test-Guard 0.0.0 (all versions).
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 with local access, in a software library.
Am I affected?: Check whether you run env-test-guard (crates.io) or Env-Test-Guard 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 malicious crate attempted credential exfiltration by reading environment variables and transmitting them to an attacker-controlled URL. The package had no legitimate dependencies and appeared to be designed as a trojan; it was published in two versions on March 24–25, 2026, and removed from crates.io on November 9, 2026, approximately 230 days later.

Affected products

env-test-guard env-test-guard 0.0.0 (all versions)

Timeline

2026-03-24: other: Malicious versions published to crates.io
2026-11-09: disclosed: Crate removed from crates.io; vulnerability reported
2026-11-10: advisory: RUSTSEC-2026-0469 advisory issued

References

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