VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@posthog/agent: vulnerability history, versions and safety

@posthog/agent 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 @posthog/agent vulnerabilities

Vulert verdict on @posthog/agent 2.4.290 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @posthog/agent 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 Key ecosystem project
  • 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.4.290 — 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
  • Stars 40,288 i
  • OpenSSF scorecard 3/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 @posthog/agent, 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.4.290 22 Oct 2026 C1 malicious MIT No Details →
2.4.289 22 Oct 2026 C1 malicious MIT No Details →
2.4.288 22 Oct 2026 C1 malicious MIT No Details →
2.4.287 22 Oct 2026 C1 malicious MIT No Details →
2.4.286 21 Oct 2026 C1 malicious MIT No Details →
2.4.285 21 Oct 2026 C1 malicious MIT No Details →
2.4.284 21 Oct 2026 C1 malicious MIT No Details →
2.4.283 21 Oct 2026 C1 malicious MIT No Details →
2.4.282 20 Oct 2026 C1 malicious MIT No Details →
2.4.281 20 Oct 2026 C1 malicious MIT No Details →
2.4.280 20 Oct 2026 C1 malicious MIT No Details →
2.4.279 19 Oct 2026 C1 malicious MIT No Details →
2.4.277 16 Oct 2026 C1 malicious MIT No Details →
2.4.275 14 Oct 2026 C1 malicious MIT No Details →
2.4.274 14 Oct 2026 C1 malicious MIT No Details →
2.4.273 14 Oct 2026 C1 malicious MIT No Details →
2.4.272 14 Oct 2026 C1 malicious MIT No Details →
2.4.271 14 Oct 2026 C1 malicious MIT No Details →
2.4.270 14 Oct 2026 C1 malicious MIT No Details →
2.4.268 14 Oct 2026 C1 malicious MIT No Details →
2.4.267 13 Oct 2026 C1 malicious MIT No Details →
2.4.266 13 Oct 2026 C1 malicious MIT No Details →
2.4.265 13 Oct 2026 C1 malicious MIT No Details →
2.4.264 13 Oct 2026 C1 malicious MIT No Details →
2.4.263 13 Oct 2026 C1 malicious MIT No Details →
2.4.262 12 Oct 2026 C1 malicious MIT No Details →
2.4.261 12 Oct 2026 C1 malicious MIT No Details →
2.4.260 12 Oct 2026 C1 malicious MIT No Details →
2.4.259 12 Oct 2026 C1 malicious MIT No Details →
2.4.258 09 Oct 2026 C1 malicious MIT No Details →
2.4.257 08 Oct 2026 C1 malicious MIT No Details →
2.4.256 02 Oct 2026 C1 malicious MIT No Details →
2.4.255 02 Oct 2026 C1 malicious MIT No Details →
2.4.254 02 Oct 2026 C1 malicious MIT No Details →
2.4.253 02 Oct 2026 C1 malicious MIT No Details →
2.4.252 01 Oct 2026 C1 malicious MIT No Details →
2.4.250 01 Oct 2026 C1 malicious MIT No Details →
2.4.249 01 Oct 2026 C1 malicious MIT No Details →
2.4.248 01 Oct 2026 C1 malicious MIT No Details →
2.4.247 01 Oct 2026 C1 malicious MIT No Details →
2.4.246 01 Oct 2026 C1 malicious MIT No Details →
2.4.244 30 Sep 2026 C1 malicious MIT No Details →
2.4.243 30 Sep 2026 C1 malicious MIT No Details →
2.4.241 30 Sep 2026 C1 malicious MIT No Details →
2.4.240 30 Sep 2026 C1 malicious MIT No Details →
2.4.239 30 Sep 2026 C1 malicious MIT No Details →
2.4.238 30 Sep 2026 C1 malicious MIT No Details →
2.4.237 30 Sep 2026 C1 malicious MIT No Details →
2.4.236 30 Sep 2026 C1 malicious MIT No Details →
2.4.235 29 Sep 2026 C1 malicious MIT No Details →
2.4.234 29 Sep 2026 C1 malicious MIT No Details →
2.4.233 28 Sep 2026 C1 malicious MIT No Details →
2.4.232 28 Sep 2026 C1 malicious MIT No Details →
2.4.231 28 Sep 2026 C1 malicious MIT No Details →
2.4.230 28 Sep 2026 C1 malicious MIT No Details →
2.4.229 28 Sep 2026 C1 malicious MIT No Details →
2.4.228 28 Sep 2026 C1 malicious MIT No Details →
2.4.227 28 Sep 2026 C1 malicious MIT No Details →
2.4.225 25 Sep 2026 C1 malicious MIT No Details →
2.4.224 24 Sep 2026 C1 malicious MIT No Details →
2.4.223 24 Sep 2026 C1 malicious MIT No Details →
2.4.220 24 Sep 2026 C1 malicious MIT No Details →
2.4.219 24 Sep 2026 C1 malicious MIT No Details →
2.4.218 24 Sep 2026 C1 malicious MIT No Details →
2.4.217 23 Sep 2026 C1 malicious MIT No Details →
2.4.216 23 Sep 2026 C1 malicious MIT No Details →
2.4.215 23 Sep 2026 C1 malicious MIT No Details →
2.4.214 23 Sep 2026 C1 malicious MIT No Details →
2.4.213 23 Sep 2026 C1 malicious MIT No Details →
2.4.212 22 Sep 2026 C1 malicious MIT No Details →
2.4.211 22 Sep 2026 C1 malicious MIT No Details →
2.4.210 22 Sep 2026 C1 malicious MIT No Details →
2.4.209 22 Sep 2026 C1 malicious MIT No Details →
2.4.208 22 Sep 2026 C1 malicious MIT No Details →
2.4.197 21 Sep 2026 C1 malicious MIT No Details →
2.4.195 21 Sep 2026 C1 malicious MIT No Details →
2.4.194 21 Sep 2026 C1 malicious MIT No Details →
2.4.193 21 Sep 2026 C1 malicious MIT No Details →
2.4.192 18 Sep 2026 C1 malicious MIT No Details →
2.4.191 18 Sep 2026 C1 malicious MIT No Details →
2.4.190 18 Sep 2026 C1 malicious MIT No Details →
2.4.189 17 Sep 2026 C1 malicious MIT No Details →
2.4.188 17 Sep 2026 C1 malicious MIT No Details →
2.4.187 16 Sep 2026 C1 malicious MIT No Details →
2.4.186 15 Sep 2026 C1 malicious MIT No Details →
2.4.185 15 Sep 2026 C1 malicious MIT No Details →
2.4.184 14 Sep 2026 C1 malicious MIT No Details →
2.4.183 14 Sep 2026 C1 malicious MIT No Details →
2.4.182 14 Sep 2026 C1 malicious MIT No Details →
2.4.180 14 Sep 2026 C1 malicious MIT No Details →
2.4.179 14 Sep 2026 C1 malicious MIT No Details →
2.4.178 14 Sep 2026 C1 malicious MIT No Details →
2.4.177 14 Sep 2026 C1 malicious MIT No Details →
2.4.176 13 Sep 2026 C1 malicious MIT No Details →
2.4.175 11 Sep 2026 C1 malicious MIT No Details →
2.4.174 11 Sep 2026 C1 malicious MIT No Details →
2.4.173 10 Sep 2026 C1 malicious MIT No Details →
2.4.172 10 Sep 2026 C1 malicious MIT No Details →
2.4.171 10 Sep 2026 C1 malicious MIT No Details →
2.4.170 10 Sep 2026 C1 malicious MIT No Details →
2.4.169 10 Sep 2026 C1 malicious — No Details →
2.4.168 10 Sep 2026 C1 malicious — No Details →
2.4.167 10 Sep 2026 C1 malicious — No Details →
2.4.166 09 Sep 2026 C1 malicious — No Details →
2.4.165 09 Sep 2026 C1 malicious — No Details →
2.4.164 09 Sep 2026 C1 malicious — No Details →
2.4.163 09 Sep 2026 C1 malicious — No Details →
2.4.162 09 Sep 2026 C1 malicious — No Details →
2.4.161 09 Sep 2026 C1 malicious — No Details →
2.4.160 09 Sep 2026 C1 malicious — No Details →
2.4.159 09 Sep 2026 C1 malicious — No Details →
2.4.158 09 Sep 2026 C1 malicious — No Details →
2.4.157 08 Sep 2026 C1 malicious — No Details →
2.4.156 08 Sep 2026 C1 malicious — No Details →
2.4.155 08 Sep 2026 C1 malicious — No Details →
2.4.154 08 Sep 2026 C1 malicious — No Details →
2.4.153 07 Sep 2026 C1 malicious — No Details →
2.4.152 07 Sep 2026 C1 malicious — No Details →
2.4.151 07 Sep 2026 C1 malicious — No Details →
2.4.150 05 Sep 2026 C1 malicious — No Details →

The newest 120 of 678 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 @posthog/agent

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 @posthog/agent 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 @posthog/agent

Is @posthog/agent safe to use?

No. Vulert records a malicious-package vulnerability for @posthog/agent: 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 @posthog/agent's Vulert package health score?

Vulert scores @posthog/agent 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 @posthog/agent affected?

Yes. 2.4.290, 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 @posthog/agent have?

1 vulnerability is recorded for @posthog/agent 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 @posthog/agent vulnerabilities disclosed?

1 vulnerability was recorded for @posthog/agent 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 @posthog/agent 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 @posthog/agent for upcoming vulnerabilities?

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