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

tealove-nokire40 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168569: Malicious code in tealove-nokire40 (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-nokire40 is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses a significant risk to the integrity of the npm registry and the security of applications relying on these packages.

Vulnerability Detail

The vulnerability in tealove-nokire40 originates from its malicious payload, which modifies the package.json file by removing private flags and changing version numbers. It generates random Indonesian-themed package names and continuously republishes variants, leading to pollution of the npm registry. This can result in compromised applications, as developers may inadvertently use these malicious packages, exposing their projects to security risks.

How To Fix

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

npm uninstall tealove-nokire40

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-nokire40 package altogether until a secure version is released. Additionally, you can use the following command to audit your npm packages for vulnerabilities: npm audit.

Conclusion

The tealove-nokire40 package poses a significant security risk due to its malicious code that alters package configurations and publishes harmful variants. It is crucial for developers to remain vigilant, update their dependencies, and utilize tools like Vulert to monitor for vulnerabilities in their applications.

See every vulnerability recorded for tealove-nokire40 →

Share this vulnerability

FAQ

Tealove-nokire40 is an npm package that is part of a token reward campaign, which has been found to contain malicious code.

The vulnerability can lead to the installation of malicious packages, potentially compromising your application's security and integrity.

You should immediately remove the package and update your dependencies to ensure that your application is not using any compromised code.

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

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

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