Malicious Code Injection in kentung-31: A Threat to npm Packages
Summary
MAL-2025-157512: Malicious code in kentung-31 (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-31' is part of the npm ecosystem and has been identified as a component of the tea.xyz token reward campaign. This campaign has been known to flood the npm registry with malicious packages that contain scripts designed to manipulate package metadata and inflate developer reputation scores. The primary functionality of these packages is to automate the generation and publication of derivative packages, which can lead to significant pollution of the npm registry.
Vulnerability Detail
The vulnerability in 'kentung-31' originates from its malicious payload, which modifies the package.json file to remove private flags and alter version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages, potentially leading to security breaches and loss of trust in the ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-31If 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-31' package and any other packages associated with the tea.xyz token reward campaign. It is advisable to audit your package-lock.json file for any dependencies that may have been affected by this vulnerability.
Conclusion
The 'kentung-31' package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is essential for developers to be vigilant and regularly audit their dependencies to protect their projects from such vulnerabilities. Utilizing tools like Vulert can aid in real-time monitoring for open-source vulnerabilities.
See every vulnerability recorded for kentung-31 →
FAQ
'kentung-31' is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through automated package publishing.
The vulnerability can lead to the introduction of malicious code into your project, compromising its security and integrity.
You can use the Vulert platform to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
If you have used 'kentung-31', it is crucial to uninstall the package immediately and review your project for any potential security issues.
No patches are available for 'kentung-31' as it is a malicious package. The best course of action is to remove it from your project.
