Malicious Code Injection in kentung-78: A Threat to npm Packages
Summary
MAL-2025-157562: Malicious code in kentung-78 (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-78' 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 used to inflate developer reputation scores for token rewards. Its functionality, while seemingly innocuous, has been compromised, making it susceptible to malicious exploitation.
Vulnerability Detail
The vulnerability in 'kentung-78' originates from its association with a malicious campaign that floods the npm registry with derivative packages. The malicious code 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 use 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-78If 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-78' package and instead look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before installation.
Conclusion
The 'kentung-78' package poses a significant security risk due to its malicious code that modifies package configurations and floods the npm registry. It is crucial for developers to be vigilant about the packages they use and to take immediate action to remove any compromised packages. Regular monitoring and updates can help mitigate these risks.
See every vulnerability recorded for kentung-78 →
FAQ
'kentung-78' is an npm package that has been identified as part of a malicious campaign to inflate developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.
You should immediately uninstall 'kentung-78' using the command 'npm uninstall kentung-78' and review your project's dependencies for any other potentially compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application for vulnerabilities using the Vulert playground without any signup.
Yes, you should look for alternative packages that provide similar functionality but have a good reputation and are actively maintained. Always check the package's documentation and community feedback.
