Malicious Code Injection in kiehtk-devapptea Package

kiehtk-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-104770: Malicious code in kiehtk-devapptea (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 kiehtk-devapptea package is part of the tea.xyz token reward campaign, which has been associated with a surge of malicious npm packages. These packages are designed to inflate developer reputation scores through the automatic generation and publishing of derivative packages. The malicious nature of this package lies in its ability to modify essential files and republish variants, affecting the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the inclusion of autopublish scripts within the kiehtk-devapptea package. These scripts are designed to automatically alter the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior leads to the pollution of the npm registry with numerous derivative packages, which can compromise the security and reliability of applications relying on this package. The malicious payload can also lead to unintended consequences for developers, such as reputation damage and potential security risks in their applications.

How To Fix

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

npm uninstall kiehtk-devapptea

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 kiehtk-devapptea package from your project to prevent any malicious activity. Use the following command to uninstall the package: npm uninstall kiehtk-devapptea. Additionally, consider using a tool like Vulert to monitor your project for vulnerabilities in real-time.

Conclusion

The kiehtk-devapptea package contains a significant vulnerability that allows for malicious code injection and the pollution of the npm registry. Developers should take immediate action to remove the package and monitor their applications for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your software.

See every vulnerability recorded for kiehtk-devapptea →

Share this vulnerability

FAQ

The kiehtk-devapptea package is part of a token reward campaign that has been associated with malicious activities in the npm ecosystem.

This vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity and security of your application.

If you have installed the kiehtk-devapptea package, it is advisable to uninstall it immediately and monitor your project for any vulnerabilities.

You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities without requiring code access or installation.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

How To Fix

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

npm uninstall kiehtk-devapptea

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