Malicious Code Vulnerability in kentung-22 Package
Summary
MAL-2025-157502: Malicious code in kentung-22 (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-22 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 can inflate developer reputation scores in exchange for token rewards. However, it has been identified as containing malicious scripts that compromise its integrity and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in the kentung-22 package originates from its involvement in a malicious campaign that modifies package.json files to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, which pollutes the npm registry and can potentially harm developers' reputations and the overall ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall kentung-22If 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-22 package and monitor your project for any dependencies that may have been affected by it. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities.
Conclusion
The kentung-22 package poses a significant risk due to its malicious behavior, which can compromise the integrity of the npm registry and affect developers' reputations. It is crucial to remove this package from your project and monitor for any vulnerabilities using tools like Vulert.
See every vulnerability recorded for kentung-22 →
FAQ
The kentung-22 package is an npm package involved in a token reward campaign that has been identified as containing malicious code.
The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project by introducing unwanted packages.
You should uninstall the kentung-22 package immediately using 'npm uninstall kentung-22' and check for any affected dependencies.
Yes, you can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without needing to access the code or install anything.
There is no patch for the kentung-22 package as it is recommended to remove it entirely from your project.
