Malicious Code Injection in outer_duck_z3n: npm Package Vulnerability
Summary
MAL-2025-122426: Malicious code in outer_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 outer_duck_z3n package is part of a broader ecosystem within the npm registry, often associated with token reward campaigns. These packages are typically designed to automate the generation and publication of derivative packages, which can inflate developer reputation scores. The malicious nature of this package lies in its ability to modify critical files and republish variants, leading to potential abuse within the npm ecosystem.
Vulnerability Detail
The vulnerability in the outer_duck_z3n package stems from its malicious payload that alters the package.json file. This includes removing private flags, changing version numbers, and generating random package names, which can lead to pollution of the npm registry. The origin of this issue is linked to a campaign that aims to exploit the npm ecosystem for token rewards, thereby compromising the integrity of the registry and potentially affecting developers who rely on these packages.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall outer_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 outer_duck_z3n package in your project. Additionally, consider using npm audit to identify and address vulnerabilities in your dependencies.
Conclusion
The outer_duck_z3n package presents a significant vulnerability due to its malicious code that alters essential files and repopulates the npm registry with compromised packages. It is crucial for developers to remove this package and monitor their dependencies for security.
See every vulnerability recorded for outer_duck_z3n →
FAQ
outer_duck_z3n is an npm package that is part of a token reward campaign, designed to automate the generation of derivative packages.
The vulnerability can lead to the pollution of the npm registry, potentially affecting the integrity and security of your project's dependencies.
You should remove the outer_duck_z3n package from your project and monitor for any updates or patches that may be released.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time using just your package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without needing to sign up.
Follow Vulert in Google
Get more Vulert vulnerability and dependency-security updates in Google Search and AI results.