Critical Malicious Code Vulnerability in @posthog/agent Package

@posthog/agent Updated 24 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-190748: Malicious code in @posthog/agent (npm). Affects @posthog/agent versions 1.24.1. 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/agent package is a tool used for capturing and analyzing user interactions in web applications. It provides developers with insights into user behavior, enabling them to optimize their applications. However, this package has been compromised, leading to significant security concerns for any system utilizing it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code embedded within the @posthog/agent package, specifically version 1.24.1. This code can compromise any computer that has the package installed, potentially allowing an external entity to gain full control over the system. Users are advised to consider all secrets and keys stored on the affected computer as compromised and to take immediate action to secure their systems.

How To Fix

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

npm uninstall @posthog/agent

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 direct workarounds to mitigate the effects of this vulnerability other than removing the package entirely. Ensure that you monitor your system for any signs of compromise and take necessary security measures.

Conclusion

The @posthog/agent package has been identified as containing malicious code, posing a serious threat to any systems utilizing it. Immediate action is required to remove the package and secure any compromised secrets. Regular monitoring and security practices are essential to safeguard your applications.

See every vulnerability recorded for @posthog/agent →

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any secrets or keys stored on the affected system.

You can use Vulert to monitor and alert for vulnerabilities in your application. Visit Vulert Scanner to check if your application is affected without any signup.

Currently, there is no patched version available for the @posthog/agent package. The only solution is to remove the package.

Failure to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential loss of sensitive information.

After removal, ensure you rotate all secrets and keys, monitor your system for unusual activity, and consider enhancing your security measures.

How To Fix

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

npm uninstall @posthog/agent

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