Malicious Code Injection in tealove-okta32: A Threat to npm Packages
Summary
MAL-2025-168610: Malicious code in tealove-okta32 (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 tealove-okta32 is part of a broader campaign associated with the tea.xyz token reward initiative. This npm package is designed to facilitate token rewards by generating and publishing derivative packages. However, it has been compromised to include malicious scripts that manipulate package metadata, posing a significant risk to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove-okta32 stems from its association with a malicious campaign that floods the npm registry with derivative packages. These packages contain scripts that automatically modify the package.json file, removing private flags, altering version numbers, and generating random package names. This behavior not only inflates developer reputation scores but also pollutes the npm registry, making it difficult for legitimate packages to be discovered. The malicious payload can lead to security breaches and compromise the integrity of applications relying on affected packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-okta32If 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 tealove-okta32 package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity of packages before including them in your project.
Conclusion
The tealove-okta32 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to uninstall this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for tealove-okta32 →
FAQ
Tealove-okta32 is an npm package that is part of a token reward campaign, which has been compromised to include malicious code.
The malicious code modifies package metadata, which can lead to security vulnerabilities and pollution of the npm registry.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
You should uninstall the package immediately using 'npm uninstall tealove-okta32' and check for any other affected packages.
Yes, consider looking for other npm packages that provide similar functionality without the associated risks.
