Critical Malicious Code Vulnerability in spstargm Package
Summary
MAL-2026-1969: Malicious code in spstargm (npm). Affects spstargm versions 1.0.0 – 1.1.0. 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 spstargm package is an npm library designed for specific functionalities within JavaScript applications. It is often utilized for managing tasks related to star ratings in web applications. However, this package has been identified as containing malicious code, which poses significant security risks to any system that has it installed.
Vulnerability Detail
The vulnerability stems from the presence of embedded malicious code within the spstargm package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package being flagged by the GitHub Security Advisory (GHSA) as a malicious package. Systems running this package should be considered fully compromised, and there is no guarantee that simply removing the package will eliminate all traces of the malicious software.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall spstargmIf 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
There are no specific workarounds to mitigate the risks associated with this vulnerability. The only effective action is to remove the affected package from your project.
Conclusion
The spstargm package has been identified as containing malicious code, posing significant risks to any system that has it installed. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor and alert for such vulnerabilities in the future.
See every vulnerability recorded for spstargm →
FAQ
You should immediately uninstall the spstargm package and rotate any secrets or keys stored on the compromised system.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
While removing the package is essential, there is no guarantee that all malicious software will be removed. It is advisable to perform a thorough security audit of your system.
Leaving the spstargm package installed can lead to unauthorized access to sensitive data and complete control of your system by malicious actors.
Yes, you can report this vulnerability to the maintainers of the spstargm package and also to security advisory platforms like GitHub.
