Malicious Code Injection in tealove-okta46 Package: A Threat to npm Users

tealove-okta46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168625: Malicious code in tealove-okta46 (npm). Affected versions are not published. No fix is published. How to fix ↓

Free scan

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.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The tealove-okta46 package is part of the tea.xyz token reward campaign, which has been known to flood the npm ecosystem with malicious packages. These packages are designed to inflate developer reputation scores through the automatic generation and publication of derivative packages. The core functionality of tealove-okta46 is compromised, as it contains scripts that manipulate package metadata and republish variants to pollute the npm registry.

Vulnerability Detail

The vulnerability in the tealove-okta46 package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants. This behavior not only compromises the integrity of the npm registry but also poses a risk to developers who may unknowingly install these malicious packages, leading to potential security breaches in their applications.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tealove-okta46

If 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, avoid using the tealove-okta46 package and monitor your project's dependencies for any malicious packages. You can also utilize tools like Vulert to scan your package-lock.json file for vulnerabilities. For real-time monitoring, visit the Vulert playground at https://vulert.com/scanner, where you can check if your application is affected by this vulnerability without needing to sign up.

Conclusion

The tealove-okta46 package poses a significant risk due to its malicious code designed to manipulate npm package metadata. Developers should take immediate action to remove this package and monitor their dependencies for any similar threats. Utilizing tools like Vulert can aid in maintaining the security of your applications.

See every vulnerability recorded for tealove-okta46 →

Share this vulnerability

FAQ

Tealove-okta46 is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the installation of malicious code that modifies your package.json file, potentially compromising your application's security and integrity.

You should immediately uninstall the package using 'npm uninstall tealove-okta46' and check for any other malicious packages in your dependencies.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without signing up.

Regularly audit your dependencies, keep your packages updated, and utilize vulnerability scanning tools to catch potential threats early.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall tealove-okta46

If 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 →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback