Malicious Code Injection in kentung-14: A Threat to npm Ecosystem
Summary
MAL-2025-157493: Malicious code in kentung-14 (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-14 package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others in the ecosystem, is intended to facilitate the development and distribution of JavaScript applications. However, it has been identified as part of a malicious campaign that aims to exploit the npm registry for token rewards, leading to significant security concerns for developers and users alike.
Vulnerability Detail
The vulnerability in kentung-14 stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these compromised packages, leading to potential data breaches or system vulnerabilities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-14If 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, you can avoid using the kentung-14 package and any other packages that may have been published as part of this malicious campaign. Regularly audit your dependencies using tools like npm audit to identify and mitigate risks.
Conclusion
The kentung-14 package poses a significant security risk due to its malicious code injection capabilities. Developers should take immediate action 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-14 →
FAQ
Kentung-14 is an npm package that has been identified as part of a malicious campaign targeting the npm registry.
The vulnerability can lead to the injection of malicious code into your project, potentially compromising your application's security and integrity.
You should immediately remove the kentung-14 package from your project and audit your dependencies for any other malicious packages.
You can use tools like npm audit or services like Vulert to monitor your dependencies for known vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
