# RUSTSEC-2023-0118: `win_run_rs` was removed from crates.io for malicious code

> A malicious Rust crate named win_run_rs was published to crates.io to execute arbitrary malware on Windows hosts.

- **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:** 15 Nov 2023

## What is RUSTSEC-2023-0118?

RUSTSEC-2023-0118 is a vulnerability in win_run_rs, published on 15 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

This crate was part of a typosquatting malware cluster published by the user
`Kraded` to run an arbitrary malware payload on Windows hosts.

This advisory is to retrospectively document this attempted attack. The version
information and download records of the malicious crate are no longer
available. The related malicious crates have been yanked, and the malicious
account has been banned.

## Which versions are affected by RUSTSEC-2023-0118?

1 open source package ship an affected version, including win_run_rs.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `win_run_rs` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2023-0118?

No fix has been published for RUSTSEC-2023-0118 yet. Limit exposure of the affected software until one is available.

## Is RUSTSEC-2023-0118 being exploited?

There is no known exploitation of RUSTSEC-2023-0118 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2023-0118 and fix it if it is affected.

What it is: RUSTSEC-2023-0118 is a vulnerability in win_run_rs, published on 15 Nov 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of RUSTSEC-2023-0118 in the wild and no public exploit code.

Affected packages and fixed versions:
- win_run_rs (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/RUSTSEC-2023-0118/ (Markdown: https://insights.sbomify.com/RUSTSEC-2023-0118/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2023-0118

---
From sbomify Insights: https://insights.sbomify.com/RUSTSEC-2023-0118/
Summaries are generated and may contain mistakes; the official description above is the record.