Malicious Code Injection in firm_bug_z3n Package - npm Vulnerability

firm_bug_z3n Updated 24 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-102736: Malicious code in firm_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 firm_bug_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 publishing numerous derivative packages with altered metadata. The primary functionality of this package is unclear due to its malicious intent, which undermines the integrity of the npm ecosystem.

Vulnerability Detail

The vulnerability in the firm_bug_z3n package stems from its association with a malicious campaign that modifies the package.json file to remove private flags and change version numbers. It generates random package names and continuously republishes these variants, leading to pollution of the npm registry. This behavior can inflate developer reputation scores fraudulently and potentially introduce security risks to applications relying on these packages.

How To Fix

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

npm uninstall firm_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 workaround, you can temporarily avoid using the firm_bug_z3n package and replace it with a trusted alternative. Additionally, you can use tools like Vulert to monitor your project for vulnerabilities. To check if your application is affected by this vulnerability, you can use the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The firm_bug_z3n package poses a significant security risk due to its malicious behavior aimed at manipulating the npm registry. It is crucial for developers to remove this package and monitor their applications for any vulnerabilities. Utilizing tools like Vulert can help maintain the security of your software.

See every vulnerability recorded for firm_bug_z3n →

Share this vulnerability

FAQ

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

This vulnerability can lead to the introduction of malicious code into your application, potentially compromising its security and integrity.

If you have installed the firm_bug_z3n package, you should uninstall it immediately and check your project for any other affected packages.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.

Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by vulnerabilities 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 firm_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