Malicious Code Injection in itchy_bear_z3n Package

itchy_bear_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-95125: Malicious code in itchy_bear_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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The itchy_bear_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package, like many others, is intended to facilitate various functionalities in applications. However, it has been identified as part of a malicious campaign that aims to exploit npm's publishing system, leading to potential security risks for developers and users alike.

Vulnerability Detail

The vulnerability originates from the package being associated with a token reward campaign that floods the npm registry with malicious packages. It contains scripts designed to automatically generate and publish derivative packages with randomized names, which can inflate developer reputation scores. The malicious payload modifies the package.json file to remove private flags, alters version numbers, and continuously republishes variants, polluting the npm registry and potentially leading to the installation of compromised packages by unsuspecting developers.

How To Fix

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

npm uninstall itchy_bear_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 itchy_bear_z3n package and look for alternative packages that provide similar functionality without the associated risks. Always verify the integrity and reputation of packages before including them in your project.

Conclusion

The itchy_bear_z3n package poses significant security risks due to its malicious code designed to exploit the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain application integrity and security.

See every vulnerability recorded for itchy_bear_z3n →

Share this vulnerability

FAQ

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

The vulnerability can lead to the installation of compromised packages, which may introduce security risks and affect the integrity of your application.

You should uninstall the itchy_bear_z3n package immediately and look for secure alternatives.

You can use tools like Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

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