Critical Malicious Code Vulnerability in @cllbk/ghl Package
Summary
MAL-2025-191206: Malicious code in @cllbk/ghl (npm). Affects @cllbk/ghl versions 1.3.1. 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 @cllbk/ghl package is a Node.js library available on npm, designed for various functionalities within JavaScript applications. However, it has recently been compromised, making it a significant security risk. The vulnerability stems from a malicious payload that can steal sensitive information and propagate itself to other packages owned by the user.
Vulnerability Detail
The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected version 1.3.1 of the @cllbk/ghl package. This malicious code can steal tokens and credentials, publishing them to GitHub, and may also destroy the user's home directory. Any system running this package is considered fully compromised, necessitating immediate action to secure sensitive information.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @cllbk/ghlIf 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 other than removing the package and securing your environment. It is advisable to monitor your systems for any unusual activity following the removal.
Conclusion
The @cllbk/ghl package has been compromised by malicious code that poses significant risks to users. Immediate action is required to remove the package and secure sensitive information. Regular monitoring for vulnerabilities is essential to maintain a secure development environment.
See every vulnerability recorded for @cllbk/ghl →
FAQ
Immediately uninstall the package and rotate any sensitive credentials stored on the affected system.
The malicious payload can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions.
Failure to address this vulnerability can lead to unauthorized access to sensitive information, potential data loss, and further compromise of your development environment.
Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just the package-lock.json file.
You can use the Vulert playground at Vulert Scanner to check if your application is affected without requiring any signup.
