Rust advisories / custom-req-on-workers
VulnerabilityRUSTSEC-2025-0160 · custom-req-on-workers
RUSTSEC-2025-0160: `custom-req-on-workers` was removed from crates.io for malicious code
Short answerA security vulnerability in the custom-req-on-workers crate: `custom-req-on-workers` was removed from crates.io for malicious code. No severity score was published. No fixed version: replace the crate or remove the affected code path.
| Crate | custom-req-on-workers |
|---|---|
| Type | Vulnerability (malicious) |
| Affected versions | Every version. |
| Fixed in | none |
| Severity | not scored |
| Published | 2025-01-30 |
| Last changed | 2026-03-30 |
| Also known as | none |
What to do
- Find who pulls it in:
cargo tree -i custom-req-on-workers. - Avoid the affected API, or replace the crate.
Details from the advisory
custom-req-on-workers was part of a campaign that attempted to exfiltrate environmental data from the host.
The malicious crate had 1 version published in January 2025, and had no evidence of actual usage. This crate had no dependencies on crates.io.
References
- Package: crates.io/crates/custom-req-on-workers
- Advisory: rustsec.org/advisories/RUSTSEC-2025-0160.html
From the RustSec Advisory Database (CC0-1.0) via the OSV export, downloaded Oct 24, 2026. Severity score computed from the published CVSS vector.
Up next
Are you affected?Check your whole dependency treePaste Cargo.lock: every advisory, for your exact versions.Read it next →Also worth your time
Did this answer your question?