Critical Malicious Code Vulnerability in vite-log-plugin

vite-log-plugin Updated 02 Oct 2025

Summary

30/07/2025
CRITICAL
No i
Critical
Not published

MAL-2025-6376: Malicious code in vite-log-plugin (npm). Affected versions are not published. 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

vite-log-plugin is an npm package designed to enhance logging capabilities in Vite applications. It allows developers to easily manage and format log outputs, improving debugging and monitoring processes. However, this package has been compromised, embedding malicious code that poses significant security risks to any system using it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the vite-log-plugin package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code is classified under CWE-506, indicating that it appears to be intentionally harmful. Users are advised to treat any system with this package as potentially compromised, as the removal of the package may not eliminate all traces of the malicious software.

How To Fix

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

npm uninstall vite-log-plugin

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 workaround, you can replace the vite-log-plugin with alternative logging packages that do not have known vulnerabilities. Ensure to review the security status of any new packages before installation.

Conclusion

The vite-log-plugin package has been identified as containing malicious code that poses severe security risks. Users are strongly advised to uninstall the package immediately and monitor their systems for any signs of compromise. Utilizing tools like Vulert can help maintain awareness of vulnerabilities in open-source software.

See every vulnerability recorded for vite-log-plugin →

Share this vulnerability

FAQ

Immediately uninstall the package using 'npm uninstall vite-log-plugin' and rotate any secrets or keys stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without needing to sign up.

Keeping vite-log-plugin installed can lead to unauthorized access to sensitive data, potentially compromising your entire system.

The best mitigation is to uninstall the package and replace it with a secure alternative. Regularly monitor your dependencies for vulnerabilities.

Vulert uses your package-lock.json to monitor for vulnerabilities in real-time, providing alerts and insights without requiring access to your code.

How To Fix

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

npm uninstall vite-log-plugin

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