Malicious Code Detected in drawon Package - Security Alert
Summary
MAL-2025-18773: Malicious code in drawon (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 drawon package is an npm library designed for drawing functionalities in web applications. It allows developers to create interactive graphics and visualizations easily. However, recent findings have revealed that this package contains malicious code, posing a significant risk to applications that utilize it.
Vulnerability Detail
The vulnerability stems from the inclusion of malicious code within the drawon package. This code can potentially compromise the integrity of applications using the package, leading to unauthorized access, data breaches, or other malicious activities. The issue was introduced in version 0 and affects all subsequent versions.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall drawon
If 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
If immediate updating is not feasible, consider removing the drawon package from your project temporarily until a secure version is available. You can do this by executing: npm uninstall drawon.
Conclusion
The discovery of malicious code in the drawon package highlights the importance of regularly monitoring and updating open-source dependencies. By following the recommended steps to fix or work around the vulnerability, developers can protect their applications from potential threats.
See every vulnerability recorded for drawon →
FAQ
The drawon package is used for creating drawing functionalities in web applications, allowing developers to implement interactive graphics.
The malicious code was identified by security researchers from Amazon Inspector, who found it during routine checks of open-source packages.
Using the compromised package can lead to unauthorized access to your application, data breaches, and potential exploitation of user data.
Yes, you can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json file. You can check your application for vulnerabilities without any signup at the Vulert playground.
If you cannot update the package right away, consider removing it from your project until a secure version is released to mitigate risks.