{"answers":{"affected":"1 open source package ship an affected version, including microsoftsystem64.","exploited":"There is no known exploitation of RUSTSEC-2026-0102 in the wild and no public exploit code.","fix":"No fix has been published for RUSTSEC-2026-0102 yet. Limit exposure of the affected software until one is available.","what":"RUSTSEC-2026-0102 is a vulnerability in microsoftsystem64, published on 13 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for RUSTSEC-2026-0102 and fix it if it is affected.\n\nWhat it is: RUSTSEC-2026-0102 is a vulnerability in microsoftsystem64, published on 13 Apr 2026. 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-2026-0102 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- microsoftsystem64 (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-2026-0102/ (Markdown: https://insights.sbomify.com/RUSTSEC-2026-0102/index.md)","id":"RUSTSEC-2026-0102","markdown":"https://insights.sbomify.com/RUSTSEC-2026-0102/index.md","name":"RUSTSEC-2026-0102","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"no_fix_stated","impacts":["data_read","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Rust crate","requires_auth":"none","summary":"A malicious Rust crate exfiltrates sensitive files and credentials, requiring developers to remove it immediately.","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":"`microsoftsystem64` installs a hardcoded SSH authorized_keys entry (persistence/backdoor) and scans for sensitive files (.env, credential-like JSON names, keyword-matching docs), reads their contents, base64-encodes where needed, and exfiltrates everything to a remote server via HTTP. It also packages and uploads Telegram Desktop tdata, indicating targeted credential/session/data harvesting.\n\nThe malicious crate had 9 versions published on 2026-04-09 that had a total of 6346 downloads. There were no crates depending on this crate on crates.io.\n\nThanks to [Socket.dev](https://socket.dev/) and [sitsh](https://sit.sh/) for detecting and reporting this to the crates.io team!","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":"`microsoftsystem64` was removed from crates.io for malicious code","id":"RUSTSEC-2026-0102","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"crates.io","product":null,"products":[],"type":"supply_chain","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"crates.io","fixed":[],"introduced":["0.0.0-0"],"last_affected":[],"package":"microsoftsystem64","purl":"pkg:cargo/microsoftsystem64","source":"RUSTSEC-2026-0102"}],"products":null,"published":"2026-04-13","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 exfiltrates sensitive files and credentials, requiring developers to remove it immediately.","url":"https://insights.sbomify.com/RUSTSEC-2026-0102/"}