Which versions of @dev-blinq/blinqioclient are malicious?

The following npm versions of @dev-blinq/blinqioclient are flagged malicious: 1.0.21. Treat any of these as compromised.

How do I remediate @dev-blinq/blinqioclient if I installed it?

@dev-blinq/blinqioclient 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 @dev-blinq/blinqioclient — how do I know if it already compromised me?

If @dev-blinq/blinqioclient 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 @dev-blinq/blinqioclient part of a known attack campaign?

Yes — @dev-blinq/blinqioclient is associated with the RLMA-2025-06018 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 @dev-blinq/blinqioclient 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 @dev-blinq/blinqioclient (version 1.0.21). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @dev-blinq/blinqioclient across your stack and pipelines.

Malicious package

@dev-blinq/blinqioclientnpm

Malicious code in @dev-blinq/blinqioclient (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191211

Immediate action

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

npm uninstall @dev-blinq/blinqioclient

What this malware does

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

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.21

Indicators of compromise (SHA-256)

745bb6a14ea7476c5b4262eed189519fda19d65f97baafea52a2215c9e00cf4b

b3a1d417e283165e25dc75c9510f4bcdde80854ca5600090b4de220548e72ae1

0efea55cd9181ef18880d5ebddd353129bc11d38b718faf5866b4cb81949dbba

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 @dev-blinq/blinqioclient (version 1.0.21). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging @dev-blinq/blinqioclient across your stack and pipelines.
If you installed it — respond
@dev-blinq/blinqioclient 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 @dev-blinq/blinqioclient 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 @dev-blinq/blinqioclient 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. @dev-blinq/blinqioclient on npm has been identified as a malicious package (version 1.0.21 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2025-06018

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @dev-blinq/blinqioclient-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