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

tealove-nokire4 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168568: Malicious code in tealove-nokire4 (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 package tealove-nokire4 is part of a broader campaign associated with the tea.xyz token reward initiative. This package is designed to manipulate the npm ecosystem by creating and publishing numerous derivative packages with randomized names. Its primary function is to inflate developer reputation scores for token rewards, but this leads to significant pollution of the npm registry and poses security risks to users.

Vulnerability Detail

The vulnerability in tealove-nokire4 stems from its malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior allows the package to continuously republish variants, which can lead to the proliferation of potentially harmful packages in the npm registry. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes such malicious practices to manipulate the npm ecosystem.

How To Fix

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

npm uninstall tealove-nokire4

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 remove the tealove-nokire4 package from your project by executing the command: npm uninstall tealove-nokire4. This will prevent any malicious activity associated with this package until a fix is implemented.

Conclusion

The tealove-nokire4 package poses a significant risk due to its malicious code that manipulates the npm registry. It is crucial for developers to be aware of this vulnerability, take immediate action to remove the package, and utilize tools like Vulert to monitor their projects for potential threats.

See every vulnerability recorded for tealove-nokire4 →

Share this vulnerability

FAQ

Tealove-nokire4 is an npm package associated with the tea.xyz token reward campaign, designed to manipulate the npm registry by publishing numerous derivative packages.

The vulnerability can lead to the pollution of the npm registry with malicious packages, potentially compromising the security and integrity of your project.

You should uninstall the package immediately and check for any other affected packages in your project.

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

Regularly update your packages to their latest versions, monitor for vulnerabilities using tools like Vulert, and review your dependencies for any known issues.

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-nokire4

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