Critical Malicious Code Vulnerability in @silgi/module-builder Package
Summary
MAL-2025-191315: Malicious code in @silgi/module-builder (npm). Affects @silgi/module-builder versions 0.8.8. 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The @silgi/module-builder package is an npm module designed for building and managing modules in JavaScript applications. It is commonly used by developers to streamline their workflow and enhance productivity. However, this package has been compromised, making it a significant security risk for any system utilizing it.
Vulnerability Detail
The vulnerability stems from a malicious code injection within the @silgi/module-builder package, attributed to the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials from the user's environment and publish them to GitHub. It 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 severe data loss and system compromise.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @silgi/module-builderIf 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, avoid using the @silgi/module-builder package until it has been confirmed safe. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The @silgi/module-builder package has been identified as compromised, posing a significant security threat to users. Immediate action is required to mitigate risks, including removing the package and securing sensitive information. Regular monitoring of dependencies is essential to prevent future vulnerabilities.
See every vulnerability recorded for @silgi/module-builder →
FAQ
Immediately remove the package and rotate all secrets and keys stored on the affected machine.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without requiring any signup.
The consequences include unauthorized access to sensitive information, potential data loss, and full control of the compromised system by an external entity.
Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you in real-time for open-source vulnerabilities.
The malicious code was introduced by the Sha1-Hulud: The Second Coming NPM worm, which specifically targets npm packages.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
