# gabby-types-sec malicious code in Rust crate

Source: https://junglewise.ai/threats/rustsec-2026-0470-gabby-types-sec-was-removed-from-crates-io-for-6e7f1340  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-11-09. Updated: 2026-11-11  
License: CC BY 4.0 with a link back

Severity: info · Published 2026-11-09

A Rust library package called gabby-types-sec was removed from the crates.io package repository after being discovered to contain malicious code. The package attempted to exfiltrate sensitive information from build environments by sending telemetry to an attacker-controlled server, potentially exposing credentials or proprietary source code to an unauthorized third party.

Vendors: [crates.io](https://junglewise.ai/threats/vendors/crates-io), [Unknown](https://junglewise.ai/threats/vendors/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 9 November 2026.

**Which products and versions are affected?** gabby-types-sec (crates.io) SEMVER:introduced=0.0.0-0; Unknown Gabby-Types-Sec 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 with local access or over the network, in a software library.

**Am I affected?** Check whether you run gabby-types-sec (crates.io) or Unknown Gabby-Types-Sec 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 gabby-types-sec crate contained malicious code designed to send telemetry from the build environment to an arbitrary URL, likely for credential or secrets exfiltration. The package was published on 2026-02-17 with a single version, remained undetected for approximately 9 months, and showed no evidence of actual adoption before removal from crates.io. The attack surface was limited due to lack of usage, but any developer who included this dependency in their build process could have had build-time secrets or environment variables exposed.

## Affected products

- <unknown> gabby-types-sec 0.0.0

## Timeline

- 2026-11-09: disclosed
- 2026-02-17: other: Malicious version published

## References

- [https://crates.io/crates/gabby-types-sec](https://crates.io/crates/gabby-types-sec)
- [https://rustsec.org/advisories/RUSTSEC-2026-0470.html](https://rustsec.org/advisories/RUSTSEC-2026-0470.html)