Malicious Code Injection in changing_whitefish_z3n Package
Summary
MAL-2025-100330: Malicious code in changing_whitefish_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 changing_whitefish_z3n package is part of the npm ecosystem and is associated with the tea.xyz token reward campaign. This package is designed to facilitate the automatic generation and publication of derivative packages, which can inflate developer reputation scores for token rewards. However, it has been identified as containing malicious code that compromises its integrity and security.
Vulnerability Detail
The vulnerability originates from the malicious payload embedded within the changing_whitefish_z3n package. This payload modifies the package.json file by removing private flags, altering version numbers, and generating random package names. It continuously republishes these variants, leading to pollution of the npm registry and potential exploitation by malicious actors. The ramifications include unauthorized access to sensitive data, reputation damage for developers, and increased risk of dependency confusion attacks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall changing_whitefish_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 avoid using the changing_whitefish_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, ensure that your package-lock.json file is monitored for any unauthorized changes.
Conclusion
The changing_whitefish_z3n package poses a significant security risk due to its embedded malicious code. It is crucial for developers to remove this package and monitor their projects for vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.
See every vulnerability recorded for changing_whitefish_z3n →
FAQ
It is an npm package associated with the tea.xyz token reward campaign, designed to automate the publication of derivative packages.
The malicious code modifies your package.json file and can lead to unauthorized republishing of packages, potentially compromising your project's security.
You should uninstall the changing_whitefish_z3n package immediately and monitor your project for any unauthorized changes.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can check your application using the Vulert playground without any signup.
Using compromised packages can lead to security breaches, data leaks, and damage to your reputation as a developer, as well as potential legal ramifications.