Malicious Code Injection in tealove-okta7: A Threat to npm Users
Summary
MAL-2025-168632: Malicious code in tealove-okta7 (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The package tealove-okta7 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 derivative packages with randomized names. The primary functionality of tealove-okta7 is compromised due to its malicious payload, which alters package configurations to facilitate the spread of harmful variants.
Vulnerability Detail
The vulnerability in tealove-okta7 originates from its inclusion in a malicious campaign that employs scripts to modify the package.json file. This modification removes private flags, changes version numbers, and generates random package names, leading to the continuous republishing of these variants. The ramifications include the pollution of the npm registry, potential security risks for developers who unknowingly use these packages, and a significant impact on the integrity of the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall tealove-okta7If 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-okta7 package and look for alternative packages that provide 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-okta7 package poses a significant threat due to its malicious code that manipulates package configurations and pollutes the npm registry. It is essential for developers to remove this package and monitor their dependencies for vulnerabilities to maintain the integrity of their projects.
See every vulnerability recorded for tealove-okta7 →
FAQ
Tealove-okta7 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, potential security risks, and the introduction of malicious code into your project, which can compromise its integrity.
If you have installed tealove-okta7, you should uninstall it immediately using 'npm uninstall tealove-okta7' and check for any other affected dependencies.
You can use tools like npm audit to regularly check for vulnerabilities in your npm packages. Additionally, Vulert can monitor your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
