Critical Security Breach in v-plausible: Malicious Code Injection Detected

v-plausible Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191445: Malicious code in v-plausible (npm). Affects v-plausible versions 1.2.1. 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

v-plausible is an npm package designed for tracking and analyzing user interactions in web applications. It provides developers with insights into user behavior, enabling them to make informed decisions about their applications. However, the package has recently been compromised, exposing users to significant security risks.

Vulnerability Detail

The vulnerability stems from a malicious code injection introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal sensitive 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 malicious payload poses a risk of destroying the user's home directory, leading to potential data loss.

How To Fix

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

npm uninstall v-plausible

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, users can remove the v-plausible package from their project until a secure version is confirmed. This can be done using the command: npm uninstall v-plausible. Additionally, review your GitHub actions and remove any unauthorized scripts or actions that may have been introduced by the worm.

Conclusion

The v-plausible package has been compromised by a malicious worm, posing serious security risks to users. Immediate action is required to update or remove the package to protect sensitive information and maintain the integrity of your applications. Utilize tools like Vulert to monitor for vulnerabilities in your projects.

See every vulnerability recorded for v-plausible →

Share this vulnerability

FAQ

v-plausible is an npm package that helps developers track user interactions within web applications, providing valuable insights for improving user experience.

The vulnerability was introduced by a malicious npm worm that compromised the package, allowing it to steal sensitive information and propagate itself.

If you have installed v-plausible, you should immediately update to the latest patched version or uninstall the package to mitigate risks.

Yes, the worm can propagate to other npm packages owned by the user, making it crucial to address the vulnerability promptly.

You can use Vulert, which monitors and alerts in real-time for open-source vulnerabilities using just your package-lock.json. You can also check your application for vulnerabilities using the Vulert playground without any signup.

How To Fix

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

npm uninstall v-plausible

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