Malicious Code Injection in eligible_newt_z3n Package

eligible_newt_z3n Updated 27 Nov 2025

Summary

11/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-94225: Malicious code in eligible_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 Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The eligible_newt_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate token rewards by generating and publishing derivative packages with randomized names. However, it has been identified as malicious due to its functionality that compromises the integrity of the npm registry.

Vulnerability Detail

The vulnerability originates from the package's malicious code that modifies the package.json file by removing private flags, altering version numbers, and generating random package names. This behavior leads to the automatic generation and publication of numerous derivative packages, which can inflate developer reputation scores fraudulently. The continuous republishing of these variants pollutes the npm registry, potentially affecting other developers and users relying on legitimate packages.

How To Fix

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

npm uninstall eligible_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 temporary workaround, you can prevent the installation of the eligible_newt_z3n package by using the following command: npm uninstall eligible_newt_z3n. Additionally, you can monitor your project for vulnerabilities using Vulert, which utilizes package-lock.json to alert you in real-time for open-source vulnerabilities.

Conclusion

The eligible_newt_z3n package has been identified as a source of malicious code that compromises the npm registry. It is crucial for developers to take immediate action by updating or removing the package and utilizing tools like Vulert to monitor for vulnerabilities in their projects.

See every vulnerability recorded for eligible_newt_z3n →

Share this vulnerability

FAQ

The eligible_newt_z3n package is part of a token reward campaign in the npm ecosystem, designed to generate and publish derivative packages.

The vulnerability can lead to the pollution of the npm registry and may compromise the integrity of your project's dependencies.

You should uninstall the eligible_newt_z3n package and monitor your project for vulnerabilities using tools like Vulert.

Yes, you can use Vulert to monitor your project for open-source vulnerabilities by simply using your package-lock.json file.

You can check if your application is affected by this vulnerability using the Vulert playground at Vulert Scanner without any signup.

How To Fix

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

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