Malicious npm packages jito-bundle, jito-bundle-tip, jito-bundle-service, jito-bundle-tip-service — full system compromise
Severity: critical · Patch status: no-fix-needed · Since 2026-11-17
On 2026-11-17 GitHub published four critical malware advisories for npm packages jito-bundle, jito-bundle-tip, jito-bundle-service and jito-bundle-tip-service, flagged as embedded malicious code (CWE-506). Every published version (= 0) is affected and no patched versions exist, so the packages should be treated as malicious from inception — likely typosquatting the legitimate Jito bundling tooling for Solana. GitHub's guidance states any machine with these packages installed or running must be considered fully compromised, with attacker access to secrets and keys. Download counts are very low (2-6 per month), limiting reach, but anyone who installed them is exposed. Removal of the package alone is not guaranteed to remove all malicious software. No fix will be issued; remediation is removal plus credential rotation and system rebuild.
What to do
- Rotate all secrets, keys, wallets and credentials stored on any machine where these packages were installed, using a clean machine
- Remove the packages and rebuild/reimage affected systems, as removal may not eliminate all malicious software
- Audit systems for signs of compromise and any persistence mechanisms
- Check dependency trees and lockfiles for these package names and block them in CI/CD and registries
Sources
All live incidents on Threat Watch