Malicious Code Injection in kentung-67 Package: npm Vulnerability Overview
Summary
MAL-2025-157550: Malicious code in kentung-67 (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-67 package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which are often created to inflate developer reputation scores for token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in the kentung-67 package stems from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and generates random package names, leading to the pollution of the npm registry. This can result in significant security risks, including the potential for developers to unknowingly install compromised packages, which can further propagate malicious code.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-67If 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-67 package and instead look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your package dependencies using tools like npm audit to identify and address vulnerabilities.
Conclusion
The kentung-67 package poses a significant security risk due to its malicious code designed to manipulate package metadata and pollute the npm registry. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for kentung-67 →
FAQ
The kentung-67 package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The malicious code modifies your project's package.json file, potentially exposing your project to further vulnerabilities and pollution of the npm registry.
You should immediately remove the kentung-67 package from your project and check for any other affected packages. Use npm uninstall kentung-67 to remove it.
You can use tools like npm audit to scan your project for vulnerabilities. Additionally, Vulert provides real-time monitoring for open-source vulnerabilities using your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
