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

tealove-darknest46 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168304: Malicious code in tealove-darknest46 (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

tealove-darknest46 is an npm package that is part of the tea.xyz token reward campaign. This package is designed to interact with the npm ecosystem, primarily for developers looking to enhance their reputation through token rewards. However, it has been identified as malicious, containing scripts that manipulate package metadata and flood the npm registry with derivative packages.

Vulnerability Detail

The vulnerability in tealove-darknest46 originates from its inclusion in a campaign that aims to inflate developer reputation scores by automatically generating and publishing numerous derivative packages. The malicious payload alters the package.json file by removing private flags, changing version numbers, and creating random package names, which leads to pollution of the npm registry. This can result in developers unknowingly using compromised packages, potentially exposing their applications to further security risks.

How To Fix

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

npm uninstall tealove-darknest46

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

Currently, there are no specific workarounds to mitigate the effects of this vulnerability other than removing the affected package from your project. Regularly audit your dependencies to ensure no malicious packages are included.

Conclusion

The tealove-darknest46 package poses a significant threat due to its malicious code designed to manipulate npm package metadata. It is crucial for developers to remove this package and monitor their dependencies to safeguard their applications from potential security risks.

See every vulnerability recorded for tealove-darknest46 →

Share this vulnerability

FAQ

tealove-darknest46 is an npm package that has been identified as malicious, designed to manipulate package metadata and flood the npm registry.

The vulnerability can lead to the inclusion of compromised packages in your application, potentially exposing it to security risks and instability.

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

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities using the Vulert playground without any signup.

Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and stay updated on known vulnerabilities in the packages you use.

How To Fix

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

npm uninstall tealove-darknest46

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