Critical Malicious Code Vulnerability in @posthog/ai Package

@posthog/ai Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190644: Malicious code in @posthog/ai (npm). Affects @posthog/ai versions 7.1.2. 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 Penetration testing for web, API and mobile 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/ai package is a JavaScript library used within the npm ecosystem, primarily aimed at enhancing analytics capabilities for applications. It provides tools for integrating artificial intelligence features into user interactions and data analysis. However, it has been found to contain malicious code that compromises the security of systems using it.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @posthog/ai package, identified as GHSA-mjv6-3w2m-7669. This code can lead to full system compromise, allowing unauthorized access to sensitive information such as secrets and keys stored on the affected machine. The malicious nature of the code means that simply removing the package may not eliminate all traces of the compromise, as control of the system may have been handed over to an external entity.

How To Fix

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

npm uninstall @posthog/ai

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

There are no effective workarounds for this vulnerability other than removing the package and rotating any compromised secrets. It is recommended to monitor the system for any unusual activity following the removal.

Conclusion

The discovery of malicious code in the @posthog/ai package poses a significant risk to any systems utilizing it. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help prevent future vulnerabilities by providing real-time monitoring and alerts.

See every vulnerability recorded for @posthog/ai →

Share this vulnerability

FAQ

Immediately remove the package and rotate any sensitive information stored on the affected system.

Look for unusual activity, unauthorized access attempts, or any changes to your system that you did not initiate.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, which can alert you to issues in real-time.

Vulert monitors open-source vulnerabilities in your software using just the package-lock.json file, providing real-time alerts without requiring code access.

Yes, you can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without any signup.

How To Fix

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

npm uninstall @posthog/ai

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