Critical Vulnerability in nuxt-keycloak: Malicious Code Exposure

nuxt-keycloak Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191400: Malicious code in nuxt-keycloak (npm). Affects nuxt-keycloak versions 0.2.2. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

nuxt-keycloak is an npm package that integrates Keycloak authentication into Nuxt.js applications, providing a seamless way to manage user authentication and authorization. It is designed to enhance security in web applications by leveraging Keycloak's capabilities. However, this package has been compromised, exposing users to significant security risks.

Vulnerability Detail

The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected the nuxt-keycloak package. This malicious code is designed to steal tokens and credentials from users and publish them to GitHub. Additionally, it can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. The worm poses a severe risk as it may also destroy the user's home directory, leading to potential data loss and unauthorized access.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nuxt-keycloak

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary measure, users can remove the nuxt-keycloak package from their project until a secure version is released. This can be done using the command: 'npm uninstall nuxt-keycloak'. Additionally, consider using alternative authentication methods or libraries that are not affected by this vulnerability.

Conclusion

The nuxt-keycloak package has been compromised by a malicious worm, posing serious security risks to users. It is essential to take immediate action by updating or removing the package and monitoring for any further vulnerabilities. Utilizing tools like Vulert can help in maintaining the security of your applications.

See every vulnerability recorded for nuxt-keycloak →

Share this vulnerability

FAQ

nuxt-keycloak is an npm package that allows developers to integrate Keycloak authentication into their Nuxt.js applications, facilitating user management and security.

The worm introduces malicious code that steals user tokens and credentials, propagates to other packages, and can potentially destroy the user's home directory.

If you have installed nuxt-keycloak, it is crucial to uninstall the package immediately and monitor for any updates or patches from the maintainers.

Yes, you can use Vulert, which monitors and alerts for open-source vulnerabilities in your software using just package-lock.json. You can check your application for vulnerabilities without signing up at the Vulert playground.

Failing to address this vulnerability can lead to unauthorized access to sensitive user data, potential data loss, and the risk of further propagation of the malicious code to other packages.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall nuxt-keycloak

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback