Malicious Code Injection in tealove-darknest22: A Threat to npm Ecosystem

tealove-darknest22 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168278: Malicious code in tealove-darknest22 (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-darknest22 is part of a broader campaign associated with the tea.xyz token reward system. It is designed to manipulate the npm registry by generating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making it a significant concern for developers relying on npm for package management.

Vulnerability Detail

The vulnerability in tealove-darknest22 originates from its malicious design, which includes autopublish scripts that modify the package.json file. These modifications remove private flags, alter version numbers, and create random package names, leading to the continuous republishing of variants. This not only pollutes the npm registry but also poses a risk of unintentional dependency on malicious packages by developers, potentially compromising their applications.

How To Fix

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

npm uninstall tealove-darknest22

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 tealove-darknest22 and any packages that depend on it. Regularly audit your dependencies using 'npm audit' to identify any vulnerabilities in your project.

Conclusion

The tealove-darknest22 package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and republishing variants. It is essential for developers to take immediate action to remove this package and monitor their dependencies to safeguard their applications.

See every vulnerability recorded for tealove-darknest22 →

Share this vulnerability

FAQ

tealove-darknest22 is an npm package involved in a malicious campaign to inflate developer reputation scores through the publication of numerous derivative packages.

The vulnerability can lead to unintentional dependency on malicious packages, which may compromise the security and integrity of your application.

You should uninstall the package immediately and check your package-lock.json for any references to it. Use 'npm uninstall tealove-darknest22' to remove it.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using your package-lock.json. You can check your application for vulnerabilities without signup at the Vulert playground.

Regularly audit your dependencies, keep your packages updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.

How To Fix

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

npm uninstall tealove-darknest22

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