Malicious Code Injection in tealove-okta50: A Threat to npm Ecosystem
Summary
MAL-2025-168630: Malicious code in tealove-okta50 (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-okta50 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to generate and publish derivative packages with randomized names, which are used to inflate developer reputation scores for token rewards. This package, like others in the campaign, contains scripts that automatically modify and republish itself, posing a significant risk to the integrity of the npm registry.
Vulnerability Detail
The vulnerability in tealove-okta50 originates from its malicious code that modifies the package.json file by removing private flags and changing version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants, leading to pollution of the npm registry. This behavior can compromise the security of applications relying on this package, as it may introduce unverified and potentially harmful code into their dependencies.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-okta50If 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 tealove-okta50 and replace it with alternative packages that provide similar functionality without the associated risks. Additionally, consider using tools like Vulert to monitor your package-lock.json for vulnerabilities in real-time.
Conclusion
The tealove-okta50 package poses a significant risk due to its malicious code that modifies and republishes itself, potentially compromising the security of applications that depend on it. It is crucial to uninstall this package and monitor your dependencies for vulnerabilities using tools like Vulert.
See every vulnerability recorded for tealove-okta50 →
FAQ
Tealove-okta50 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing of derivative packages.
The vulnerability can lead to the introduction of unverified and potentially harmful code into your application, compromising its security and integrity.
You should uninstall the package immediately using 'npm uninstall tealove-okta50' and consider using alternative packages.
Yes, you can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without needing to access the code or install additional tools.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
