Critical Malicious Code Vulnerability in @posthog/heartbeat-plugin: Token Theft and Home Directory Destruction

@posthog/heartbeat-plugin Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191291: Malicious code in @posthog/heartbeat-plugin (npm). Affects @posthog/heartbeat-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 Your last release was probably never penetration tested 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/heartbeat-plugin is an npm package designed to enhance the functionality of PostHog, a product analytics platform. This plugin allows developers to track user interactions and gather insights into product usage. However, it has recently been compromised, exposing users to significant security risks due to malicious code embedded within the package.

Vulnerability Detail

The vulnerability originates from the Sha1-Hulud: The Second Coming NPM worm, which has compromised the @posthog/heartbeat-plugin package. This malicious payload is capable of stealing sensitive tokens and credentials, subsequently publishing them to GitHub. Additionally, the worm can propagate itself to other npm packages owned by the user and may establish persistence through a GitHub action. The malicious code also poses a risk of destroying 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/heartbeat-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, it is advisable to remove the compromised package from your project until a secure version is released. You can do this by executing the following command: npm uninstall @posthog/heartbeat-plugin. Additionally, monitor your GitHub repositories for any unauthorized changes or actions.

Conclusion

The @posthog/heartbeat-plugin has been compromised by a malicious worm that poses serious security risks, including token theft and home directory destruction. Users are urged to update or uninstall the package immediately and monitor their systems for any unauthorized activity.

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

Share this vulnerability

FAQ

The vulnerability involves malicious code that steals 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 your application without needing to sign up.

If you have installed version 0.0.8 of the @posthog/heartbeat-plugin, it is recommended to uninstall it immediately and check for updates or patches.

Yes, the malicious code can propagate to other npm packages owned by the user, increasing the risk of widespread compromise.

Consequences include unauthorized access to sensitive information, potential data loss, and the risk of further propagation of the malicious code.

How To Fix

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

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