Which versions of blinqio-executions-cli are malicious?

The following npm versions of blinqio-executions-cli are flagged malicious: 1.0.41. Treat any of these as compromised.

How do I remediate blinqio-executions-cli if I installed it?

blinqio-executions-cli 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.

I already installed blinqio-executions-cli — how do I know if it already compromised me?

If blinqio-executions-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is blinqio-executions-cli part of a known attack campaign?

Yes — blinqio-executions-cli is associated with the GHSA-grm4-x7gc-qhg2 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find blinqio-executions-cli across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for blinqio-executions-cli (version 1.0.41). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging blinqio-executions-cli across your stack and pipelines.

Malicious package

blinqio-executions-clinpm

Malicious code in blinqio-executions-cli (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191076

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

npm uninstall blinqio-executions-cli

What this malware does

The package blinqio-executions-cli 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

1 flagged

1.0.41

Indicators of compromise (SHA-256)

fe0a204aa6311e23a86c20ef8823dc5e8767e427ccd1c23e9d289028e8e778e1

fa53788034d07d937401f1812037a1d38674b71fd61f8eaa22cfc07ebadcde61

d9e5a96fa18543da294b321a481fba9ad03884c6ca9387794f923c84892966be

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for blinqio-executions-cli (version 1.0.41). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging blinqio-executions-cli across your stack and pipelines.
If you installed it — respond
blinqio-executions-cli 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.
Did it already run?
If blinqio-executions-cli was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks blinqio-executions-cli before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

No. blinqio-executions-cli on npm has been identified as a malicious package (version 1.0.41 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-grm4-x7gc-qhg2

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks blinqio-executions-cli-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring