Malicious Code Detected in posthog-react-native Package - Critical Vulnerability Alert

posthog-react-native Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190926: Malicious code in posthog-react-native (npm). Affects posthog-react-native versions 4.11.1 – 4.12.5. 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

The posthog-react-native package is a library designed for integrating PostHog analytics into React Native applications. It provides developers with tools to track user interactions and gather insights about application usage. However, this package has been found to contain malicious code, posing significant risks to applications that utilize it.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the posthog-react-native package. This code can potentially compromise the security of applications using the library, leading to unauthorized access, data breaches, or other malicious activities. The affected versions are 4.12.5 and 4.11.1, as identified by Amazon Inspector.

How To Fix

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

npm uninstall posthog-react-native

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, consider removing the posthog-react-native package from your project until a secure version is released. You can do this by executing the following command: npm uninstall posthog-react-native.

Conclusion

The discovery of malicious code in the posthog-react-native package poses a serious threat to applications using this library. It is crucial for developers to take immediate action by updating to a secure version or removing the package to safeguard their applications.

See every vulnerability recorded for posthog-react-native →

Share this vulnerability

FAQ

The malicious code can potentially allow unauthorized access to sensitive data or enable other harmful activities within applications that use the package.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. By utilizing the Vulert playground, you can check if your application is affected without needing to sign up.

The affected versions of the posthog-react-native package are 4.12.5 and 4.11.1.

If immediate updates are not possible, consider removing the package as a temporary measure to mitigate risks until a secure version is available.

Detailed information about the vulnerability can be found in the official GitHub repository and through security advisories from trusted sources like Amazon Inspector.

How To Fix

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

npm uninstall posthog-react-native

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