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

gx-npm-uinpm

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

Malicious code in gx-npm-ui (npm)

MAL-2026-6481
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall gx-npm-ui

What this malware does

Package published at version 99.99.99 under the gx-npm-* namespace, a shape designed to win npm version resolution against private internal packages of the same name. package.json declares postinstall=node beacon.js, which runs unconditionally on npm install. beacon.js collects the installer's hostname, OS username, current working directory, package name, Node version, and the first 80 environment variable names, then exfiltrates them two ways to the hardcoded out-of-band host d8uectoqtvskhftsa940pm3kth3ahdxn4.oast.me: (1) a DNS lookup encoding the collected identifiers as subdomain labels, and (2) an HTTPS GET with a base64-encoded JSON payload in the query string. Any CI/build system or developer machine that resolves this package against the public npm registry leaks host identity and environment-variable names to an attacker-controlled interactsh/OAST endpoint on every install.

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
99.99.99

Indicators of compromise (SHA-256)

04e5ac6b8b24f2c158c37d3d6ac268bbf7f472433660064491538ee468cfcfcb
40016c94d5d31e1314b1f462b5fb83ae7ce15121df43474ce3440749ab89e72e

Detection & response playbook

Credential / info stealer
  1. Find it

    Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for gx-npm-ui (version 99.99.99). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging gx-npm-ui across your stack and pipelines.

  2. If you installed it — respond

    gx-npm-ui 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.

  3. Did it already run?

    If gx-npm-ui 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.

  4. How O3 protects you

    O3 blocks gx-npm-ui 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. gx-npm-ui on npm has been identified as a malicious package (version 99.99.99 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007559GHSA-5jpv-9x2f-72jj

References

Credits

  • Amazon Inspector · finder

Detect & block this

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

Explore

gx-npm-ui (npm) malicious package — MAL-2026-6481 | O3 Security