Critical Malicious Code Vulnerability in @posthog/intercom-plugin: Token Theft and Home Directory Risk
Summary
MAL-2025-191293: Malicious code in @posthog/intercom-plugin (npm). Affects @posthog/intercom-plugin versions 0.0.8. 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/intercom-plugin is an npm package designed to integrate PostHog analytics with Intercom, enabling users to track and analyze customer interactions. This package is widely used for enhancing user engagement and understanding customer behavior. However, it has recently been compromised, exposing users to significant security risks.
Vulnerability Detail
The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has infected the @posthog/intercom-plugin package. This malicious code 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/intercom-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/intercom-plugin package from their project until a secure version is available. This can be done using the command: npm uninstall @posthog/intercom-plugin. Additionally, users should monitor their GitHub repositories for any unauthorized changes or actions.
Conclusion
The @posthog/intercom-plugin package has been compromised by a malicious NPM worm, posing serious security risks to users. It is essential to update the package immediately and monitor for any unauthorized changes in your projects. Utilizing tools like Vulert can help in identifying vulnerabilities in your applications.
See every vulnerability recorded for @posthog/intercom-plugin →
FAQ
The malicious code is designed to steal tokens and credentials, publish them to GitHub, and potentially destroy the user's home directory.
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 needing to sign up.
If you have installed the compromised version, you should immediately uninstall it and update to the latest patched version of the package.
Yes, the worm can propagate to other npm packages owned by the user, making it crucial to monitor all related packages.
Failure to address this vulnerability can lead to unauthorized access to sensitive information, data loss, and further propagation of the malicious code.