Malicious Code Injection in tealove-okta37: A Threat to npm Packages
Summary
MAL-2025-168615: Malicious code in tealove-okta37 (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-okta37 is part of a broader campaign involving the tea.xyz token reward system, 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 derivative packages with randomized names. The primary function of tealove-okta37 is to serve as a vehicle for these malicious activities, compromising the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove-okta37 arises from its inclusion in a malicious campaign that employs scripts to alter package.json files. This manipulation removes private flags, modifies version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include potential pollution of the npm registry, increased risk of dependency confusion, and exploitation of developer reputation systems. The malicious payload is designed to operate stealthily, making it difficult for developers to detect the underlying threat.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-okta37If 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 measure, you can avoid using the tealove-okta37 package and any other packages associated with the tea.xyz token reward campaign. If you need to use similar functionality, consider finding alternative packages that are well-reviewed and maintained.
Conclusion
The tealove-okta37 package poses a significant threat due to its malicious code designed to manipulate npm package integrity. It is crucial for developers to remain vigilant, regularly update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities. By taking proactive measures, you can protect your projects from potential exploitation.
See every vulnerability recorded for tealove-okta37 →
FAQ
Tealove-okta37 is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, increased risk of dependency confusion, and potential exploitation of your project's reputation if the malicious packages are inadvertently used.
You should uninstall the package immediately using the command npm uninstall tealove-okta37 and review your project's dependencies for any other potentially malicious packages.
You can use tools like Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities. You can also check your application against known vulnerabilities using the Vulert playground at Vulert Scanner.
Yes, look for well-reviewed and actively maintained packages that provide similar functionality without the associated risks of malicious code.
