Malicious Code Injection in tealove-coki13 Package - npm Vulnerability
Summary
MAL-2025-168168: Malicious code in tealove-coki13 (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 tealove-coki13 package is part of a broader campaign associated with the tea.xyz token reward system. This package is designed to facilitate automatic publishing of derivative packages on the npm registry, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious scripts that compromise the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in the tealove-coki13 package stems from its inclusion of malicious code that modifies the package.json file. This code removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants that pollute the npm registry. The origin of this vulnerability is linked to a campaign that exploits npm's publishing mechanisms, posing significant risks to developers and users by potentially introducing untrusted code into their projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-coki13If 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 workaround, you can avoid using the tealove-coki13 package altogether. If it is already in your project, consider using a tool like Vulert to monitor your package-lock.json file for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without needing to sign up.
Conclusion
The tealove-coki13 package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities using tools like Vulert.
See every vulnerability recorded for tealove-coki13 →
FAQ
The tealove-coki13 package is part of a campaign that aims to inflate developer reputation scores through automatic publishing of derivative npm packages.
The vulnerability can introduce untrusted code into your project, potentially compromising its security and integrity.
You should uninstall the package immediately using the command npm uninstall tealove-coki13.
You can use tools like Vulert, which monitors your package-lock.json for vulnerabilities in real-time.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities without needing to create an account.
