Which versions of bvdfhdfvnk3 are malicious?

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

How do I remediate bvdfhdfvnk3 if I installed it?

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

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

Yes — bvdfhdfvnk3 is associated with the GHSA-cp2x-vxp4-762f, IN-MAL-2026-017527 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 bvdfhdfvnk3 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 bvdfhdfvnk3 (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 bvdfhdfvnk3 across your stack and pipelines.

Malicious package

bvdfhdfvnk3npm

bvdfhdfvnk3 is a confirmed malicious npm package (MAL-2026-13790) that executes malicious code on install (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bvdfhdfvnk3 (npm)

MAL-2026-13790

Immediate action

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

npm uninstall bvdfhdfvnk3

What this malware does

The tarball contains a single index.html declared as the package main, with no JavaScript entrypoint and no preinstall/install/postinstall/prepare lifecycle scripts. The HTML loads Cloudflare Turnstile and, on Turnstile completion, an obfuscator.io-packed script constructs a URL to campaigns.microlive.club and calls window.location.replace to redirect the browser there. Node.js cannot execute an HTML file as main, so nothing runs on npm install or on require() of this package. The redirect only fires if a browser directly opens the HTML file. This is npm being used as static hosting for a cloaked redirect page rather than code that harms installers.

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

1 flagged

1.0.0

Indicators of compromise (SHA-256)

e2445848aeadf8022228ed7bb744e6d221c76e10be583d1e24e0edf71cbee525

6fadba2f2b2bb1c3507b2559209c50677db3b20feb0c083333567dfe7fcbddc4

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 bvdfhdfvnk3 (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 bvdfhdfvnk3 across your stack and pipelines.
If you installed it — respond
Remove bvdfhdfvnk3 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 bvdfhdfvnk3 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 bvdfhdfvnk3 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. bvdfhdfvnk3 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-cp2x-vxp4-762fIN-MAL-2026-017527

References

Credits

Amazon Inspector · finder

Detect & block this

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