NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@dev-blinq/cucumber_clientnpm

Advisory published Updated

@dev-blinq/cucumber_client is a confirmed malicious npm package (MAL-2025-191213) that steals credentials and exfiltrates sensitive data (malicious versions 1.0.736, 1.0.737, 1.0.738…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @dev-blinq/cucumber_client (npm)

MAL-2025-191213
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @dev-blinq/cucumber_client

What this malware does

The package @dev-blinq/cucumber_client was found to contain malicious code.

Any computer that has 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. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

7 flagged
1.0.7361.0.7371.0.7381.0.7391.0.1393-stage1.0.1394-stage1.0.1634-dev

Indicators of compromise (SHA-256)

d4423970644a3fcfa214dba271ed72641deb43f25ca572783ff6783dc4b89c1c
18aa2351e84034cab769245e36e6aa0a48e60a01f5d71f66d89b7f321c486baa
f6fff1942d89be5a0a85bfaaf6e778a0cbd4c70e2acb411a2345db2d7ee296d8
db4a451970465311f6a1d2b9ac8b4713f2f4ff114aa37c12dd0daff6032c8ab6

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @dev-blinq/cucumber_client (7 malicious versions).

  2. If you installed it — respond

    @dev-blinq/cucumber_client is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

  3. Did it already run?

    If @dev-blinq/cucumber_client was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @dev-blinq/cucumber_client on npm has been identified as a malicious package (versions 1.0.736, 1.0.737, 1.0.738, 1.0.739, 1.0.1393-stage, 1.0.1394-stage, 1.0.1634-dev flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-hw88-7qh5-5pvx

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @dev-blinq/cucumber_client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Explore

@dev-blinq/cucumber_client (npm) malicious package — MAL-2025-191213 | O3 Security