Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Malicious package

mbxcnsuwgs1npm

Advisory published Updated

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

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)

1dcbd9c1d41f7cb0f208e9d3a855f7b72b87b24e05fb0831554b57d5bfbe7a07
ea1e6265ca3ac7c399af2e8611eb6c59515fb95103387a132da4c2839311c09b

Detection & response playbook

Typosquat
  1. Find it

    Search your lockfiles and build artifacts for mbxcnsuwgs1 (version 1.0.0).

  2. 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.

  3. Did it already run?

    If mbxcnsuwgs1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

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-019278GHSA-4vx3-9fv9-qg2m

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.

Explore

mbxcnsuwgs1 (npm) malicious package — MAL-2026-15607 | O3 Security