Critical Malicious Code Vulnerability in solomon-api-stories Package
Summary
MAL-2025-191427: Malicious code in solomon-api-stories (npm). Affects solomon-api-stories versions 1.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 solomon-api-stories package is an npm library designed for managing and retrieving stories in a web application. It provides functionalities such as story creation, editing, and deletion, making it a useful tool for developers building content-driven applications. However, this package has been compromised, leading to severe security risks for any system utilizing it.
Vulnerability Detail
The vulnerability stems from a malicious code injection within the solomon-api-stories package, attributed to the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal sensitive tokens and credentials, publishing 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, making it a critical threat to system integrity and security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall solomon-api-stories
If 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, you can isolate the affected system from the network to prevent further data leakage while you remove the package. Additionally, consider using alternative packages that provide similar functionality without the associated risks.
Conclusion
The solomon-api-stories package has been compromised, posing significant risks to any systems using it. Immediate action is required to remove the package and secure sensitive information. Regular monitoring of dependencies is essential to maintain security in your applications.
See every vulnerability recorded for solomon-api-stories →
FAQ
Immediately remove the package and rotate any sensitive credentials stored on the affected system.
The malicious code can steal sensitive information, propagate to other packages, and potentially destroy your home directory.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without any signup.
Failing to address this vulnerability can lead to unauthorized access to sensitive data, loss of control over your systems, and potential data destruction.
While many npm packages are safe, it is crucial to regularly monitor and audit your dependencies for vulnerabilities using tools like Vulert.