MalwarePublished 4 Nov 2026

@touchkey0111/jito-bundle (npm) · Malicious Code

Affects @touchkey0111/jito-bundleSource GCVE Database

Malicious package : remove @touchkey0111/jito-bundle and rotate any secrets on hosts that installed it.

Data as of 4 Nov 2026, 04:47 UTC

Classification

Malicious package

Published to npm · OSV MAL-2026-18588

What to do

Remove @touchkey0111/jito-bundle from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.

Affected software

Product	Affected	Fixed in
npm@touchkey0111/jito-bundle	Affected–	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

Description

The npm package @touchkey0111/jito-bundle contains malicious code that compromises any computer on which it is installed or running. Installation of this package can lead to full system compromise, including unauthorized access to secrets and keys stored on the affected machine. Removal of the package alone does not guarantee elimination of all malicious software introduced by it, and immediate rotation of all secrets and keys from a different, uncompromised computer is strongly advised.

Impact

Full compromise of the affected computer, including potential unauthorized access to all secrets and keys stored on the system. The attacker may maintain persistent control beyond the presence of the malicious package itself.

Defensive guidance

Remove the @touchkey0111/jito-bundle package immediately. Rotate all secrets and keys stored on the compromised computer from a separate, secure machine. Because the system may be fully compromised, consider rebuilding or thoroughly cleaning the affected environment to ensure removal of all malicious components.

Summary

The @touchkey0111/jito-bundle npm package is identified as malicious software. According to the source details, any system with this package installed or running should be considered fully compromised. The malicious code likely grants an external entity full control over the affected computer, putting all stored secrets and keys at risk. Because the compromise may extend beyond the package itself, simply uninstalling the package does not ensure complete remediation.

References

github.com/advisories/GHSA-wm3m-jxgh-45rj (opens in a new tab)

Community reviews

Loading reviews…

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Nov 2026, 04:47 UTC

Technical details

References

Community reviews