Malicious Code Injection in kentung-36 Package: npm Vulnerability Overview
Summary
MAL-2025-157517: Malicious code in kentung-36 (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-36 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign aimed at exploiting the npm registry. It is designed to manipulate package metadata and inflate developer reputation scores through automated scripts. The presence of this package poses significant risks to developers and users relying on npm for secure package management.
Vulnerability Detail
The vulnerability stems from the malicious code embedded within the kentung-36 package. Originating from the tea.xyz token reward campaign, this package includes scripts that automatically generate and publish derivative packages with randomized names. These scripts modify the package.json file by removing private flags, altering version numbers, and continuously republishing variants, which pollutes the npm registry. This can lead to compromised security, as developers may unknowingly install these malicious packages, potentially exposing their applications to further vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-36If 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, avoid using the kentung-36 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-36 package poses a significant security risk due to its malicious code designed to manipulate npm registry data. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining secure software practices.
See every vulnerability recorded for kentung-36 →
FAQ
The kentung-36 package is an npm package that has been identified as part of a malicious campaign aimed at manipulating the npm registry.
The malicious code can modify your package.json file, remove private flags, and republish variants, potentially leading to security vulnerabilities in your application.
You should uninstall the kentung-36 package immediately using 'npm uninstall kentung-36' and monitor your project for any other vulnerabilities.
Regularly update your dependencies, use tools like Vulert to monitor for vulnerabilities, and verify the integrity of packages before installation.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check if your application is affected by vulnerabilities using the Vulert playground without any signup.
