NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
Malicious package

@alexcolls/nuxt-uxnpm

Advisory published Updated

@alexcolls/nuxt-ux is a confirmed malicious npm package (MAL-2025-191186) that steals credentials and exfiltrates sensitive data (malicious versions 0.6.1, 0.6.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @alexcolls/nuxt-ux (npm)

MAL-2025-191186
Immediate action
Remove the package, then rotate any secrets the build/runtime could reach.
npm uninstall @alexcolls/nuxt-ux

What this malware does

The package @alexcolls/nuxt-ux was found to contain 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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

2 flagged
0.6.10.6.2

Indicators of compromise (SHA-256)

e220dc2f4107791df449396c0e19c2313708302524dec0aa5ebe4f99e192956d
8288b29fdb4a9d449ef3b6b0331e95c94898fd4456ea97f2b19965013fcd4661
b6d0dc43ee3b9d8d19d3d6a710804c3ea65f07046818a98a58990901d8f88d77

Detection & response playbook

Credential / info stealer
  1. Find it

    Search your lockfiles and build artifacts for @alexcolls/nuxt-ux (2 malicious versions).

  2. If you installed it — respond

    @alexcolls/nuxt-ux 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 @alexcolls/nuxt-ux 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. @alexcolls/nuxt-ux on npm has been identified as a malicious package (versions 0.6.1, 0.6.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-wfwg-6872-q985

References

Credits

  • Amazon Inspector · finder

Detect & block this

O3 blocks @alexcolls/nuxt-ux-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

@alexcolls/nuxt-ux (npm) malicious package — MAL-2025-191186 | O3 Security