Which versions of mbxcnsuwgs1 are malicious?

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

How do I remediate mbxcnsuwgs1 if I installed it?

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

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

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

Yes — mbxcnsuwgs1 is associated with the IN-MAL-2026-019278 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 mbxcnsuwgs1 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 mbxcnsuwgs1 (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 mbxcnsuwgs1 across your stack and pipelines.

Malicious package

mbxcnsuwgs1npm

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

MAL-2026-15607

Immediate action

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

npm uninstall mbxcnsuwgs1

What this malware does

Published as part of a ClickFix-style fake-CAPTCHA phishing campaign documented by OX Security (see reference). The package's only file is index.html, declared as the npm "main" entry; package.json defines no preinstall/install/postinstall/prepare lifecycle script, so the payload does not execute at npm install time. index.html renders a fake Cloudflare Turnstile verification widget. An obfuscator.io-obfuscated inline script POSTs a hardcoded per-package "hostKey" to https://api.keyval.org/get, receives a base64-encoded IV:ciphertext pair, decrypts it client-side via the Web Crypto API (AES-CTR) using an embedded key to obtain a redirect URL, appends the visitor's original query-string parameters, and navigates the browser there via window.location.replace(). This "dead drop" design lets the operator change the phishing destination for every package sharing a hostKey without republishing to npm; OX Security observed keyval.org-served destinations including a typosquatted Microsoft login page and, at time of writing, a ChatGPT redirect. The package therefore does not attack the installing machine directly; it is used as a static file host on the npm CDN (e.g. unpkg/jsDelivr) so the index.html can be linked to and opened directly in a victim's browser as a phishing/ClickFix landing page. Published by npm user "johnvaldez9a" as part of a burst of near-identical single-purpose packages published between 2026-08-04 and 2026-08-24 that share this same fake-Turnstile-redirect page structure.

The package was found to contain malicious code or consuming dependency that contains malicious code

Malicious versions

1 flagged

1.0.0

Indicators of compromise (SHA-256)

1dcbd9c1d41f7cb0f208e9d3a855f7b72b87b24e05fb0831554b57d5bfbe7a07

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 mbxcnsuwgs1 (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 mbxcnsuwgs1 across your stack and pipelines.
If you installed it — respond
mbxcnsuwgs1 is a typosquat — you almost certainly intended a legitimately-named package. Remove mbxcnsuwgs1, 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 mbxcnsuwgs1 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 mbxcnsuwgs1 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. mbxcnsuwgs1 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

IN-MAL-2026-019278

References

Credits

Amazon Inspector · finder
OX Security · finder

Detect & block this

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