Malicious Package in kraken-api
Summary
GHSA-fgfj-rj24-mj7q: Malicious Package in kraken-api. Affects kraken-api versions 0.1.8. 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 kraken-api package is an npm package used for interacting with the Kraken cryptocurrency exchange API. It provides a convenient way for developers to access and manage their Kraken accounts programmatically. However, version 0.1.8 of this package contains a malicious code as a postinstall script.
Vulnerability Detail
The malicious code in version 0.1.8 of kraken-api package calls home to a Command and Control server, allowing an attacker to execute arbitrary commands on the compromised computer. This means that any computer with this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. Downgrading to version 0.1.7 is recommended, but it's important to note that removing the package may not remove all the malicious software installed by it.
How To Fix
No fixed version is published for this vulnerability.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
There is no specific workaround mentioned for this vulnerability. The recommended course of action is to remove the package and rotate all secrets and keys.
Conclusion
The kraken-api package version 0.1.8 contains a malicious code that compromises the security of the affected computer. It is recommended to remove the package, downgrade to version 0.1.7 if possible, and rotate all secrets and keys stored on the computer. For further support on vulnerability remediation, you can contact DevNack.com.
See every vulnerability recorded for kraken-api →
FAQ
The impact of this vulnerability is severe as it allows an attacker to execute arbitrary commands on the compromised computer. All secrets and keys stored on that computer should be considered compromised.
You can use the Vulert Playground at Vulert Scanner to check if your computer is affected by this vulnerability. Simply provide your package-lock.json file, and Vulert will alert you in real-time if any open-source vulnerabilities are detected.
Yes, downgrading to version 0.1.7 of the kraken-api package can mitigate the risk of this vulnerability. However, it is still recommended to remove the package and rotate all secrets and keys.
If your computer is affected, it is crucial to remove the kraken-api package immediately. Additionally, all secrets and keys stored on that computer should be rotated from a different, secure computer.
There is no guarantee that removing the kraken-api package will remove all malicious software resulting from its installation. The computer may have been fully compromised, so it is important to take additional steps such as rotating all secrets and keys.
