Malicious Code Injection in joyous_shark_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-95149: Malicious code in joyous_shark_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
Background
The package joyous_shark_z3n is part of a series of npm packages that emerged during the tea.xyz token reward campaign. These packages are designed to manipulate the npm registry by automatically generating and publishing derivative packages with randomized names. The malicious nature of joyous_shark_z3n lies in its ability to alter package metadata, which can significantly impact developers' reputations and the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in joyous_shark_z3n originates from its inclusion in a malicious campaign aimed at inflating developer reputation scores for token rewards. The package contains scripts that modify the package.json file to remove private flags, change version numbers, and generate random package names. This behavior leads to the continuous republishing of variants, polluting the npm registry and potentially compromising the security of dependent projects.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall joyous_shark_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, you can prevent the installation of joyous_shark_z3n by using npm's package-lock.json to monitor your dependencies. If joyous_shark_z3n is already installed, you can remove it with the command: npm uninstall joyous_shark_z3n.
Conclusion
The joyous_shark_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior aimed at manipulating package metadata. It is crucial for developers to remain vigilant, remove any affected packages, and utilize monitoring tools like Vulert to safeguard their projects.
See every vulnerability recorded for joyous_shark_z3n →
FAQ
joyous_shark_z3n is an npm package that is part of a malicious campaign to manipulate the npm registry and inflate developer reputation scores.
The vulnerability can lead to the pollution of the npm registry, potentially compromising the integrity of your project's dependencies and affecting your reputation as a developer.
You should uninstall the package immediately using the command: npm uninstall joyous_shark_z3n and monitor your dependencies for any further malicious packages.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities in your software using just package-lock.json. You can also check if your application is affected by this vulnerability using the Vulert playground.
Regularly audit your dependencies, keep them updated, and utilize tools like Vulert to monitor for vulnerabilities in real-time.
