Malicious Code Injection in peaceful_bug_z3n Package

peaceful_bug_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95869: Malicious code in peaceful_bug_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 peaceful_bug_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, often with randomized names. It aims to inflate developer reputation scores for token rewards, making it a target for malicious actors looking to exploit npm's package management system.

Vulnerability Detail

The vulnerability in the peaceful_bug_z3n package stems from its malicious code, which modifies the package.json file to remove private flags and alters version numbers. It generates random package names, primarily themed around Indonesian culture, and continuously republishes these variants to pollute the npm registry. This behavior can lead to a significant compromise of the npm ecosystem, affecting developers who rely on the integrity of packages for their applications.

How To Fix

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

npm uninstall peaceful_bug_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 peaceful_bug_z3n package and any packages that depend on it. Monitor your package-lock.json file for any unexpected changes or additions that may indicate the presence of malicious packages.

Conclusion

The peaceful_bug_z3n package poses a significant risk due to its malicious code that alters package metadata and repopulates the npm registry with potentially harmful variants. It is essential to remove this package and monitor your dependencies regularly to maintain the security of your applications.

See every vulnerability recorded for peaceful_bug_z3n →

Share this vulnerability

FAQ

The peaceful_bug_z3n package is an npm package associated with a token reward campaign that generates and publishes derivative packages to inflate developer reputation scores.

The vulnerability can compromise the integrity of your application by introducing malicious code that modifies your package.json file and republishing variants that could lead to further exploitation.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By using the Vulert playground, you can check if your application is affected without any signup.

If you have installed the peaceful_bug_z3n package, you should uninstall it immediately using 'npm uninstall peaceful_bug_z3n' and review your other dependencies for any potential vulnerabilities.

Yes, tools like Vulert can help monitor your project's dependencies for vulnerabilities by analyzing your package-lock.json file.

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 peaceful_bug_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