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

tealove-nokire38 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168566: Malicious code in tealove-nokire38 (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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

tealove-nokire38 is a package within the npm ecosystem, associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards for developers by generating and publishing derivative packages. However, it has been identified as containing malicious scripts that compromise the integrity of the npm registry.

Vulnerability Detail

The vulnerability in tealove-nokire38 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 leads to the automatic generation and publication of numerous derivative packages, which can inflate developer reputation scores fraudulently. The continuous republishing of these variants pollutes the npm registry, posing a significant risk to developers relying on the integrity of npm packages.

How To Fix

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

npm uninstall tealove-nokire38

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-nokire38 package from your project to prevent any potential exploitation. Use the following command: npm uninstall tealove-nokire38. Additionally, consider using Vulert to monitor your project for vulnerabilities by checking your package-lock.json file.

Conclusion

The tealove-nokire38 package poses a significant risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial to take immediate action by updating or removing the package and utilizing monitoring tools like Vulert to safeguard your projects.

See every vulnerability recorded for tealove-nokire38 →

Share this vulnerability

FAQ

tealove-nokire38 is an npm package associated with the tea.xyz token reward campaign, designed to generate and publish derivative packages.

The vulnerability can lead to the pollution of the npm registry and compromise the integrity of your project's dependencies, potentially introducing malicious code.

You should uninstall the package immediately and monitor your project for any vulnerabilities using tools like Vulert.

Yes, you can use Vulert's playground to check if your application is affected by this vulnerability without any signup required.

Regularly update your dependencies, monitor your project with tools like Vulert, and review package sources before installation.

How To Fix

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

npm uninstall tealove-nokire38

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