Malicious Code Injection in tealove-nokire47 Package

tealove-nokire47 Updated 26 Nov 2025

Summary

12/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-168576: Malicious code in tealove-nokire47 (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 tealove-nokire47 package is part of the tea.xyz token reward campaign, which has been known to flood the npm registry with various packages. These packages often include scripts designed to manipulate package metadata and inflate developer reputation scores for token rewards. The primary functionality of these packages is to generate and publish derivative packages with randomized names, which can lead to significant pollution of the npm registry.

Vulnerability Detail

The vulnerability in the tealove-nokire47 package stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, primarily themed around Indonesian culture. This behavior not only compromises the integrity of the npm registry but also poses risks to developers who may unknowingly use these tainted packages. The origin of this issue is linked to the tea.xyz token reward campaign, which incentivizes the creation of such malicious packages.

How To Fix

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

npm uninstall tealove-nokire47

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-nokire47 package and any other packages that are part of the tea.xyz token reward campaign. Regularly audit your project's dependencies to ensure that no malicious packages are included.

Conclusion

The tealove-nokire47 package poses a significant risk due to its malicious code that alters package metadata and pollutes the npm registry. It is crucial for developers to be vigilant about their dependencies and to utilize tools like Vulert for real-time monitoring of vulnerabilities. Always ensure to remove any affected packages and keep your project dependencies updated.

See every vulnerability recorded for tealove-nokire47 →

Share this vulnerability

FAQ

The tealove-nokire47 package is part of a campaign that floods the npm registry with malicious packages designed to inflate developer reputation scores for token rewards.

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

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.

If you have installed the tealove-nokire47 package, it is recommended to uninstall it immediately using the command npm uninstall tealove-nokire47.

Currently, there are no patches available for the tealove-nokire47 package, so the best course of action is to remove it from your project.

How To Fix

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

npm uninstall tealove-nokire47

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