Critical Malicious Code Vulnerability in @dev-blinq/cucumber-js Package
Summary
MAL-2025-191212: Malicious code in @dev-blinq/cucumber-js (npm). Affects @dev-blinq/cucumber-js versions 1.0.131. 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-js package is a JavaScript library used for behavior-driven development (BDD) testing with Cucumber. It allows developers to write tests in a human-readable format, facilitating collaboration between technical and non-technical stakeholders. However, this package has been compromised, exposing users to significant security risks.
Vulnerability Detail
The vulnerability stems from a malicious code injection by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal sensitive tokens and credentials from users and publish them to GitHub. Additionally, it can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. The malicious payload poses a risk of destroying the user's home directory, leading to potential data loss.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @dev-blinq/cucumber-jsIf 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 workaround, consider removing the @dev-blinq/cucumber-js package from your project until a secure version is released. You can do this by running: npm uninstall @dev-blinq/cucumber-js. Additionally, monitor your system for any unauthorized access or changes.
Conclusion
The @dev-blinq/cucumber-js package has been compromised by a malicious worm, posing serious security risks to users. It is essential to take immediate action by uninstalling the package and monitoring for any unauthorized access. Stay vigilant and ensure to update to a patched version once available.
See every vulnerability recorded for @dev-blinq/cucumber-js →
FAQ
The vulnerability involves malicious code that steals credentials and can destroy user data.
You can use Vulert, which monitors open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.
Immediately uninstall the package and monitor your system for any unauthorized access. Update to a patched version as soon as it is available.
Yes, the worm can propagate to other NPM packages that you own, increasing the risk of further compromise.
Consequences include loss of sensitive data, unauthorized access to your GitHub repositories, and potential destruction of your home directory.
