Malicious Code Injection in kentung-64 Package
Summary
MAL-2025-157547: Malicious code in kentung-64 (npm). Affected versions are not published. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The kentung-64 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate automated publishing of derivative packages, which can inflate developer reputation scores for token rewards. Its functionality includes generating and publishing packages with randomized names, which can lead to pollution of the npm registry.
Vulnerability Detail
The vulnerability in the kentung-64 package stems from its malicious code that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, which can lead to the continuous republishing of variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which employs such tactics to manipulate developer reputation scores.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-64
If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary measure, you can avoid using the kentung-64 package until a patched version is released. Additionally, consider using npm audit to check for vulnerabilities in your project and remove any affected packages.
Conclusion
The kentung-64 package contains a significant vulnerability due to its malicious code that alters package metadata and republishing behavior. It is crucial to update the package to a patched version and monitor your projects for vulnerabilities using tools like Vulert to maintain security.
See every vulnerability recorded for kentung-64 →
FAQ
The kentung-64 package is an npm package associated with automated publishing and is part of the tea.xyz token reward campaign.
The vulnerability can lead to the modification of your package.json file, potentially compromising your project's integrity and security.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without needing to sign up.
If you cannot update the package, consider removing it from your project and using alternative packages that do not have known vulnerabilities.
More information can be found in the vulnerability report on the Open Source Vulnerability database or by checking the package's repository on npm.