Critical Malicious Code Vulnerability in @posthog/rrweb Package

@posthog/rrweb Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190673: Malicious code in @posthog/rrweb (npm). Affects @posthog/rrweb versions 0.0.31. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

The @posthog/rrweb package is a JavaScript library used for recording and replaying web sessions. It is commonly utilized in analytics and user experience research to capture user interactions on web applications. However, the package has been compromised, leading to severe security risks for any application that integrates it.

Vulnerability Detail

The vulnerability originates from malicious code embedded within the @posthog/rrweb package, specifically in version 0.0.31. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The implications of this vulnerability are significant, 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/rrweb

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 workaround, it is recommended to avoid using the @posthog/rrweb package altogether until a secure version is released. If you need similar functionality, consider exploring alternative libraries that do not have known vulnerabilities.

Conclusion

The @posthog/rrweb package has been compromised with malicious code, posing a significant security risk. Users are urged to uninstall the package and rotate any sensitive information immediately. Monitoring tools like Vulert can help ensure your application remains secure from such vulnerabilities.

See every vulnerability recorded for @posthog/rrweb →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information that may have been compromised.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without any signup.

No, there is currently no patched version available. The only solution is to remove the package entirely.

Failing to address this vulnerability could lead to unauthorized access to sensitive data and potential data breaches.

It is strongly advised to avoid using the @posthog/rrweb package until a secure version is released.

How To Fix

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

npm uninstall @posthog/rrweb

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