Which versions of bmgki3g6fh3 are malicious?

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

How do I remediate bmgki3g6fh3 if I installed it?

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

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

Yes — bmgki3g6fh3 is associated with the GHSA-wm4g-m94m-47vj, IN-MAL-2026-017545 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 bmgki3g6fh3 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 bmgki3g6fh3 (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 bmgki3g6fh3 across your stack and pipelines.

Malicious package

bmgki3g6fh3npm

bmgki3g6fh3 is a confirmed malicious npm package (MAL-2026-13789) 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 bmgki3g6fh3 (npm)

MAL-2026-13789

Immediate action

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

npm uninstall bmgki3g6fh3

What this malware does

The package contains a single file, index.html, declared as main. The page renders a spoofed Cloudflare 'Just a moment...' / Turnstile 'security verification' interstitial (fake Ray ID alongside a real Turnstile widget) and, on completion, runs an obfuscator.io-wrapped script that assembles a URL starting with 'https://lo' + decoded fragments + '/', appends the current query string, and navigates window.location to it. No install lifecycle scripts (preinstall/install/postinstall/prepare) are declared and main points at a non-JS file, so npm install and require() do not execute any code on a developer machine or build system. The hostile behavior only manifests if a browser is pointed at index.html. This is registry abuse for hosting phishing/redirect infrastructure 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)

e3d6efa965e641c0214a21386f396171e4422a00a3d4445180197706fe77d065

9212dc22bc5983b7b163b7851e76596bda812485709581a8dd61475630db4450

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 bmgki3g6fh3 (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 bmgki3g6fh3 across your stack and pipelines.
If you installed it — respond
Remove bmgki3g6fh3 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 bmgki3g6fh3 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 bmgki3g6fh3 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. bmgki3g6fh3 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-wm4g-m94m-47vjIN-MAL-2026-017545

References

Credits

Amazon Inspector · finder

Detect & block this

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