Malicious Code Injection in tealove-okta34: A Threat to npm Ecosystem
Summary
MAL-2025-168612: Malicious code in tealove-okta34 (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-okta34 is part of a broader campaign associated with the tea.xyz token reward initiative. This npm package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores in exchange for tea protocol token rewards. The package's functionality is compromised by malicious scripts that manipulate its metadata and behavior.
Vulnerability Detail
The vulnerability in tealove-okta34 stems from the presence of malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of these variants, polluting the npm registry and potentially compromising the integrity of other packages. The malicious payload is part of a larger scheme to exploit the npm ecosystem for token rewards, posing risks to developers and users relying on npm packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-okta34If 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-okta34 package and any packages that depend on it. Additionally, consider using a tool like Vulert to monitor your project 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-okta34 package poses a significant threat due to its malicious code that alters package metadata and floods the npm registry with compromised packages. It is crucial for developers to uninstall this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for tealove-okta34 →
FAQ
Tealove-okta34 is an npm package associated with a token reward campaign that has been found to contain malicious code.
The malicious code modifies your package.json file, removes private flags, and generates random package names, which can lead to pollution of the npm registry and compromise your project's integrity.
You should uninstall the package immediately using the command npm uninstall tealove-okta34 and check for any dependencies that may rely on it.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities without requiring any signup.
