Malicious Code Injection in tealove-okta35: A Threat to npm Ecosystem
Summary
MAL-2025-168613: Malicious code in tealove-okta35 (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-okta35 is part of a broader campaign targeting the npm ecosystem, specifically designed to exploit the tea.xyz token reward system. This package, like others in the campaign, is intended to generate and publish derivative packages with randomized names, thereby inflating developer reputation scores for token rewards. Its functionality is compromised by malicious scripts that manipulate package metadata.
Vulnerability Detail
The vulnerability in tealove-okta35 originates from its inclusion in a malicious campaign that floods the npm registry with derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to pollution of the npm registry, potentially affecting developers who rely on the integrity of packages for their applications. The scripts involved are designed to continuously republish variants, exacerbating the issue.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-okta35If 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 tealove-okta35 and any packages that may have been published as derivatives. Monitor your package-lock.json file for any unauthorized changes and consider using tools like Vulert to track vulnerabilities in your dependencies.
Conclusion
The tealove-okta35 package poses a significant threat to the npm ecosystem due to its malicious code injection capabilities. It is crucial for developers to be aware of such vulnerabilities and take proactive measures to secure their applications. Regular monitoring and updating of dependencies are essential practices to maintain software integrity.
See every vulnerability recorded for tealove-okta35 →
FAQ
Tealove-okta35 is an npm package that is part of a malicious campaign aimed at exploiting the npm ecosystem for token rewards.
The vulnerability can lead to the inclusion of malicious code in your application, potentially compromising its security and integrity.
You should uninstall the package immediately using the command 'npm uninstall tealove-okta35' and check your project for any unauthorized changes.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
