Malicious Code Injection in Grateful Bedbug Z3N Package: npm Vulnerability

grateful_bedbug_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-103349: Malicious code in grateful_bedbug_z3n (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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

The 'grateful_bedbug_z3n' package is part of the npm ecosystem, which is widely used for JavaScript package management. This package is associated with the tea.xyz token reward campaign, which has been known to flood npm with malicious packages. These packages often contain scripts designed to manipulate the npm registry and inflate developer reputation scores through the automatic generation of derivative packages.

Vulnerability Detail

The vulnerability in the 'grateful_bedbug_z3n' package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes variants to pollute the npm registry. This can lead to reputational damage for developers and potential security risks for applications relying on these packages.

How To Fix

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

npm uninstall grateful_bedbug_z3n

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 'grateful_bedbug_z3n' package altogether. If it is already included in your project, remove it by running: npm uninstall grateful_bedbug_z3n.

Conclusion

The 'grateful_bedbug_z3n' package poses significant risks due to its malicious nature. It is essential to remove this package from your projects and stay vigilant about the dependencies you use. Utilizing tools like Vulert can help you monitor and manage vulnerabilities effectively.

See every vulnerability recorded for grateful_bedbug_z3n →

Share this vulnerability

FAQ

It is an npm package that is part of a malicious campaign aimed at manipulating the npm registry.

It can lead to security risks and reputational damage due to the pollution of the npm registry with malicious packages.

You should uninstall the package immediately and monitor your application for any unusual behavior.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json.

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities without any signup.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

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

npm uninstall grateful_bedbug_z3n

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