Which versions of nuxt-keycloak are malicious?

The following npm versions of nuxt-keycloak are flagged malicious: 0.2.2. Treat any of these as compromised.

How do I remediate nuxt-keycloak if I installed it?

nuxt-keycloak 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 nuxt-keycloak — how do I know if it already compromised me?

If nuxt-keycloak 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.

How do I find nuxt-keycloak across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for nuxt-keycloak (version 0.2.2).

Malicious package

nuxt-keycloaknpm

Advisory published Nov 25, 2025Updated Dec 1, 2025

nuxt-keycloak is a confirmed malicious npm package (MAL-2025-191400) that steals credentials and exfiltrates sensitive data (malicious version 0.2.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in nuxt-keycloak (npm)

MAL-2025-191400

Immediate action

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

npm uninstall nuxt-keycloak

What this malware does

The package nuxt-keycloak was found to contain malicious code.

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

1 flagged

0.2.2

Indicators of compromise (SHA-256)

644bc25c1f5c204d528cf906b446cbe6e1a365383f45ab8781ba6f7809da9f22

cbb088ab2b0e4b6991065c6bcdc57302ff545bb3fe2f2a73ec21fafeae1175f8

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for nuxt-keycloak (version 0.2.2).
If you installed it — respond
nuxt-keycloak 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 nuxt-keycloak 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. nuxt-keycloak on npm has been identified as a malicious package (version 0.2.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks nuxt-keycloak-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