Critical Malicious Code Vulnerability in @silgi/permission Package
Summary
MAL-2025-191317: Malicious code in @silgi/permission (npm). Affects @silgi/permission versions 0.6.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
Background
The @silgi/permission package is an npm library designed to manage user permissions within applications. It provides developers with tools to implement and control access rights effectively. However, this package has been compromised, making it a significant security risk for any application utilizing it.
Vulnerability Detail
The vulnerability stems from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This payload is capable of stealing tokens and credentials, which are then published to GitHub. Additionally, the worm can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. There is also a risk of the worm destroying the user's home directory, leading to severe data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @silgi/permissionIf 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, you can isolate the affected environment by removing the package and ensuring that no other packages are compromised. Use the following command to uninstall the package: npm uninstall @silgi/permission.
Conclusion
The @silgi/permission package has been compromised, posing a severe security risk to applications that utilize it. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for @silgi/permission →
FAQ
Immediately uninstall the package and rotate any secrets or keys stored on the affected machine.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without signing up.
The risks include credential theft, unauthorized access to your GitHub repositories, and potential destruction of your home directory.
Regularly audit your dependencies, use tools like Vulert for real-time monitoring, and ensure you are using trusted packages.
The malicious code was introduced by the Sha1-Hulud: The Second Coming NPM worm, which compromised the package.
