Malicious Code Injection in dynamic_slug_z3n: A Threat to npm Ecosystem
Summary
MAL-2025-101838: Malicious code in dynamic_slug_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 dynamic_slug_z3n package is part of the npm ecosystem, which is widely used for JavaScript package management. This package, like many others, is intended to facilitate the development and deployment of applications by providing reusable code components. However, it has been identified as part of a malicious campaign that aims to inflate developer reputation scores through the automatic generation and publication of derivative packages. This behavior poses significant risks to developers and the integrity of the npm registry.
Vulnerability Detail
The vulnerability in dynamic_slug_z3n stems from its association with a malicious campaign that modifies the package.json file to remove private flags, changes version numbers, and generates random package names. This results in the continuous republishing of variants, which pollutes the npm registry and can lead to the unintentional use of compromised packages by developers. The malicious payload is designed to exploit the npm ecosystem, making it crucial for developers to be aware of such threats.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dynamic_slug_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 dynamic_slug_z3n package altogether and look for alternative packages that provide similar functionality without the associated risks. Additionally, regularly audit your dependencies using tools like Vulert to monitor for vulnerabilities.
Conclusion
The dynamic_slug_z3n package poses a significant threat to the npm ecosystem due to its malicious behavior. Developers must take proactive measures to remove this package and monitor their dependencies for vulnerabilities. Utilizing tools like Vulert can help ensure the security of your applications.
See every vulnerability recorded for dynamic_slug_z3n →
FAQ
dynamic_slug_z3n is an npm package that has been identified as part of a malicious campaign aimed at inflating developer reputation scores.
The vulnerability can lead to the unintentional use of compromised packages, which may introduce security risks and instability to your application.
You should uninstall the dynamic_slug_z3n package immediately and audit your project for any other potentially compromised packages.
You can use tools like Vulert, which monitors your package-lock.json file for open-source vulnerabilities in real-time without requiring code access or installation.
Yes, you can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
