Malicious Code Vulnerability in kentung-53: Exploiting npm for Token Rewards
Summary
MAL-2025-157535: Malicious code in kentung-53 (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-53' 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 rewards related to the tea protocol.
Vulnerability Detail
The vulnerability in 'kentung-53' originates from its malicious design, which includes scripts that modify the package.json file to remove private flags, alter version numbers, and generate random package names. This results in continuous republishing of variants that pollute the npm registry, potentially leading to security risks for developers who unknowingly install these packages. The malicious payload can compromise the integrity of the npm ecosystem and mislead developers regarding the authenticity of packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-53If 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 avoid using the 'kentung-53' package and any other packages associated with the tea.xyz token reward campaign. Regularly audit your package dependencies to identify and remove any malicious packages.
Conclusion
The 'kentung-53' package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating developer reputation scores. It is essential to remove this package and remain vigilant about the dependencies used in your projects. Utilizing tools like Vulert can aid in identifying and mitigating such vulnerabilities.
See every vulnerability recorded for kentung-53 →
FAQ
The impact includes potential pollution of the npm registry, misleading developers, and compromising the integrity of applications that rely on affected packages.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By analyzing your package-lock.json file, Vulert can help identify affected packages.
No, there is no patch available for the kentung-53 package as it is inherently malicious. The best course of action is to uninstall it.
Regularly audit your dependencies, use tools like Vulert to monitor for vulnerabilities, and avoid using packages from untrusted sources.
Immediately uninstall the package using 'npm uninstall kentung-53' and review your project for any other potentially malicious dependencies.
