Malicious Code Injection in hon_badger_z3n: Exploiting npm for Token Rewards

hon_badger_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94848: Malicious code in hon_badger_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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The hon_badger_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a campaign that aims to exploit the npm registry by flooding it with malicious packages. These packages often contain scripts that automatically publish derivative versions to manipulate developer reputation scores for token rewards. The vulnerability stems from the package's design, which allows for the injection of malicious code that alters package metadata.

Vulnerability Detail

The vulnerability in hon_badger_z3n originates from its association with the tea.xyz token reward campaign. The malicious code modifies the package.json file to remove private flags, changes version numbers, and generates random package names, which leads to the pollution of the npm registry. This not only compromises the integrity of the npm ecosystem but also poses risks to developers who may unknowingly install these malicious packages, potentially leading to further exploitation or data breaches.

How To Fix

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

npm uninstall hon_badger_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, avoid using the hon_badger_z3n package and monitor your project's dependencies for any signs of malicious activity. Regularly audit your package-lock.json file to ensure no unauthorized packages are included.

Conclusion

The hon_badger_z3n package poses a significant risk due to its malicious code designed to exploit the npm registry. Developers should take immediate action to remove this package and monitor their projects for any signs of compromise. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for hon_badger_z3n →

Share this vulnerability

FAQ

hon_badger_z3n 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 malicious code that modifies your project's dependencies and can compromise your application's security.

You should immediately uninstall the package using npm uninstall hon_badger_z3n and audit your project for any other malicious dependencies.

You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time. You can check your application against known vulnerabilities using the Vulert playground.

Regularly audit your dependencies, use trusted sources for packages, and consider implementing automated tools that can alert you to vulnerabilities as they arise.

How To Fix

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

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