Critical Vulnerability in @posthog/filter-out-plugin: Malicious Code Injection

@posthog/filter-out-plugin Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191290: Malicious code in @posthog/filter-out-plugin (npm). Affects @posthog/filter-out-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/filter-out-plugin is an npm package designed to enhance data filtering capabilities within PostHog, a product analytics tool. This package allows users to customize and filter analytics data effectively. However, it has recently been compromised, exposing users to significant security risks due to malicious code embedded in the package.

Vulnerability Detail

The vulnerability stems from a compromise by the Sha1-Hulud: The Second Coming NPM worm, which has infected the @posthog/filter-out-plugin package. This malicious payload is designed to steal sensitive tokens and credentials from users and publish them to GitHub. Additionally, the worm can propagate itself to other NPM packages owned by the user and establish persistence through GitHub actions. There is also a risk that the worm may destroy 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 @posthog/filter-out-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 should consider removing the @posthog/filter-out-plugin package from their project until a secure version is released. This can be done using the following command: npm uninstall @posthog/filter-out-plugin. Additionally, monitor your system for any unauthorized access or changes.

Conclusion

The @posthog/filter-out-plugin has been compromised by a malicious NPM worm, posing serious security risks to users. Immediate action is required to update or remove the package to protect sensitive data and maintain system integrity. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for @posthog/filter-out-plugin →

Share this vulnerability

FAQ

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

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

If you have installed the compromised package, you should uninstall it immediately and monitor your system for any signs of unauthorized access.

Regularly update your dependencies, use tools like Vulert to monitor vulnerabilities, and review package sources before installation to mitigate risks.

Failure to address this vulnerability could lead to data breaches, loss of sensitive information, and unauthorized access to your systems.

How To Fix

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

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