Critical Malicious Code Vulnerability in @posthog/plugin-contrib Package
Summary
MAL-2025-190751: Malicious code in @posthog/plugin-contrib (npm). Affects @posthog/plugin-contrib versions 0.0.6. No fix is published. How to fix ↓
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.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
The @posthog/plugin-contrib package is a collection of plugins designed for use with PostHog, a product analytics platform that helps teams understand user behavior. This package allows developers to extend PostHog's functionality with custom plugins. However, it has been found to contain malicious code that compromises the security of systems using it.
Vulnerability Detail
The vulnerability originates from a malicious code embedded within version 0.0.6 of the @posthog/plugin-contrib package. This code can fully compromise any computer where the package is installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are severe, as it may lead to data breaches and loss of control over the affected systems.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall @posthog/plugin-contribIf 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
There are no effective workarounds for this vulnerability other than removing the package and securing the system. It is recommended to monitor your systems for any unusual activity following the removal of the package.
Conclusion
The discovery of malicious code in the @posthog/plugin-contrib package poses a significant security risk. Immediate action is required to remove the package and secure any compromised systems. Regular monitoring and updates are essential to maintain the integrity of your software environment.
See every vulnerability recorded for @posthog/plugin-contrib →
FAQ
Immediately remove the package and rotate all secrets and keys stored on the affected system.
You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.
As of now, there is no patched version available. The best course of action is to remove the package.
Failing to address this vulnerability can lead to unauthorized access to sensitive data and potential data breaches.
Yes, but ensure that they are not affected by similar vulnerabilities. Always verify the integrity of third-party packages before installation.
References
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
