Malicious Code Injection in kentung-58: A Threat to npm Users
Summary
MAL-2025-157540: Malicious code in kentung-58 (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-58' is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This package is designed to automatically generate and publish derivative packages with randomized names, aiming to inflate developer reputation scores for token rewards. Its functionality is compromised due to the presence of malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in 'kentung-58' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-58If 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, avoid using the 'kentung-58' package and consider using alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before installation.
Conclusion
The 'kentung-58' package poses a significant risk due to its malicious behavior of modifying package metadata and flooding the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for kentung-58 →
FAQ
The main risk is that it modifies package.json files, potentially leading to the installation of compromised packages and security vulnerabilities in your applications.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
If you have installed kentung-58, you should uninstall it immediately using 'npm uninstall kentung-58' and review your project for any other potentially compromised packages.
Yes, there are many alternative packages available in the npm registry that provide similar functionalities. Always ensure to check the package's reputation and reviews before installation.
To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and only install packages from trusted sources.
