Critical Malicious Code Vulnerability in @dev-blinq/cucumber_client Package
Summary
MAL-2025-191213: Malicious code in @dev-blinq/cucumber_client (npm). Affects @dev-blinq/cucumber_client versions 1.0.1393-stage – 1.0.739. 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 @dev-blinq/cucumber_client package is an npm library designed for integrating Cucumber testing frameworks into applications. It is utilized by developers to facilitate behavior-driven development (BDD) testing. However, this package has been compromised, leading to significant security risks for any system utilizing it.
Vulnerability Detail
The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected the @dev-blinq/cucumber_client package. This malicious code is capable of stealing tokens and credentials, subsequently publishing them to GitHub. Furthermore, it can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. The worm may also have the potential to destroy the user's home directory, leading to severe data loss and system compromise.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @dev-blinq/cucumber_clientIf 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
As a temporary measure, you can prevent the execution of the compromised package by uninstalling it with the command: npm uninstall @dev-blinq/cucumber_client. However, be aware that this may not eliminate all traces of the malicious software.
Conclusion
The @dev-blinq/cucumber_client package has been compromised by a malicious worm, posing serious security threats to users. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring and using tools like Vulert can help prevent future vulnerabilities.
See every vulnerability recorded for @dev-blinq/cucumber_client →
FAQ
Immediately uninstall the package and rotate all secrets and keys stored on the affected machine.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.
The risks include unauthorized access to sensitive information, potential data loss, and the possibility of further propagation of the malicious code to other packages.
Recovery may depend on your backup solutions. It is recommended to regularly back up important data to prevent loss from such incidents.
Once a package has been compromised, it is advisable to avoid using it until it has been thoroughly audited and confirmed safe by the community.
