Which versions of bidirectional-adapter are malicious?

The following npm versions of bidirectional-adapter are flagged malicious: 1.2.2, 1.2.3, 1.2.4, 1.2.5. Treat any of these as compromised.

How do I remediate bidirectional-adapter if I installed it?

bidirectional-adapter 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 bidirectional-adapter — how do I know if it already compromised me?

If bidirectional-adapter 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 bidirectional-adapter part of a known attack campaign?

Yes — bidirectional-adapter is associated with the GHSA-vhm7-gf4p-j2rq, RLMA-2025-06066 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 bidirectional-adapter 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 bidirectional-adapter (4 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bidirectional-adapter across your stack and pipelines.

Malicious package

bidirectional-adapternpm

Malicious code in bidirectional-adapter (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191075

Immediate action

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

npm uninstall bidirectional-adapter

What this malware does

The package bidirectional-adapter 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

4 flagged

1.2.21.2.31.2.41.2.5

Indicators of compromise (SHA-256)

08b05c32c22c6fed17ce75a21ba4cee91ded4efc48b98739d3415942de39c55e

e5986d109580870d96a5e492aeb85ca7d1207efc3f767d00e6bdbfa8cd80f69d

802437a698d42bdff3afaeed455af9851ac155ca0e78774e22f0f08416199c3a

9232b33b143ce14e500ddb0d725a5b646a180ad4bd7dbf1fc8890baefdd22f95

fb23d3d004f988e32f5a2d9cb6c90e775437971a0ff256d5aa02f9dc25603957

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

Campaign

GHSA-vhm7-gf4p-j2rqRLMA-2025-06066

References

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks bidirectional-adapter-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