Malicious Code Vulnerability in tealove-okta48: Exploitation of npm Packages

tealove-okta48 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168627: Malicious code in tealove-okta48 (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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package tealove-okta48 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to facilitate the automatic generation and publication of derivative npm packages. This package, like others in the campaign, aims to inflate developer reputation scores through the creation of numerous variants with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in tealove-okta48 arises from its malicious payload, which modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior is part of a strategy to automatically publish numerous derivative packages, thereby compromising the integrity of the npm registry and potentially leading to the distribution of harmful code. The origin of this vulnerability is linked to the tea.xyz token reward campaign, which exploits npm's publishing mechanisms.

How To Fix

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

npm uninstall tealove-okta48

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 workaround, you can avoid using the tealove-okta48 package and replace it with a secure alternative. Additionally, regularly audit your npm packages using the command npm audit to identify and address vulnerabilities.

Conclusion

The tealove-okta48 package poses a significant risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial to remove this package from your projects and monitor your dependencies for vulnerabilities to maintain the security and integrity of your applications.

See every vulnerability recorded for tealove-okta48 →

Share this vulnerability

FAQ

Tealove-okta48 is an npm package that is part of a malicious campaign designed to inflate developer reputation scores through the automatic generation of derivative packages.

The vulnerability can lead to the pollution of the npm registry, potentially allowing harmful code to be distributed and executed in your project.

You should uninstall the package immediately using npm uninstall tealove-okta48 and audit your project for any other vulnerabilities.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time 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 requiring any signup.

How To Fix

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

npm uninstall tealove-okta48

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