Malicious Code Injection in tealove-okta1: A Threat to npm Packages

tealove-okta1 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168585: Malicious code in tealove-okta1 (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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The package 'tealove-okta1' is part of a campaign associated with the tea.xyz token reward system, which has been known to flood the npm registry with malicious packages. These packages are designed to inflate developer reputation scores through automated publishing scripts. The functionality of 'tealove-okta1' is compromised due to its malicious intent, posing a significant risk to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in 'tealove-okta1' originates from its inclusion in a broader malicious campaign that utilizes autopublish scripts to generate and publish derivative packages with randomized names. This malicious payload modifies the package.json file by removing private flags, altering version numbers, and continuously republishing variants, thereby polluting the npm registry. The ramifications include potential security risks for applications using this package, as it can lead to unauthorized access or data manipulation.

How To Fix

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

npm uninstall tealove-okta1

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 'tealove-okta1' and consider using alternative packages that provide similar functionality without the associated risks. Always validate the source and integrity of packages before integrating them into your projects.

Conclusion

The 'tealove-okta1' package poses a significant threat due to its malicious code designed to manipulate npm packages. It is crucial for developers to remove this package and monitor their dependencies for vulnerabilities to ensure the security of their applications.

See every vulnerability recorded for tealove-okta1 →

Share this vulnerability

FAQ

'tealove-okta1' is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through automated publishing.

The vulnerability can lead to unauthorized modifications in your application, potentially exposing it to security risks and data breaches.

You should uninstall 'tealove-okta1' immediately using 'npm uninstall tealove-okta1' and check your project for any other compromised packages.

You can use tools like Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall tealove-okta1

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