Critical Malicious Code Vulnerability in @silgi/drizzle Package
Summary
MAL-2025-191312: Malicious code in @silgi/drizzle (npm). Affects @silgi/drizzle versions 0.8.4. 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 @silgi/drizzle package is an npm library designed for managing database interactions in JavaScript applications. It provides developers with tools to streamline data handling and improve application performance. However, this package has been compromised, exposing users to severe security risks.
Vulnerability Detail
The vulnerability stems from a malicious code injection within the @silgi/drizzle package, specifically version 0.8.4. This package was compromised by the Sha1-Hulud: The Second Coming NPM worm, which is known to steal tokens and credentials, publishing them to GitHub. The worm can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. Additionally, it poses a risk of destroying the user's home directory, leading to potential data loss and unauthorized access.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @silgi/drizzleIf 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 measure, users should avoid using the @silgi/drizzle package until it has been confirmed safe. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The @silgi/drizzle package has been compromised by malicious code, posing significant security risks to users. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help monitor and mitigate future vulnerabilities.
See every vulnerability recorded for @silgi/drizzle →
FAQ
Immediately remove the package and rotate any secrets or keys that may have been compromised.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without needing to sign up.
The consequences include unauthorized access to sensitive information, potential data loss, and the risk of further propagation of malicious code.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
While many npm packages are safe, it's crucial to remain vigilant and use tools like Vulert to monitor for vulnerabilities in your dependencies.
