Critical Malicious Code Vulnerability in @sameepsi/sor2 Package
Summary
MAL-2025-191310: Malicious code in @sameepsi/sor2 (npm). Affects @sameepsi/sor2 versions 2.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 @sameepsi/sor2 package is an npm library that is used for various functionalities in JavaScript applications. It is designed to facilitate certain operations within the npm ecosystem. However, this package has been compromised, making it a significant security risk for any application that relies on it. The malicious code embedded within the package can lead to severe consequences for users and their systems.
Vulnerability Detail
The vulnerability originates from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is capable of stealing tokens and credentials, publishing them to GitHub, and propagating itself to other npm packages owned by the user. Additionally, it can establish persistence through GitHub actions and may even destroy the user's home directory. Any system with this package installed is considered fully compromised, necessitating immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @sameepsi/sor2If 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, ensure that you do not run any applications that depend on the @sameepsi/sor2 package until it has been removed and your system has been secured. Additionally, monitor your GitHub repositories for any unauthorized changes or actions.
Conclusion
The @sameepsi/sor2 package has been compromised, posing a critical security risk to users. Immediate removal of the package and rotation of sensitive credentials is essential to mitigate the impact of this vulnerability. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.
See every vulnerability recorded for @sameepsi/sor2 →
FAQ
Immediately remove the package and rotate any secrets or keys stored on your system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without any signup.
Failing to address this vulnerability can lead to unauthorized access to your tokens and credentials, potential data loss, and compromise of your entire system.
Currently, there is no patched version available. The best course of action is to remove the package entirely.
Vulert monitors and alerts in real-time for open-source vulnerabilities using just the package-lock.json file, providing a proactive approach to security.
