Malware in @zynkit/jwtbytes
Malware was discovered in the npm package @zynkit/jwtbytes, resulting in full system compromise for any computer with the package installed or running. All secrets and keys on affected systems should be rotated immediately from a different computer.
- Disclosed
- Last updated
- Blast radius
- Any system with the package installed or running
- Ecosystems
- Attack vectors
- Affected entities
- @zynkit/jwtbytes
A malicious package named @zynkit/jwtbytes was published to npm and contained malware. Installation or execution of this package grants an outside entity full control of the affected computer.\n\nAny system with this package installed or running should be considered fully compromised. All secrets, keys, and credentials stored on affected computers must be rotated immediately from a different, unaffected system.\n\nWhile the package should be removed, complete removal of all malicious software cannot be guaranteed due to the level of system access the malware may have obtained. A full security audit and potential system rebuild may be necessary for affected systems.\n\nThe incident was disclosed via GitHub Advisory GHSA-xpqg-89v5-vc7w on 2026-08-17.
Indicators of compromise
- Packages
- @zynkit/jwtbytes
Remediation
- Immediately remove @zynkit/jwtbytes from all systems
- Rotate all secrets, keys, and credentials from a different, unaffected computer
- Conduct a full security audit of any system that had the package installed
- Consider rebuilding affected systems from clean media
- Monitor for any signs of unauthorized access or data exfiltration
- Review logs for any suspicious activity during the time the package was installed
Sources
- GitHub Advisory GHSA-xpqg-89v5-vc7w · GitHub Advisory Database
Cite this entry
"Malware in @zynkit/jwtbytes." supplychainattack.org, Supply Chain Attack Incident Catalog. Disclosed August 17, 2026; last updated August 17, 2026. https://supplychainattack.org/incident/malware-in-zynkit-jwtbytes-set0ua
Suggest a correction
Found an error or have a newer source? Corrections to factual errors take priority over new entries.
Related incidents
- containedcritical
Malicious code in 3-buildsight-web (npm)
The npm package 3-buildsight-web contains malicious code that fetches and executes arbitrary JavaScript from a remote Bitbucket URL on module load, granting full page privileges to an unverified third party.
npmCompromised package - resolvedcritical
Malicious code in @usaa-grp-personal-profile/personal-profile-common (npm)
Malicious package @usaa-grp-personal-profile/personal-profile-common version 999.0.0 published to public npm as a dependency-confusion attack targeting an organization's internal registry. The package contains preinstall and postinstall hooks that exfiltrate hostname, username, and working directory to an attacker-controlled OAST endpoint on every install.
npmDependency confusionCompromised package - resolvedcritical
Malicious code in create-coin (npm)
create-coin@20.1.1 on npm contained malicious postinstall code that collected sensitive environment variables, credentials, and host reconnaissance data. The package impersonated an esbuild platform build and exfiltrated data to a hardcoded endpoint.
npmCompromised packageTyposquatting - resolvedcritical
Malicious code in @syncraft-labs/vue (npm)
The npm package @syncraft-labs/vue version 0.4.1 contained malicious obfuscated code in its ESM build that implements a blockchain-hosted C2 dropper (EtherHiding pattern), enabling remote code execution on any consumer importing the package.
npmCompromised package