Malicious Code Injection in kentung-66 Package - npm Vulnerability
Summary
MAL-2025-157549: Malicious code in kentung-66 (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-66 package is part of the npm ecosystem, typically used for various JavaScript functionalities. However, it has been identified as part of a malicious campaign associated with the tea.xyz token reward system. This package is designed to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata, thereby inflating developer reputation scores.
Vulnerability Detail
The vulnerability in the kentung-66 package stems from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and creates random package names. This behavior not only compromises the integrity of the npm registry but also poses a risk of dependency confusion and potential exploitation of applications relying on these packages. The origin of this vulnerability is linked to a broader trend of malicious packages flooding the npm ecosystem, specifically targeting users involved in the tea protocol token rewards.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-66If 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 workaround, you can prevent the installation of the kentung-66 package by using npm's package-lock.json to lock your dependencies. Additionally, you can monitor your project for vulnerabilities using tools like Vulert, which analyzes your package-lock.json file for any known security issues.
Conclusion
The kentung-66 package poses a significant risk due to its malicious code designed to manipulate the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help ensure the security of your applications.
See every vulnerability recorded for kentung-66 →
FAQ
The kentung-66 package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The vulnerability can lead to the installation of malicious code, which may compromise your application's integrity and security.
You should immediately remove the kentung-66 package from your project and monitor for any updates or patches.
You can use tools like Vulert, which allows you to check your package-lock.json for vulnerabilities without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
