Critical Malicious Code Vulnerability in sparkling-cli Package
Summary
MAL-2026-156: Malicious code in sparkling-cli (npm). Affected versions are not published. 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 sparkling-cli package is a command-line interface tool designed for developers to create and manage sparkling applications. It is widely used in the npm ecosystem for its ease of use and functionality. However, it has recently been identified as containing malicious code, which poses significant security risks to any system where it is installed.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the sparkling-cli package. This code can compromise the entire system, allowing unauthorized access to sensitive information, including secrets and keys stored on the affected computer. The malicious nature of this code means that any system running this package should be considered fully compromised, and the risks extend beyond just the package itself, potentially affecting the integrity of the entire system.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall sparkling-cliIf 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
Currently, there are no effective workarounds to mitigate the risks posed by the malicious code in sparkling-cli. The only recommended action is to uninstall the package and secure the system.
Conclusion
The sparkling-cli package has been identified as containing malicious code, posing significant risks to any system where it is installed. Immediate action is required to uninstall the package and secure sensitive information. Regular monitoring for vulnerabilities using tools like Vulert is highly recommended.
See every vulnerability recorded for sparkling-cli →
FAQ
You should uninstall sparkling-cli immediately and rotate any sensitive information stored on your system.
You can use Vulert's playground at Vulert Scanner to check if your application is affected without requiring any signup.
No, there is currently no patched version available for sparkling-cli. It is recommended to uninstall the package.
Failing to remove sparkling-cli may result in unauthorized access to your system and compromise sensitive data.
Vulert uses the package-lock.json file to monitor and alert in real-time for open-source vulnerabilities in your software.
