Malicious Code Injection in digital_donkey_z3n Package
Summary
MAL-2025-98678: Malicious code in digital_donkey_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 digital_donkey_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package was identified as part of a malicious campaign that aimed to exploit npm's publishing system. It is designed to generate and publish derivative packages with randomized names, which can inflate developer reputation scores for token rewards. The presence of this package poses a significant risk to developers and users relying on npm for secure package management.
Vulnerability Detail
This vulnerability originates from the digital_donkey_z3n package, which contains malicious code that modifies the package.json file to remove private flags, alters version numbers, and generates random package names. The malicious payload continuously republishes these variants, polluting the npm registry and potentially leading to security breaches and compromised applications. The exploitation of this vulnerability can result in unauthorized access to sensitive data and a loss of trust in the npm ecosystem.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall digital_donkey_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 digital_donkey_z3n package and look for alternative packages that provide similar functionality without the associated risks. Additionally, you can monitor your package-lock.json file for any unauthorized changes.
Conclusion
The digital_donkey_z3n package poses a significant security risk due to its malicious code that alters package configurations and republishing behavior. It is crucial for developers to remove this package from their projects and monitor their dependencies for any unauthorized changes. Utilizing tools like Vulert can help maintain the security of your applications.
See every vulnerability recorded for digital_donkey_z3n →
FAQ
The digital_donkey_z3n package is an npm package that has been identified as part of a malicious campaign to exploit the npm registry.
This vulnerability can lead to unauthorized modifications in your application's dependencies, potentially compromising its security and integrity.
You should uninstall the digital_donkey_z3n package immediately and check for any dependencies that may have been affected.
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.
