Which versions of bgzxcuite2 are malicious?

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

How do I remediate bgzxcuite2 if I installed it?

bgzxcuite2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

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

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

Yes — bgzxcuite2 is associated with the GHSA-35pm-fj6m-m6v6, IN-MAL-2026-017498 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 bgzxcuite2 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 bgzxcuite2 (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 bgzxcuite2 across your stack and pipelines.

Malicious package

bgzxcuite2npm

bgzxcuite2 is a confirmed malicious npm package (MAL-2026-13785) that steals credentials and exfiltrates sensitive data (malicious version 1.0.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in bgzxcuite2 (npm)

MAL-2026-13785

Immediate action

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

npm uninstall bgzxcuite2

What this malware does

Package's main entry is index.html, a page styled as a Cloudflare Turnstile challenge. The inline script is obfuscator.io-obfuscated and, after the Turnstile widget completes, reconstructs a URL from an encoded string array and calls window.location.replace to redirect the browser. package.json declares no preinstall/install/postinstall/prepare lifecycle hooks and there is no JavaScript entry point, so npm install and require()/import of this package do not execute the payload; the redirect only fires if a user opens the HTML file in a browser. The behavior is inconsistent with a normal npm library and is consistent with using npm as a hosting channel for a browser-side redirect (phishing/traffic-monetization shape), but it does not attack the installer's machine, filesystem, environment, credentials, or network at install or require time.

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)

07d4731411678cd400fb21afdeb55e0da60073c177c3b98f381cb2ab56314176

dc7e4c75a05788e3a757fe3ce7fc683bac9c90d12967dcf8430986799bc58fb8

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for bgzxcuite2 (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 bgzxcuite2 across your stack and pipelines.
If you installed it — respond
bgzxcuite2 is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If bgzxcuite2 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 bgzxcuite2 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. bgzxcuite2 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-35pm-fj6m-m6v6IN-MAL-2026-017498

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks bgzxcuite2-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database