# GHSA-99j7-fhr2-xfj4: `exploration` was removed from crates.io for malicious code

> A malicious Rust crate on crates.io attempted to download and execute remote payloads, posing a supply chain risk to developers.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Jun 2026
- **Also known as:** RUSTSEC-2026-0155

## What is GHSA-99j7-fhr2-xfj4?

GHSA-99j7-fhr2-xfj4 is a vulnerability in exploration, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A method within the `exploration` crate attempted to download and execute a payload from a remote site.

The malicious crate had 1 version published on 2026-06-02, approximately 1 hour before removal, and had no evidence of actual usage. This crate had no dependencies on crates.io.

Rustsec to Kirill Boychenko from the [Socket Threat Research Team](https://socket.dev/) for reporting this crate.

## Which versions are affected by GHSA-99j7-fhr2-xfj4?

3 open source packages ship an affected version, including exploration.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `exploration` | crates.io | All versions | None |
| `exploration` | crates.io | All versions | None |
| `exploration` | crates.io | From 0.0.0-0 | None |

## How do I fix GHSA-99j7-fhr2-xfj4?

No fix has been published for GHSA-99j7-fhr2-xfj4 yet. Limit exposure of the affected software until one is available.

## Is GHSA-99j7-fhr2-xfj4 being exploited?

There is no known exploitation of GHSA-99j7-fhr2-xfj4 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-99j7-fhr2-xfj4 and fix it if it is affected.

What it is: GHSA-99j7-fhr2-xfj4 is a vulnerability in exploration, published on 2 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-99j7-fhr2-xfj4 in the wild and no public exploit code.

Affected packages and fixed versions:
- exploration (crates.io): affected all versions; no fix listed
- exploration (crates.io): affected all versions; no fix listed
- exploration (crates.io): affected from 0.0.0-0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/GHSA-99j7-fhr2-xfj4/ (Markdown: https://insights.sbomify.com/GHSA-99j7-fhr2-xfj4/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-99j7-fhr2-xfj4

---
From sbomify Insights: https://insights.sbomify.com/GHSA-99j7-fhr2-xfj4/
Summaries are generated and may contain mistakes; the official description above is the record.