VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@medusajs/analytics-posthog: vulnerability history, versions and safety

@medusajs/analytics-posthog is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Nov 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded C1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
1 in the last 12 months

Most recent disclosure 24 Nov 2025.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @medusajs/analytics-posthog vulnerabilities

Vulert verdict on @medusajs/analytics-posthog 2.22.0 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @medusajs/analytics-posthog is a malicious-package vulnerability — a published version contained hostile code rather than a bug. Do not install it, and check whether it is already resolved in your dependencies.

Package health score 15/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

The current release contains malicious code, which caps this score.

What to do: Do not install this package. If it is already in your dependency tree, remove or replace it, and check what resolved it in the first place. Vulert keeps watching the name: if a maintained replacement appears, you will see it here. Monitor it with Vulert →

  • Current release 2.22.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 24 Nov 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Depended on by 21 packages i
  • Stars 36,857 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for @medusajs/analytics-posthog, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.22.0 21 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261021091347 21 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261020204851 20 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261020140411 20 Oct 2026 C1 malicious MIT No Details →
2.22.0-preview-20261020134424 20 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261020130711 20 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261019210621 19 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261019163142 19 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261019151241 19 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261016081036 16 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261008225942 08 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261008220405 08 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261008144129 08 Oct 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20261006025321 06 Oct 2026 C1 malicious MIT No Details →
2.22.0-preview-20261002101246 02 Oct 2026 C1 malicious MIT No Details →
2.22.0-preview-20261002093930 02 Oct 2026 C1 malicious MIT No Details →
2.21.2 28 Sep 2026 C1 malicious MIT No Details →
2.21.2-snapshot-20260928075521 28 Sep 2026 C1 malicious MIT No Details →
2.21.2-snapshot-20260925150426 25 Sep 2026 C1 malicious MIT No Details →
2.21.2-preview-20260925133948 25 Sep 2026 C1 malicious MIT No Details →
2.21.1 22 Sep 2026 C1 malicious MIT No Details →
2.21.1-preview-20260922104932 22 Sep 2026 C1 malicious MIT No Details →
2.21.1-preview-20260922093132 22 Sep 2026 C1 malicious MIT No Details →
2.21.1-preview-20260922080739 22 Sep 2026 C1 malicious MIT No Details →
2.21.1-preview-20260921152858 21 Sep 2026 C1 malicious MIT No Details →
2.21.1-preview-20260918055502 18 Sep 2026 C1 malicious MIT No Details →
2.21.1-preview-20260917150924 17 Sep 2026 C1 malicious MIT No Details →
2.21.1-preview-20260916094546 16 Sep 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20260911212358 11 Sep 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20260911210440 11 Sep 2026 C1 malicious MIT No Details →
2.22.0-snapshot-20260911183712 11 Sep 2026 C1 malicious MIT No Details →
2.21.0-snapshot-20260911153132 11 Sep 2026 C1 malicious MIT No Details →
2.21.0 11 Sep 2026 C1 malicious MIT No Details →
2.21.0-preview-20260911072753 11 Sep 2026 C1 malicious MIT No Details →
2.21.0-snapshot-20260910110221 10 Sep 2026 C1 malicious MIT No Details →
2.21.0-snapshot-20260910075006 10 Sep 2026 C1 malicious MIT No Details →
2.21.0-snapshot-20260909235122 09 Sep 2026 C1 malicious MIT No Details →
2.21.0-snapshot-20260909165104 09 Sep 2026 C1 malicious MIT No Details →
2.21.0-snapshot-20260909143118 09 Sep 2026 C1 malicious MIT No Details →
2.20.2-snapshot-20260908153812 08 Sep 2026 C1 malicious MIT No Details →
2.20.2-snapshot-20260908125625 08 Sep 2026 C1 malicious MIT No Details →
2.20.2-snapshot-20260908025401 08 Sep 2026 C1 malicious MIT No Details →
2.20.2-snapshot-20260907141516 07 Sep 2026 C1 malicious MIT No Details →
2.20.2-preview-20260904113944 04 Sep 2026 C1 malicious MIT No Details →
2.20.2-preview-20260904091918 04 Sep 2026 C1 malicious MIT No Details →
2.20.1 03 Sep 2026 C1 malicious MIT No Details →
2.20.0 02 Sep 2026 C1 malicious MIT No Details →
2.20.0-preview-20260902142626 02 Sep 2026 C1 malicious MIT No Details →
2.20.0-preview-20260902090439 02 Sep 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260901131559 01 Sep 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260901111536 01 Sep 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260901110936 01 Sep 2026 C1 malicious MIT No Details →
2.20.0-preview-20260901102542 01 Sep 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260901095738 01 Sep 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260901091328 01 Sep 2026 C1 malicious MIT No Details →
2.20.0-preview-20260831100125 31 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260828133414 28 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260828124434 28 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260828123013 28 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260828085301 28 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260827165934 27 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260827112459 27 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260827110137 27 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260827104818 27 Aug 2026 C1 malicious MIT No Details →
2.20.0-preview-20260825203911 25 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260821203347 21 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260821130503 21 Aug 2026 C1 malicious MIT No Details →
2.20.0-preview-20260821111201 21 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260820212935 20 Aug 2026 C1 malicious MIT No Details →
2.20.0-preview-20260820152905 20 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260820121028 20 Aug 2026 C1 malicious MIT No Details →
2.20.0-snapshot-20260819163351 19 Aug 2026 C1 malicious MIT No Details →
2.20.0-preview-20260818191603 18 Aug 2026 C1 malicious MIT No Details →
2.20.0-preview-20260818141721 18 Aug 2026 C1 malicious MIT No Details →
2.19.1-snapshot-20260818122749 18 Aug 2026 C1 malicious MIT No Details →
2.19.1-preview-20260815080253 15 Aug 2026 C1 malicious MIT No Details →
2.19.1-snapshot-20260815055055 15 Aug 2026 C1 malicious MIT No Details →
2.19.1-snapshot-20260813214603 13 Aug 2026 C1 malicious MIT No Details →
2.19.1-preview-20260813160157 13 Aug 2026 C1 malicious MIT No Details →
2.19.1-preview-20260813144737 13 Aug 2026 C1 malicious MIT No Details →
2.19.0 13 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260813102506 13 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260812155528 12 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260812112149 12 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811191629 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811162321 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811161416 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811152815 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811152026 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811120905 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811115931 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-preview-20260811104048 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-preview-20260811102316 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811100009 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811095123 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260811075925 11 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260810131014 10 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260807103108 07 Aug 2026 C1 malicious MIT No Details →
2.19.0-snapshot-20260804104020 04 Aug 2026 C1 malicious MIT No Details →
2.19.0-preview-20260803001937 03 Aug 2026 C1 malicious MIT No Details →
2.18.0 23 Jul 2026 C1 malicious — No Details →
2.18.0-preview-20260717211441 17 Jul 2026 C1 malicious — No Details →
2.17.3-snapshot-20260710122216 10 Jul 2026 C1 malicious — No Details →
2.17.2 01 Jul 2026 C1 malicious — No Details →
2.17.1 25 Jun 2026 C1 malicious — No Details →
2.17.0 24 Jun 2026 C1 malicious — No Details →
2.16.0 18 Jun 2026 C1 malicious — No Details →
2.16.0-options-preview-20260605124754 05 Jun 2026 C1 malicious — No Details →
2.15.5 29 May 2026 C1 malicious — No Details →
2.15.3 21 May 2026 C1 malicious — No Details →
2.15.3-snapshot-20260515193434 15 May 2026 C1 malicious — No Details →
2.15.2 13 May 2026 C1 malicious — No Details →
2.15.1 11 May 2026 C1 malicious — No Details →
2.15.0 11 May 2026 C1 malicious — No Details →
2.14.2 30 Apr 2026 C1 malicious — No Details →
2.14.1 24 Apr 2026 C1 malicious — No Details →
2.14.0 23 Apr 2026 C1 malicious — No Details →
2.14.0-preview-20260421152527 21 Apr 2026 C1 malicious — No Details →
2.13.6 08 Apr 2026 C1 malicious — No Details →
2.13.5 25 Mar 2026 C1 malicious — No Details →

The newest 120 of 149 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 1 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @medusajs/analytics-posthog

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Malicious Code Vulnerability in @medusajs/analytics-posthog Package N/A critical No fix published 24 Nov 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 →

Questions

About @medusajs/analytics-posthog

Is @medusajs/analytics-posthog safe to use?

No. Vulert records a malicious-package vulnerability for @medusajs/analytics-posthog: a published version contained hostile code rather than a bug, and the package looks like one that was withdrawn for abuse. Do not install it, and check whether it is already resolved in your dependencies.

What is @medusajs/analytics-posthog's Vulert package health score?

Vulert scores @medusajs/analytics-posthog 15/100, which reads as critical. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release contains malicious code, which caps this score.

Is the latest version of @medusajs/analytics-posthog affected?

Yes. 2.22.0, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does @medusajs/analytics-posthog have?

1 vulnerability is recorded for @medusajs/analytics-posthog in the npm ecosystem: 1 critical, 0 high, 0 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new @medusajs/analytics-posthog vulnerabilities disclosed?

1 vulnerability was recorded for @medusajs/analytics-posthog in the last 12 months, and the oldest entry in this database dates to 24 Nov 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of @medusajs/analytics-posthog are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

What does a malicious-package vulnerability mean?

It means the published package itself contained hostile code — a backdoor, a credential stealer or similar — rather than only a bug. Registries remove such packages once they are confirmed, so treat any application that resolved an affected version as compromised and rotate the credentials it could reach.

How do I monitor @medusajs/analytics-posthog for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @medusajs/analytics-posthog version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.