Malicious Code Injection in due_asp_z3n: A Threat to npm Packages
Summary
MAL-2025-101797: Malicious code in due_asp_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 due_asp_z3n package is part of the npm ecosystem, which is widely used for JavaScript development. This package has been identified as part of a malicious campaign that floods the npm registry with derivative packages. These packages are designed to inflate developer reputation scores through automated publishing scripts, making them a significant threat to the integrity of the npm ecosystem.
Vulnerability Detail
The vulnerability in due_asp_z3n stems from its malicious payload that modifies the package.json file. It removes private flags, alters version numbers, and generates random package names, leading to the continuous republishing of variants. This behavior not only pollutes the npm registry but also compromises the security of applications relying on this package. The origin of this issue is linked to a token reward campaign that incentivizes such malicious activities.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall due_asp_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, consider removing the due_asp_z3n package from your project if it is not essential. You can do this by running the command: npm uninstall due_asp_z3n. Additionally, monitor your package-lock.json file for any unauthorized changes.
Conclusion
The due_asp_z3n package poses a significant risk due to its malicious behavior of modifying package files and republishing variants. It is crucial for developers to take immediate action by updating or removing the package to safeguard their applications. Utilizing tools like Vulert can help in monitoring for such vulnerabilities effectively.
See every vulnerability recorded for due_asp_z3n →
FAQ
The due_asp_z3n package is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
This vulnerability can lead to the injection of malicious code into your application, potentially compromising its security and integrity.
If you are using due_asp_z3n, it is recommended to update the package to a patched version or remove it from your project.
You can use Vulert to monitor and alert in real-time for open-source vulnerabilities in your software by analyzing your package-lock.json file.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
