Malicious Code Detected in Dystatic Package - Security Alert
Summary
MAL-2025-19045: Malicious code in dystatic (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
Dystatic is an npm package designed for static site generation, enabling developers to create and deploy web applications efficiently. It offers features such as templating, routing, and asset management. However, recent findings have revealed that the package contains malicious code, posing significant risks to users and their applications.
Vulnerability Detail
The vulnerability in the dystatic package originates from the inclusion of malicious code that can compromise the security of applications utilizing this package. This code may allow unauthorized access to sensitive data, execute arbitrary commands, or facilitate other harmful activities. Users of the package are at risk of data breaches and potential exploitation by malicious actors.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall dystaticIf 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 dystatic package from your project until a secure version is available. You can do this by executing: npm uninstall dystatic.
Conclusion
The discovery of malicious code in the dystatic package highlights the importance of vigilance in managing open-source dependencies. Users are urged to update their packages promptly and utilize tools like Vulert to monitor for vulnerabilities effectively.
See every vulnerability recorded for dystatic →
FAQ
The malicious code can potentially allow unauthorized access to sensitive data and execute harmful commands within the user's application.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Yes, users are advised to update to the latest version of the dystatic package to mitigate the vulnerability.
If immediate updates are not possible, consider removing the package from your project as a temporary measure.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and keep your packages updated to their latest secure versions.
