Malicious Code Detected in @posthog/variance-plugin: Security Risk Alert

@posthog/variance-plugin Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190898: Malicious code in @posthog/variance-plugin (npm). Affects @posthog/variance-plugin versions 0.0.8. 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 @posthog/variance-plugin is an npm package designed to facilitate variance analysis in data-driven applications. It is utilized by developers to enhance their applications with statistical insights. However, recent findings have revealed that this package contains malicious code, posing a significant security threat to users and their applications.

Vulnerability Detail

The vulnerability originates from the package @posthog/variance-plugin, which was identified by Amazon Inspector. The malicious code embedded within this package can potentially compromise the integrity of applications that rely on it, leading to unauthorized access, data breaches, or other malicious activities. The specific version affected is 0.0.8, and it is crucial for users to be aware of the risks associated with using this package.

How To Fix

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

npm uninstall @posthog/variance-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, users can remove the @posthog/variance-plugin package from their project until a secure version is released. This can be done by executing the following command: 'npm uninstall @posthog/variance-plugin'.

Conclusion

The discovery of malicious code in the @posthog/variance-plugin package poses a serious threat to applications utilizing this npm package. Users are strongly advised to update or remove the package to mitigate potential risks. Utilizing tools like Vulert can help monitor for such vulnerabilities in real-time.

See every vulnerability recorded for @posthog/variance-plugin →

Share this vulnerability

FAQ

The malicious code can compromise application security, potentially leading to unauthorized access and data breaches.

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

Consider removing the package from your project as a temporary measure until a secure version is available.

Yes, the version 0.0.8 of @posthog/variance-plugin is known to contain the malicious code.

The vulnerability was reported by Amazon Inspector, which identified the malicious code in the package.

How To Fix

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

npm uninstall @posthog/variance-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