Malicious Code Vulnerability in hon_newt_z3n Package

hon_newt_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94851: Malicious code in hon_newt_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 hon_newt_z3n package is part of the npm ecosystem, typically used for various JavaScript applications. It is often involved in token reward campaigns, which can lead to the proliferation of malicious packages. This particular package has been identified as part of a larger scheme to manipulate the npm registry by generating and publishing numerous derivative packages with altered metadata.

Vulnerability Detail

The vulnerability originates from the package being part of a malicious campaign that floods the npm registry with derivative packages. The malicious code modifies the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior can lead to reputation inflation for developers and pollution of the npm registry, potentially causing security risks for applications relying on these packages.

How To Fix

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

npm uninstall hon_newt_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 avoid using the hon_newt_z3n package altogether. If it is already in use, consider replacing it with a more reputable package that serves a similar purpose. Additionally, you can use the following command to uninstall the package: npm uninstall hon_newt_z3n.

Conclusion

The hon_newt_z3n package has been identified as a malicious package that modifies critical files and can lead to security risks. It is crucial to remove this package from your project and monitor for any updates or alternatives. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for hon_newt_z3n →

Share this vulnerability

FAQ

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

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

You should remove the hon_newt_z3n package from your project and replace it with a more secure alternative.

Currently, there is no specific patch for the hon_newt_z3n package. It is advisable to remove it from your project.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can also check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

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