Malicious Code Injection in tealove-okta40: A Threat to npm Packages
Summary
MAL-2025-168619: Malicious code in tealove-okta40 (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-okta40 is part of a broader campaign associated with the tea.xyz token reward initiative, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to manipulate developer reputation scores by automatically generating and publishing numerous derivative packages with randomized names. This behavior not only clutters the npm registry but also poses a significant risk to developers who may unknowingly integrate these compromised packages into their projects.
Vulnerability Detail
The vulnerability in tealove-okta40 originates from its inclusion in the tea.xyz token reward campaign. It features malicious scripts that modify the package.json file by removing private flags, altering version numbers, and generating random package names. This results in the continuous republishing of these variants, which can lead to pollution of the npm registry and potential exploitation by malicious actors. The ramifications include compromised developer environments and the risk of integrating untrusted code into applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-okta40If 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-okta40 package and replace it with an alternative package that provides similar functionality without the associated risks. Additionally, regularly audit your npm packages using tools like npm audit to identify and mitigate vulnerabilities.
Conclusion
The tealove-okta40 package poses a significant risk due to its malicious behavior aimed at manipulating npm package reputation scores. It is essential for developers to remove this package from their projects and monitor their dependencies for vulnerabilities to maintain a secure development environment.
See every vulnerability recorded for tealove-okta40 →
FAQ
tealove-okta40 is an npm package that is part of a malicious campaign aimed at manipulating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the integration of untrusted code into your project, potentially compromising security and functionality.
You should uninstall the package immediately using 'npm uninstall tealove-okta40' and consider using an alternative package.
You can use tools like npm audit or services 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 if your application is affected by this vulnerability without requiring any signup.
