Malicious Code Injection in working_muskox_z3n Package
Summary
MAL-2025-97406: Malicious code in working_muskox_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
The working_muskox_z3n package is part of the npm ecosystem, often utilized in various JavaScript applications. It is associated with the tea.xyz token reward campaign, which has been known to flood the npm registry with packages that have dubious intentions. This package, like others in the campaign, is designed to manipulate npm's publishing system, potentially compromising the integrity of applications that depend on it.
Vulnerability Detail
The vulnerability stems from malicious code embedded within the working_muskox_z3n package. This code is designed to modify the package.json file by removing private flags, altering version numbers, and generating random package names. The primary goal is to inflate developer reputation scores for token rewards by continuously republishing these variants, which can lead to pollution of the npm registry and potential 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 working_muskox_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 workaround, you can prevent the installation of the working_muskox_z3n package by using npm's package-lock.json file to monitor dependencies. You can also utilize the Vulert platform to check if your application is affected by this vulnerability. Visit https://vulert.com/scanner to use the Vulert playground without any signup.
Conclusion
The working_muskox_z3n package poses a significant risk due to its malicious code that alters package configurations and republishing behavior. It is essential for developers to remove this package and monitor their dependencies to maintain application security.
See every vulnerability recorded for working_muskox_z3n →
FAQ
The working_muskox_z3n package is part of a campaign that floods npm with malicious packages aimed at manipulating developer reputation scores.
The malicious code can alter your package.json file, remove private flags, and republish variants, potentially compromising your application's integrity.
You should uninstall the working_muskox_z3n package immediately and check for any dependencies that may rely on it.
You can use Vulert, which monitors your package-lock.json file to alert you in real-time for open-source vulnerabilities.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
