Malicious Code Injection in prepared_kiwi-apptea Package

prepared_kiwi-apptea Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107219: Malicious code in prepared_kiwi-apptea (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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The prepared_kiwi-apptea package is part of the npm ecosystem, primarily used for various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with numerous derivative packages. This package, like others in the campaign, has been designed to manipulate developer reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the prepared_kiwi-apptea package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This behavior leads to the continuous republishing of variants, which pollutes the npm registry and can potentially compromise the integrity of dependent applications. The malicious payload is executed through scripts that are automatically triggered, making it a significant threat to developers and users relying on this package.

How To Fix

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

npm uninstall prepared_kiwi-apptea

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, consider removing the prepared_kiwi-apptea package from your project if it is not essential. You can uninstall it using the command: npm uninstall prepared_kiwi-apptea. Additionally, monitor your package-lock.json file for any unexpected changes.

Conclusion

The prepared_kiwi-apptea package has been identified as containing malicious code that poses a significant risk to developers and applications using it. It is essential to take immediate action by updating or removing the package to safeguard your projects. Utilizing tools like Vulert can help in monitoring and managing open-source vulnerabilities effectively.

See every vulnerability recorded for prepared_kiwi-apptea →

Share this vulnerability

FAQ

The vulnerability involves malicious code that modifies package.json and repackages it under random names, affecting the integrity of the npm registry.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application against the vulnerability using the Vulert playground at Vulert Scanner.

Using this package can lead to security breaches, as it may introduce malicious code into your application, compromising its functionality and security.

Regularly audit your dependencies and use tools like Vulert to monitor for vulnerabilities. Always keep your packages updated to the latest secure versions.

If an immediate update is not possible, consider removing the package and replacing it with a safer alternative until a fix is available.

How To Fix

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

npm uninstall prepared_kiwi-apptea

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