Which versions of bfvkjmeikpwhqxc are malicious?

The following npm versions of bfvkjmeikpwhqxc are flagged malicious: 0.0.0-stage, 1.0.0, 1.0.1. Treat any of these as compromised.

How do I remediate bfvkjmeikpwhqxc if I installed it?

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

If bfvkjmeikpwhqxc 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.

Is bfvkjmeikpwhqxc part of a known attack campaign?

Yes — bfvkjmeikpwhqxc is associated with the GHSA-pg3x-mr83-5crv 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 bfvkjmeikpwhqxc across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for bfvkjmeikpwhqxc (3 malicious versions).

Malicious package

bfvkjmeikpwhqxcnpm

Advisory published Nov 2, 2026Updated Nov 2, 2026

bfvkjmeikpwhqxc is a confirmed malicious npm package (MAL-2026-18483) that executes malicious code on install (malicious versions 0.0.0-stage, 1.0.0, 1.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bfvkjmeikpwhqxc (npm)

MAL-2026-18483

Immediate action

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

npm uninstall bfvkjmeikpwhqxc

What this malware does

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.

Malicious versions

3 flagged

0.0.0-stage1.0.01.0.1

Indicators of compromise (SHA-256)

bc18af375249e950878cf3a95c2290bdee9ec1a2e188d0bba906acda390403e5

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for bfvkjmeikpwhqxc (3 malicious versions).
If you installed it — respond
Remove bfvkjmeikpwhqxc 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 bfvkjmeikpwhqxc 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. bfvkjmeikpwhqxc on npm has been identified as a malicious package (versions 0.0.0-stage, 1.0.0, 1.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-pg3x-mr83-5crv

References

github.com

Detect & block this

O3 blocks bfvkjmeikpwhqxc-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

Explore

All malware advisories How O3 detects malware Vulnerability database