Xinference PyPI compromise
A malicious pull request took secrets from the project's CI runner, and three trojanized xinference releases followed on PyPI. They ran on import and collected credentials, environment variables, SSH keys, cloud tokens and wallet data.
- First seen
- 2026-04-22
- Disclosed
- 2026-04-22
- Affected packages
- 1
- Attributed to
- Disputed: JFrog linked it to TeamPCP, which denied involvement
What to do
Treat any environment that installed or imported 2.6.0 to 2.6.2 as compromised and rotate the credentials it held. Reinstall from a trusted baseline on a release before 2.6.0 or a later release.
Check a lockfile for these releases →Affected releases
| Package | Registry | Versions |
|---|---|---|
| xinference | PyPI | 2.6.0, 2.6.1, 2.6.2 |
Advisories
Sources
- https://github.com/xorbitsai/inference/issues/4828 · xorbitsai/inference (maintainers, GitHub), 2026-04-22
- https://research.jfrog.com/post/xinference-compromise/ · JFrog Security Research, 2026-04-22
- https://osv.dev/vulnerability/MAL-2026-3000 · OpenSSF Malicious Packages (via OSV, analysis by kam193), 2026-04-22
Written up from the sources above and last checked on 2026-11-18. ShieldMap describes what was affected and what to do; it does not publish the malicious code or how it worked. Report a correction to [email protected].