Which versions of bcnfjndwbkf2 are malicious?

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

How do I remediate bcnfjndwbkf2 if I installed it?

bcnfjndwbkf2 is a typosquat — you almost certainly intended a legitimately-named package. Remove bcnfjndwbkf2, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

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

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

Yes — bcnfjndwbkf2 is associated with the GHSA-7cv8-7v66-c3mh, IN-MAL-2026-017535 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 bcnfjndwbkf2 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 bcnfjndwbkf2 (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 bcnfjndwbkf2 across your stack and pipelines.

Malicious package

bcnfjndwbkf2npm

bcnfjndwbkf2 is a confirmed malicious npm package (MAL-2026-13783) that typosquats a legitimate package to trick installs (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bcnfjndwbkf2 (npm)

MAL-2026-13783

Immediate action

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

npm uninstall bcnfjndwbkf2

What this malware does

The package contains only index.html and declares main: 'index.html' with no scripts, no bin, and no JavaScript library surface. The HTML mimics a Cloudflare 'Just a moment...' interstitial and, after a 1s timeout, runs obfuscator.io-style code that reconstructs a target URL from a rotated base64 string array (visible fragments include 'gin.microc' and '/') and calls window.location.replace() to it, forwarding current URL search params. Because main points at an HTML file, the package cannot be require()'d or import()'d, has no lifecycle hooks, and does not execute code on npm install. Installing or depending on this package does not run the redirector against the installer — the content only affects browser visitors who fetch the HTML via an npm CDN mirror (unpkg/jsdelivr). This is npm-as-static-host abuse for a browser-side redirect page rather than a supply-chain attack against 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)

7b5740dffc794b8911973e8fe1861f4bb3bf1185a727066bf2c9c9c9b661de99

5a1fc1ec45930a69372eadc47b662c5d82b247b5b4227feacda3d1c4302b4bf3

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bcnfjndwbkf2 (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 bcnfjndwbkf2 across your stack and pipelines.
If you installed it — respond
bcnfjndwbkf2 is a typosquat — you almost certainly intended a legitimately-named package. Remove bcnfjndwbkf2, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If bcnfjndwbkf2 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 bcnfjndwbkf2 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. bcnfjndwbkf2 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-7cv8-7v66-c3mhIN-MAL-2026-017535

References

Credits

Amazon Inspector · finder

Detect & block this

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