Malicious Code Injection in kentung-69: A Threat to npm Users
Summary
MAL-2025-157552: Malicious code in kentung-69 (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 package 'kentung-69' is part of a series of malicious npm packages associated with the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, posing significant risks to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in 'kentung-69' originates from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This results in the continuous republishing of variants that pollute the npm registry, potentially leading to confusion and misuse of legitimate packages. The malicious scripts included in the package (auto.js, autopublish.js, etc.) automate this harmful behavior, making it difficult for developers to track and manage their dependencies effectively.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-69If 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-69' package and replace it with a trusted alternative. Regularly audit your package-lock.json file for any suspicious packages and remove them promptly.
Conclusion
The 'kentung-69' package poses a significant risk to npm users due to its malicious behavior of modifying package files and republishing variants. It is crucial to remove this package and monitor your dependencies regularly to maintain the integrity of your projects. Utilizing tools like Vulert can aid in identifying and managing vulnerabilities effectively.
See every vulnerability recorded for kentung-69 →
FAQ
The primary threat is the automatic generation and publication of malicious packages that can pollute the npm registry, leading to potential misuse of legitimate packages.
You can use Vulert to monitor your project for vulnerabilities. By analyzing your package-lock.json file, Vulert provides real-time alerts for any open-source vulnerabilities.
If you have installed kentung-69, you should uninstall it immediately using 'npm uninstall kentung-69' and check your project for any other suspicious packages.
Yes, tools like Vulert can help you monitor and alert for open-source vulnerabilities in your software without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without any signup.
