Malicious Code Injection in like_bonobo_z3n Package - npm Vulnerability

like_bonobo_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-105129: Malicious code in like_bonobo_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 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 like_bonobo_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package has been identified as part of a malicious campaign that aims to exploit the npm registry by flooding it with derivative packages. The malicious nature of this package is linked to its role in the tea.xyz token reward scheme, which incentivizes developers to inflate their reputation scores through automated publishing scripts.

Vulnerability Detail

The vulnerability in the like_bonobo_z3n package stems from its inclusion in a malicious campaign that utilizes autopublish scripts to generate and publish numerous derivative packages with randomized names. These scripts modify the package.json file by removing private flags, altering version numbers, and creating random package names, which leads to pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses a risk to developers who may unknowingly use these malicious packages in their projects.

How To Fix

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

npm uninstall like_bonobo_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 measure, you can avoid using the like_bonobo_z3n package and any other packages associated with the tea.xyz token reward scheme. Regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities. You can use the following command to check your package-lock.json file for vulnerabilities: npm audit.

Conclusion

The like_bonobo_z3n package poses a significant risk due to its malicious nature and its role in a broader scheme to exploit the npm registry. It is crucial for developers to be vigilant and regularly audit their dependencies to ensure the security of their projects. Removing this package and utilizing tools like Vulert can help maintain a secure development environment.

See every vulnerability recorded for like_bonobo_z3n →

Share this vulnerability

FAQ

The like_bonobo_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.

If your project uses the like_bonobo_z3n package, it may inadvertently publish malicious derivatives and compromise the integrity of your application.

You should uninstall the like_bonobo_z3n package immediately and review your project's dependencies for any other potentially malicious packages.

You can use tools like Vulert, which monitors your package-lock.json file for vulnerabilities in real-time 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 any signup.

How To Fix

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

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