Malicious Code Injection in neutral_fox_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-106279: Malicious code in neutral_fox_z3n (npm). Affected versions are not published. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
neutral_fox_z3n is an npm package that has been identified as part of a malicious campaign targeting the npm registry. This package is associated with the tea.xyz token reward initiative, which aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. The malicious nature of this package compromises the integrity of the npm ecosystem by introducing harmful scripts and altering package metadata.
Vulnerability Detail
The vulnerability in neutral_fox_z3n stems from its inclusion in a broader malicious campaign that floods the npm registry with derivative packages. These packages contain scripts designed to modify the package.json file by removing private flags, changing version numbers, and generating random package names. This behavior not only pollutes the npm registry but also poses a risk to developers who may unknowingly install these compromised packages, leading to potential security breaches and loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall neutral_fox_z3nIf 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 neutral_fox_z3n package and monitor your project for any unauthorized changes. You can also use tools like Vulert to scan your package-lock.json file for vulnerabilities. To check if your application is affected, visit the Vulert playground at https://vulert.com/scanner.
Conclusion
The neutral_fox_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior of modifying package metadata and flooding the registry with compromised packages. It is crucial for developers to be vigilant, regularly audit their dependencies, and utilize tools like Vulert to safeguard their projects from such vulnerabilities.
See every vulnerability recorded for neutral_fox_z3n →
FAQ
neutral_fox_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores through the automatic generation of derivative packages.
The vulnerability can lead to unauthorized modifications in your project's package.json file, potentially compromising the security and integrity of your application.
You should uninstall the package immediately using the command npm uninstall neutral_fox_z3n and review your project for any unauthorized changes.
Regularly audit your dependencies, use trusted packages, and utilize tools like Vulert to monitor your project for vulnerabilities.
Vulert is a tool that monitors and alerts for open-source vulnerabilities in your software by analyzing your package-lock.json file. You can check for vulnerabilities in your application without any signup at the Vulert playground.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
