Malicious Code Injection in genhih-devapptea: A Threat to npm Packages

genhih-devapptea Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103091: Malicious code in genhih-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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The package 'genhih-devapptea' is part of the tea.xyz token reward campaign that has infiltrated the npm ecosystem. It is designed to automate the generation and publication of derivative packages, often with randomized names, to inflate developer reputation scores for token rewards. This behavior poses significant risks to developers and users relying on npm packages.

Vulnerability Detail

The vulnerability in 'genhih-devapptea' originates from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, often themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This not only compromises the integrity of the npm ecosystem but also exposes developers to potential security risks and reputation damage.

How To Fix

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

npm uninstall genhih-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 measure, avoid using the 'genhih-devapptea' package and monitor your project for any dependencies that may have been affected by this malicious code. You can also use tools like Vulert to monitor your package-lock.json for vulnerabilities.

Conclusion

The 'genhih-devapptea' package poses a significant threat to the npm ecosystem due to its malicious code that modifies package files and republishes harmful variants. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain security and integrity.

See every vulnerability recorded for genhih-devapptea →

Share this vulnerability

FAQ

'genhih-devapptea' is an npm package involved in a token reward campaign that automates the creation and publication of derivative packages.

The malicious code can compromise your project's integrity by modifying package.json files and introducing potentially harmful packages into your environment.

You should uninstall the package immediately using 'npm uninstall genhih-devapptea' and check for any other affected packages.

Yes, you can use Vulert to monitor your package-lock.json for open-source vulnerabilities in real-time without needing to install any software.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

How To Fix

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

npm uninstall genhih-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