Critical Security Breach in @livecms/nuxt-live-edit: Malicious Code Detected

@livecms/nuxt-live-edit Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191242: Malicious code in @livecms/nuxt-live-edit (npm). Affects @livecms/nuxt-live-edit versions 1.9.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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @livecms/nuxt-live-edit package is a tool designed for integrating live editing capabilities into Nuxt.js applications, enhancing the development experience by allowing real-time content updates. However, this package has been compromised, exposing users to severe security risks due to malicious code embedded within it.

Vulnerability Detail

The vulnerability originates from a compromise by the Sha1-Hulud: The Second Coming NPM worm, which has infiltrated the @livecms/nuxt-live-edit package. This malicious payload is capable of stealing sensitive tokens and credentials, subsequently publishing them to GitHub. Furthermore, the worm can propagate itself to other NPM packages owned by the user and establish persistence through a GitHub action. In extreme cases, it may even destroy the user's home directory, leading to significant data loss.

How To Fix

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

npm uninstall @livecms/nuxt-live-edit

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, you can remove the compromised package from your project by executing 'npm uninstall @livecms/nuxt-live-edit'. This will prevent the malicious code from executing until a secure version is available.

Conclusion

The @livecms/nuxt-live-edit package has been compromised by a malicious worm, posing serious security risks to users. It is essential to take immediate action by updating the package and monitoring for any further vulnerabilities. Utilizing tools like Vulert can help maintain the security of your applications.

See every vulnerability recorded for @livecms/nuxt-live-edit →

Share this vulnerability

FAQ

The malicious code is designed to steal tokens and credentials, potentially leading to unauthorized access to user accounts and data.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check your application without any signup.

Immediately uninstall the package using 'npm uninstall @livecms/nuxt-live-edit' and update to a secure version as soon as it is available.

Yes, the worm can propagate itself to other NPM packages owned by the user, increasing the risk of widespread compromise.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated to the latest secure versions.

How To Fix

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

npm uninstall @livecms/nuxt-live-edit

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