# RUSTSEC-2026-0264: `proc-macro-en` was removed from crates.io due to malicious code

> Malicious Rust crate proc-macro-en executes arbitrary code during build, requiring developers to remove it from dependencies.

- **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:** 20 Aug 2026

## What is RUSTSEC-2026-0264?

RUSTSEC-2026-0264 is a vulnerability in proc-macro-en, published on 20 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

We identified that `proc-macro-en` contained the same build script as
`proc-macro1` and it was part of the same supply chain attack.

This crate had one single version published at 2026-08-20. The crate was
removed from crates.io and related user account was locked.

This crate was used as part of a malware campaign targeted at users of
`arrayref`, which was downloaded 2,285 times before being removed; see
[the `arrayref` advisory][arrayref-advisory] for more detail.

[arrayref-advisory]: https://rustsec.org/advisories/RUSTSEC-2026-0260.html

## Which versions are affected by RUSTSEC-2026-0264?

1 open source package ship an affected version, including proc-macro-en.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `proc-macro-en` | crates.io | From 0.0.0-0 | None |

## How do I fix RUSTSEC-2026-0264?

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

## Is RUSTSEC-2026-0264 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for RUSTSEC-2026-0264 and fix it if it is affected.

What it is: RUSTSEC-2026-0264 is a vulnerability in proc-macro-en, published on 20 Aug 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 RUSTSEC-2026-0264 in the wild and no public exploit code.

Affected packages and fixed versions:
- proc-macro-en (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-2026-0264/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0264/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/RUSTSEC-2026-0264

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