Critical Malicious Code Vulnerability in starling-api Package
Summary
MAL-2025-192596: Malicious code in starling-api (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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The starling-api package is a Node.js library designed for interfacing with the Starling Bank API, enabling developers to integrate banking functionalities into their applications. It is widely used in various projects for its ease of use and comprehensive features. However, recent findings have revealed that this package contains malicious code, posing significant risks to any system utilizing it.
Vulnerability Detail
The vulnerability originates from the presence of embedded malicious code within the starling-api package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The ramifications of this vulnerability are severe, as it can lead to full control of the affected system by an external entity, making it imperative for users to take immediate action.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall starling-apiIf 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 effective workarounds for this vulnerability. The only recommended action is to uninstall the starling-api package and secure your system.
Conclusion
The discovery of malicious code within the starling-api package poses a critical threat to users. Immediate action is required to uninstall the package and secure any sensitive information. Users are encouraged to utilize tools like Vulert for ongoing monitoring of vulnerabilities in their applications.
See every vulnerability recorded for starling-api →
FAQ
You should immediately uninstall the starling-api package and rotate any sensitive information stored on your system.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without any signup.
Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential financial loss.
There are no effective mitigation strategies; the best course of action is to remove the package entirely.
While removing the package is essential, there is no guarantee that all malicious software has been eliminated. It is advisable to conduct a thorough security audit of your system.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
