Critical Malicious Code Vulnerability in @medusajs/analytics-posthog Package

@medusajs/analytics-posthog Updated 25 Nov 2025

Summary

24/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191456: Malicious code in @medusajs/analytics-posthog (npm). Affects @medusajs/analytics-posthog versions 2.11.4-preview-20251124060135 – 2.11.4-preview-20251124090208. 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 @medusajs/analytics-posthog package is a JavaScript library designed for integrating PostHog analytics into Medusa.js applications. It facilitates tracking user interactions and events, providing insights into user behavior. However, recent findings have revealed that this package contains malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the presence of embedded malicious code within the @medusajs/analytics-posthog package. This code can compromise any computer that has the package installed, potentially allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of this code is classified under CWE-506, indicating that it appears to be intentionally harmful. Users are advised to treat any system running this package as fully compromised.

How To Fix

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

npm uninstall @medusajs/analytics-posthog

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, users should uninstall the @medusajs/analytics-posthog package using the command: npm uninstall @medusajs/analytics-posthog. Additionally, ensure that all sensitive information is secured and rotated to prevent unauthorized access.

Conclusion

The discovery of malicious code within the @medusajs/analytics-posthog package poses a serious threat to users and their systems. Immediate action is required to mitigate risks, including uninstalling the package and securing sensitive information. Users are encouraged to stay informed about updates and potential patches.

See every vulnerability recorded for @medusajs/analytics-posthog →

Share this vulnerability

FAQ

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

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without requiring any signup.

Currently, there is no patch available for the malicious version of the package. The best course of action is to remove the package entirely.

Failure to address this vulnerability may result in unauthorized access to sensitive data and complete system compromise.

It is advisable to avoid using this package until a verified and secure version is released.

How To Fix

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

npm uninstall @medusajs/analytics-posthog

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