VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

zapier-platform-cli: vulnerability history, versions and safety

zapier-platform-cli 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 zapier-platform-cli vulnerabilities

Vulert verdict on zapier-platform-cli 19.2.1 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for zapier-platform-cli 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 Niche
  • 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 19.2.1 — 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 562 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence non-standard 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 zapier-platform-cli, 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
19.2.1 14 Oct 2026 C1 malicious non-standard No Details →
19.2.0 07 Oct 2026 C1 malicious non-standard No Details →
19.1.0 30 Jul 2026 C1 malicious non-standard No Details →
19.0.0 18 May 2026 C1 malicious non-standard No Details →
18.6.0 05 May 2026 C1 malicious non-standard No Details →
18.5.1 30 Apr 2026 C1 malicious non-standard No Details →
18.5.0 16 Apr 2026 C1 malicious non-standard No Details →
18.4.0 06 Apr 2026 C1 malicious non-standard No Details →
18.3.0 13 Mar 2026 C1 malicious non-standard No Details →
18.2.3 04 Mar 2026 C1 malicious non-standard No Details →
18.2.2 26 Feb 2026 C1 malicious non-standard No Details →
18.2.1 23 Feb 2026 C1 malicious non-standard No Details →
18.2.0 18 Feb 2026 C1 malicious non-standard No Details →
18.1.1 29 Jan 2026 C1 malicious non-standard No Details →
18.1.0 20 Jan 2026 C1 malicious non-standard No Details →
18.0.7 06 Jan 2026 C1 malicious non-standard No Details →
18.0.6 24 Dec 2025 C1 malicious non-standard No Details →
18.0.5 10 Dec 2025 C1 malicious non-standard No Details →
18.0.1 05 Nov 2025 C1 malicious non-standard No Details →
18.0.0 30 Oct 2025 C1 malicious non-standard No Details →
17.9.1 28 Oct 2025 C1 malicious non-standard No Details →
17.9.0 20 Oct 2025 C1 malicious non-standard No Details →
17.8.0 07 Oct 2025 C1 malicious non-standard No Details →
17.7.2 17 Sep 2025 C1 malicious non-standard No Details →
17.7.1 10 Sep 2025 C1 malicious non-standard No Details →
17.7.0 22 Aug 2025 C1 malicious non-standard No Details →
17.6.0 11 Aug 2025 C1 malicious non-standard No Details →
17.5.0 30 Jul 2025 C1 malicious non-standard No Details →
17.4.0 23 Jul 2025 C1 malicious non-standard No Details →
17.3.1 17 Jul 2025 C1 malicious non-standard No Details →
17.3.0 01 Jul 2025 C1 malicious non-standard No Details →
17.2.0 11 Jun 2025 C1 malicious non-standard No Details →
17.1.0 10 Jun 2025 C1 malicious non-standard No Details →
17.0.4 03 Jun 2025 C1 malicious non-standard No Details →
17.0.3 30 May 2025 C1 malicious non-standard No Details →
17.0.2 19 May 2025 C1 malicious non-standard No Details →
17.0.1 15 May 2025 C1 malicious non-standard No Details →
17.0.0 12 May 2025 C1 malicious non-standard No Details →
16.5.1 08 May 2025 C1 malicious non-standard No Details →
16.5.0 10 Apr 2025 C1 malicious non-standard No Details →
16.4.0 08 Apr 2025 C1 malicious non-standard No Details →
16.3.1 27 Feb 2025 C1 malicious non-standard No Details →
16.3.0 30 Jan 2025 C1 malicious non-standard No Details →
16.2.0 21 Jan 2025 C1 malicious non-standard No Details →
16.1.1 13 Jan 2025 C1 malicious non-standard No Details →
16.1.0 09 Jan 2025 C1 malicious non-standard No Details →
16.0.0 16 Dec 2024 C1 malicious non-standard No Details →
15.19.0 25 Nov 2024 C1 malicious non-standard No Details →
15.18.1 01 Nov 2024 C1 malicious non-standard No Details →
15.18.0 24 Oct 2024 C1 malicious non-standard No Details →
15.17.0 11 Oct 2024 C1 malicious non-standard No Details →
15.16.1 04 Oct 2024 C1 malicious non-standard No Details →
15.16.0 24 Sep 2024 C1 malicious non-standard No Details →
15.15.0 18 Sep 2024 C1 malicious non-standard No Details →
15.14.2 18 Sep 2024 C1 malicious non-standard No Details →
15.14.1 16 Sep 2024 C1 malicious non-standard No Details →
15.14.0 28 Aug 2024 C1 malicious non-standard No Details →
15.13.0 21 Aug 2024 C1 malicious non-standard No Details →
15.12.0 16 Aug 2024 C1 malicious non-standard No Details →
15.11.1 19 Jul 2024 C1 malicious non-standard No Details →
15.11.0 16 Jul 2024 C1 malicious non-standard No Details →
15.10.0 02 Jul 2024 C1 malicious non-standard No Details →
15.9.1 27 Jun 2024 C1 malicious non-standard No Details →
15.9.0 27 Jun 2024 C1 malicious non-standard No Details →
15.8.0 13 Jun 2024 C1 malicious non-standard No Details →
15.7.3 27 May 2024 C1 malicious non-standard No Details →
15.7.2 08 May 2024 C1 malicious non-standard No Details →
15.7.1 01 May 2024 C1 malicious non-standard No Details →
15.7.0 09 Apr 2024 C1 malicious non-standard No Details →
15.6.2 03 Apr 2024 C1 malicious non-standard No Details →
15.6.1 28 Mar 2024 C1 malicious non-standard No Details →
15.6.0 26 Mar 2024 C1 malicious non-standard No Details →
15.5.3 08 Feb 2024 C1 malicious non-standard No Details →
15.5.2 06 Feb 2024 C1 malicious non-standard No Details →
15.5.1 21 Nov 2023 C1 malicious non-standard No Details →
15.5.0 09 Nov 2023 C1 malicious non-standard No Details →
15.4.2 01 Nov 2023 C1 malicious non-standard No Details →
15.4.1 06 Oct 2023 C1 malicious non-standard No Details →
15.4.0 06 Oct 2023 C1 malicious non-standard No Details →
15.3.0 19 Sep 2023 C1 malicious non-standard No Details →
15.2.0 07 Sep 2023 C1 malicious non-standard No Details →
15.1.0 07 Sep 2023 C1 malicious non-standard No Details →
15.0.1 10 Jul 2023 C1 malicious non-standard No Details →
15.0.0 15 Jun 2023 C1 malicious non-standard No Details →
14.1.2 07 Jun 2023 C1 malicious non-standard No Details →
14.1.1 07 Jun 2023 C1 malicious non-standard No Details →
14.1.0 01 Jun 2023 C1 malicious non-standard No Details →
14.0.1 22 May 2023 C1 malicious non-standard No Details →
14.0.0 21 Mar 2023 C1 malicious non-standard No Details →
13.0.0 25 Jan 2023 C1 malicious non-standard No Details →
12.2.1 18 Jan 2023 C1 malicious non-standard No Details →
12.2.0 27 Oct 2022 C1 malicious non-standard No Details →
12.1.0 29 Sep 2022 C1 malicious non-standard No Details →
12.0.3 29 Apr 2022 C1 malicious non-standard No Details →
12.0.2 30 Mar 2022 C1 malicious non-standard No Details →
12.0.1 24 Mar 2022 C1 malicious non-standard No Details →
12.0.0 23 Mar 2022 C1 malicious non-standard No Details →
9.7.3 22 Mar 2022 C1 malicious non-standard No Details →
11.3.3 22 Mar 2022 C1 malicious non-standard No Details →
11.3.2 01 Mar 2022 C1 malicious non-standard No Details →
9.7.2 01 Mar 2022 C1 malicious — No Details →
11.3.1 23 Feb 2022 C1 malicious — No Details →
9.7.1 23 Feb 2022 C1 malicious — No Details →
9.7.0 14 Feb 2022 C1 malicious — No Details →
11.3.0 14 Feb 2022 C1 malicious — No Details →
9.6.0 03 Dec 2021 C1 malicious — No Details →
11.2.0 03 Dec 2021 C1 malicious — No Details →
11.1.1 24 Sep 2021 C1 malicious — No Details →
11.1.0 05 Aug 2021 C1 malicious — No Details →
9.5.0 02 Jul 2021 C1 malicious — No Details →
11.0.1 28 May 2021 C1 malicious — No Details →
11.0.0 12 May 2021 C1 malicious — No Details →
10.2.0 23 Feb 2021 C1 malicious — No Details →
10.1.3 09 Feb 2021 C1 malicious — No Details →
9.4.2 09 Feb 2021 C1 malicious — No Details →
10.1.2 30 Oct 2020 C1 malicious — No Details →
10.1.1 02 Sep 2020 C1 malicious — No Details →
10.1.0 31 Aug 2020 C1 malicious — No Details →
10.0.1 20 Jul 2020 C1 malicious — No Details →
10.0.0 20 May 2020 C1 malicious — No Details →

The newest 120 of 209 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 zapier-platform-cli

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 zapier-platform-cli 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 zapier-platform-cli

Is zapier-platform-cli safe to use?

No. Vulert records a malicious-package vulnerability for zapier-platform-cli: 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 zapier-platform-cli's Vulert package health score?

Vulert scores zapier-platform-cli 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 zapier-platform-cli affected?

Yes. 19.2.1, 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 zapier-platform-cli have?

1 vulnerability is recorded for zapier-platform-cli 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 zapier-platform-cli vulnerabilities disclosed?

1 vulnerability was recorded for zapier-platform-cli 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 zapier-platform-cli 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 zapier-platform-cli for upcoming vulnerabilities?

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