Malicious Code Detected in posthog-node Package - Vulnerability Overview
Summary
MAL-2025-190925: Malicious code in posthog-node (npm). Affects posthog-node versions 4.18.1 – 5.13.3. 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
Background
The posthog-node package is a Node.js client for PostHog, an analytics platform that helps businesses understand user behavior. It provides functionalities for event tracking, user analytics, and data visualization. However, the package has been found to contain malicious code, posing significant risks to applications that rely on it.
Vulnerability Detail
The vulnerability originates from the posthog-node package, which has been identified to contain malicious code. This code could potentially allow attackers to execute unauthorized actions, compromise user data, or manipulate application behavior. The affected versions include 5.11.3, 5.13.3, and 4.18.1, making it critical for users of these versions to take immediate action to mitigate risks.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall posthog-nodeIf 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 remove the posthog-node package from your project until a secure version is confirmed. Use the following command to uninstall it: npm uninstall posthog-node.
Conclusion
The discovery of malicious code in the posthog-node package highlights the importance of monitoring and maintaining the security of open-source dependencies. Users should take immediate action to update or remove the affected package to safeguard their applications.
See every vulnerability recorded for posthog-node →
FAQ
The malicious code can execute unauthorized actions, potentially compromising user data and application integrity.
The affected versions include 5.11.3, 5.13.3, and 4.18.1.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Check your application using the Vulert playground at Vulert Scanner without any signup.
Consider removing the posthog-node package from your project as a temporary measure until a secure version is available.
The vulnerability was reported by Amazon Inspector, a service that helps identify security vulnerabilities in applications.
