Malicious Code Injection in pleasant_bison_z3n: A Threat to npm Users

pleasant_bison_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95914: Malicious code in pleasant_bison_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

pleasant_bison_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package, like many others in the campaign, is designed to manipulate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm ecosystem, making it crucial for developers to be aware of its implications.

Vulnerability Detail

The vulnerability in pleasant_bison_z3n originates from its association with the tea.xyz token reward campaign. This package contains scripts that automatically modify the package.json file to remove private flags, alter version numbers, and generate random package names. The continuous republishing of these variants leads to pollution of the npm registry, potentially affecting other packages and developers relying on the integrity of the ecosystem. The malicious payload can also lead to unauthorized access and manipulation of projects that depend on this package.

How To Fix

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

npm uninstall pleasant_bison_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 prevent the installation of the malicious package by using npm's package-lock.json to monitor your dependencies. Ensure that you do not install any packages that are not explicitly listed in your package.json file. Additionally, consider using tools like Vulert to monitor for vulnerabilities in your dependencies.

Conclusion

The pleasant_bison_z3n package poses a significant threat to the npm ecosystem due to its malicious code designed to manipulate package integrity. Developers must take immediate action to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can aid in maintaining the security of your projects.

See every vulnerability recorded for pleasant_bison_z3n →

Share this vulnerability

FAQ

pleasant_bison_z3n is an npm package that has been identified as part of a malicious campaign aimed at manipulating developer reputation scores.

The vulnerability can lead to unauthorized modifications in your project's dependencies, potentially compromising the security and integrity of your application.

You should uninstall the package immediately using 'npm uninstall pleasant_bison_z3n' and check for any dependencies that may rely on it.

You can use tools like Vulert, which monitors your package-lock.json for open-source vulnerabilities in real-time, alerting you to any issues.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring 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 pleasant_bison_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