Malicious Code Injection in puzzled_bovid_z3n Package - npm Vulnerability

puzzled_bovid_z3n Updated 18 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-107558: Malicious code in puzzled_bovid_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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The puzzled_bovid_z3n package is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by creating and publishing numerous derivative packages with randomized names. This behavior is intended to inflate developer reputation scores for token rewards, making the package susceptible to malicious exploitation.

Vulnerability Detail

The vulnerability in the puzzled_bovid_z3n package stems from its inclusion in a malicious campaign that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. This leads to the continuous republishing of variants, which pollutes the npm registry and can compromise the integrity of other packages. The malicious payload can potentially allow attackers to execute unauthorized code or manipulate the package ecosystem.

How To Fix

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

npm uninstall puzzled_bovid_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 remove the puzzled_bovid_z3n package from your project by executing the command: 'npm uninstall puzzled_bovid_z3n'. This will prevent any malicious code from executing until a secure version is available.

Conclusion

The puzzled_bovid_z3n package poses a significant risk due to its involvement in a malicious campaign that alters package data and pollutes the npm registry. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications.

See every vulnerability recorded for puzzled_bovid_z3n →

Share this vulnerability

FAQ

The puzzled_bovid_z3n package is an npm package that is part of a malicious campaign aimed at inflating developer reputation scores through the creation of numerous derivative packages.

The vulnerability can lead to unauthorized code execution, manipulation of package data, and pollution of the npm registry, potentially affecting the integrity of your application.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected by this vulnerability without needing to sign up.

If you are using the puzzled_bovid_z3n package, you should uninstall it immediately and check for any updates or patches that may be released to address the vulnerability.

To prevent similar vulnerabilities, regularly audit your dependencies, use tools like Vulert for monitoring, and ensure you only use trusted packages from reputable sources.

How To Fix

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

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