@dev-blinq/cucumber_client (npm) · Malicious Code
Affects @dev-blinq/cucumber_clientSource GCVE Database
Malicious package : remove @dev-blinq/cucumber_client and rotate any secrets on hosts that installed it.
Data as of 20 Nov 2026, 01:04 UTC
Malicious package
Published to npm · OSV MAL-2025-191213
What to do
Remove @dev-blinq/cucumber_client from every project, lockfile and image that pulls it in. Treat any host that installed it as compromised: rotate the credentials, tokens and keys it could read, from a clean machine.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npm@dev-blinq/cucumber_client | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
The npm package @dev-blinq/cucumber_client contains malicious code linked to the Sha1-Hulud: The Second Coming NPM worm. This malware steals tokens and credentials, publishes them to GitHub, propagates itself to other NPM packages owned by the user, and establishes persistence via GitHub actions. It may also destroy the user's home directory. Systems with this package installed should be considered fully compromised.
References
- aikido.dev/blog/shai-hulud-strikes-again-hitting-zapier-ensdomains (opens in a new tab)
- wiz.io/blog/shai-hulud-2-0-ongoing-supply-chain-attack (opens in a new tab)
- stepsecurity.io/blog/sha1-hulud-the-second-coming-zapier-ens-domains-and-other-prominent-npm-packages-compromised (opens in a new tab)
- github.com/advisories/GHSA-hw88-7qh5-5pvx (opens in a new tab)