Critical Malicious Code Vulnerability in @sameepsi/sor Package
Summary
MAL-2025-191309: Malicious code in @sameepsi/sor (npm). Affects @sameepsi/sor versions 1.0.3. 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/sor package is an npm library designed for specific functionalities within JavaScript applications. However, it has been compromised by a malicious entity, leading to severe security risks for users who have it installed. This package is particularly vulnerable due to its exposure to the Sha1-Hulud: The Second Coming NPM worm, which exploits its functionality to execute harmful actions.
Vulnerability Detail
The vulnerability stems from the presence of malicious code within the @sameepsi/sor package, which has been identified as part of a broader attack vector involving the Sha1-Hulud 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. Furthermore, it can establish persistence through GitHub actions and may even destroy the user's home directory, leading to a complete compromise of the affected system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @sameepsi/sorIf 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 workaround, users should ensure that they do not run any applications that depend on the @sameepsi/sor package until it has been completely removed. Regularly monitor your system for any unusual activity and consider using tools like Vulert to check for vulnerabilities in your package-lock.json file.
Conclusion
The @sameepsi/sor package has been compromised, leading to significant security risks for users. Immediate action is required to uninstall the package and secure any sensitive information. Regular monitoring and vulnerability checks are essential to maintain the integrity of your applications.
See every vulnerability recorded for @sameepsi/sor →
FAQ
Immediately uninstall the package using npm uninstall @sameepsi/sor and rotate any sensitive credentials.
The malicious code can steal sensitive information, propagate to other packages, and potentially destroy your home directory.
No, there is currently no patched version of the @sameepsi/sor package available. The only solution is to remove it.
You can use Vulert, which monitors your package-lock.json for vulnerabilities in real-time without requiring code access.
Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.
