Critical Malicious Code Vulnerability in @mizzle-dev/orm Package
Summary
MAL-2025-191247: Malicious code in @mizzle-dev/orm (npm). Affects @mizzle-dev/orm versions 0.0.2. 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 @mizzle-dev/orm package is a Node.js ORM (Object-Relational Mapping) library designed to facilitate database interactions in JavaScript applications. It provides developers with an intuitive API to manage database records and relationships. However, this package has been compromised, making it susceptible to severe security threats.
Vulnerability Detail
The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal sensitive tokens and credentials from users, publishing them to GitHub. Additionally, it can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. The worm poses a significant risk as it may also delete the user's home directory, leading to potential data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @mizzle-dev/ormIf 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 @mizzle-dev/orm package from your project until a secure version is released. You can do this by executing: npm uninstall @mizzle-dev/orm. Additionally, monitor your GitHub repositories for any unauthorized changes or actions.
Conclusion
The @mizzle-dev/orm package has been compromised by a malicious worm that poses serious security risks. It is essential to take immediate action to protect your applications by updating or removing the affected package. Regular monitoring and using tools like Vulert can help maintain the security of your software.
See every vulnerability recorded for @mizzle-dev/orm →
FAQ
The vulnerability involves malicious code that can steal sensitive information and potentially delete user data.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Immediately uninstall the compromised version and monitor your accounts for any unauthorized access. Update to a patched version as soon as it is available.
Yes, the worm can propagate to other NPM packages owned by the user, increasing the risk of widespread compromise.
Consequences include unauthorized access to sensitive information, data loss, and potential damage to your development environment.
