Malicious Code Detected in kentung-42: A Threat to npm Ecosystem
Summary
MAL-2025-157524: Malicious code in kentung-42 (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-42' is part of the npm ecosystem, which is widely used for JavaScript package management. It is designed to facilitate the sharing and reuse of code among developers. However, this package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages, thereby inflating developer reputation scores for token rewards.
Vulnerability Detail
The vulnerability in 'kentung-42' originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically generate and publish derivative packages with randomized names, modifying the package.json file to remove private flags and change version numbers. The malicious payload leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-42If 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 workaround, you can monitor your project for any instances of the 'kentung-42' package and remove it if found. You can use the following command to check for its presence: 'npm list kentung-42'. If it appears in the list, proceed to uninstall it.
Conclusion
The 'kentung-42' package poses a significant threat to the npm ecosystem due to its malicious behavior. It is crucial for developers to be vigilant and remove such packages from their projects to maintain the integrity of their applications. Regular monitoring and updating of dependencies can help mitigate the risk of similar vulnerabilities.
See every vulnerability recorded for kentung-42 →
FAQ
'kentung-42' is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.
You should uninstall 'kentung-42' immediately using the command 'npm uninstall kentung-42'.
Regularly update your packages and monitor your project for any malicious packages using tools like Vulert.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
