Which versions of bip40 are malicious?

The following npm versions of bip40 are flagged malicious: 1.0.0. Treat any of these as compromised.

How do I remediate bip40 if I installed it?

Remove bip40 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed bip40 — how do I know if it already compromised me?

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

Yes — bip40 is associated with the GHSA-vh2r-52fp-rj7h 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 bip40 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 bip40 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bip40 across your stack and pipelines.

Malicious package

bip40npm

Malicious code in bip40 (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191469

Immediate action

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

npm uninstall bip40

What this malware does

The package bip40 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.

The OpenSSF Package Analysis project identified 'bip40' @ 1.0.0 (npm) as malicious.

It is considered malicious because:

The package communicates with a domain associated with malicious activity.

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

87ccb91e64734ece6957334cae8ce8d68b9c65cac28684c5b6d6b9c08e9a2177

39978dd4e71a01636f852725943d9488f7e1ba9f71fe9ca6a1f402a6c747fa34

376d623eb0ffaacfbc6857b02083c7a1d37460c78579f88ddf63e6850cadc3e1

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bip40 (version 1.0.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging bip40 across your stack and pipelines.
If you installed it — respond
Remove bip40 from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If bip40 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 bip40 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. bip40 on npm has been identified as a malicious package (version 1.0.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-vh2r-52fp-rj7h

References

github.com

Credits

Amazon Inspector · finder
OpenSSF: Package Analysis · finder

Detect & block this

O3 blocks bip40-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring