{"answers":{"affected":"1 open source package ship an affected version, including custom-req-on-workers.","exploited":"There is no known exploitation of RUSTSEC-2025-0160 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2025-0160 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2025-0160 is a vulnerability in custom-req-on-workers, published on 30 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2025-0160 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2025-0160 is a vulnerability in custom-req-on-workers, published on 30 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of RUSTSEC-2025-0160 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- custom-req-on-workers (crates.io): affected from 0.0.0-0; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/RUSTSEC-2025-0160/ (Markdown: https://insights.sbomify.com/RUSTSEC-2025-0160/index.md)","id":"RUSTSEC-2025-0160","markdown":"https://insights.sbomify.com/RUSTSEC-2025-0160/index.md","name":"RUSTSEC-2025-0160","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust crate","requires_auth":"none","summary":"A malicious Rust crate attempted to exfiltrate environmental data from the host system before being removed from crates.io.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"`custom-req-on-workers` was part of a campaign that attempted to exfiltrate\nenvironmental data from the host.\n\nThe malicious crate had 1 version published in January 2025, and had no\nevidence of actual usage. This crate had no dependencies on crates.io.","ecosystems":["crates.io"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"`custom-req-on-workers` was removed from crates.io for malicious code","id":"RUSTSEC-2025-0160","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"custom-req-on-workers","purl":"pkg:cargo/custom-req-on-workers","source":"RUSTSEC-2025-0160"}],"products":null,"published":"2025-01-30","related":[],"sources":[{"class":"open","licence":"CC0 1.0","name":"RustSec","prefix":"RUSTSEC"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"A malicious Rust crate attempted to exfiltrate environmental data from the host system before being removed from crates.io.","url":"https://insights.sbomify.com/RUSTSEC-2025-0160/"}