Malicious Code Injection in Rigid Duck Z3N Package: npm Vulnerability
Summary
MAL-2025-96368: Malicious code in rigid_duck_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 'rigid_duck_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. However, it has been compromised to include malicious scripts that can manipulate package metadata.
Vulnerability Detail
The vulnerability in the 'rigid_duck_z3n' package stems from its inclusion in a campaign that floods the npm registry with malicious packages. The malicious payload modifies the package.json file by removing private flags, altering 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 use these compromised packages, leading to potential security breaches in their applications.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall rigid_duck_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 avoid using the 'rigid_duck_z3n' package and any other packages associated with the tea.xyz token reward campaign. Additionally, you can use the following command to uninstall the package: 'npm uninstall rigid_duck_z3n'.
Conclusion
The 'rigid_duck_z3n' package presents a significant security risk due to its malicious code that alters package metadata and floods the npm registry. It is crucial for developers to remove this package and monitor their projects for vulnerabilities to maintain the integrity of their applications.
See every vulnerability recorded for rigid_duck_z3n →
FAQ
The 'rigid_duck_z3n' package is an npm package that is part of a campaign to generate and publish derivative packages for token rewards, but it has been compromised to include malicious code.
The malicious code modifies your package.json file, potentially exposing your application to security risks and polluting the npm registry with unwanted packages.
If you have installed the 'rigid_duck_z3n' package, it is advisable to uninstall it immediately and check for any other compromised packages in your project.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file. You can check your application for vulnerabilities using the Vulert playground without any signup.
Regularly update your dependencies, monitor for vulnerabilities using tools like Vulert, and review the npm registry for security advisories related to the packages you use.
