VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@voiceflow/logger: vulnerability history, versions and safety

@voiceflow/logger 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 25 Nov 2025.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @voiceflow/logger vulnerabilities

Vulert verdict on @voiceflow/logger 2.10.0 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @voiceflow/logger 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 Little adoption
  • Community Not enough data

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.10.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 25 Nov 2025 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Last release 1 month ago i
  • Licence ISC 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 @voiceflow/logger, 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.10.1-83bf9d420.205 20 Oct 2026 C1 malicious ISC No Details →
2.10.1-4de6e78c6.200 20 Oct 2026 C1 malicious ISC No Details →
2.10.1-935a841ed.169 14 Oct 2026 C1 malicious ISC No Details →
2.10.1-557e1b19a.141 08 Oct 2026 C1 malicious ISC No Details →
2.10.1-4b72bbad1.120 06 Oct 2026 C1 malicious ISC No Details →
2.10.1-af2cec4ca.120 06 Oct 2026 C1 malicious ISC No Details →
2.10.1-900f0be35.120 06 Oct 2026 C1 malicious ISC No Details →
2.10.1-50443834c.90 01 Oct 2026 C1 malicious ISC No Details →
2.10.1-05ed8157c.87 01 Oct 2026 C1 malicious ISC No Details →
2.10.1-7181005ce.86 01 Oct 2026 C1 malicious ISC No Details →
2.10.1-455467aca.68 29 Sep 2026 C1 malicious ISC No Details →
2.10.1-81f8a94ed.56 28 Sep 2026 C1 malicious ISC No Details →
2.10.1-2f1b1b176.21 23 Sep 2026 C1 malicious ISC No Details →
2.10.0 21 Sep 2026 C1 malicious ISC No Details →
2.9.2-2cd8541c1.292 17 Sep 2026 C1 malicious ISC No Details →
2.9.2-0cfd62920.271 15 Sep 2026 C1 malicious ISC No Details →
2.9.2-7218199ca.274 15 Sep 2026 C1 malicious ISC No Details →
2.9.2-9abd7a91c.218 09 Sep 2026 C1 malicious ISC No Details →
2.9.2-d6b9acf49.208 09 Sep 2026 C1 malicious ISC No Details →
2.9.2-37eae40cc.198 07 Sep 2026 C1 malicious ISC No Details →
2.9.2-8877f9fde.159 02 Sep 2026 C1 malicious ISC No Details →
2.9.2-d2553920e.159 01 Sep 2026 C1 malicious ISC No Details →
2.9.2-3ac4e29a5.146 31 Aug 2026 C1 malicious ISC No Details →
2.9.2-a8dd51f6c.121 26 Aug 2026 C1 malicious ISC No Details →
2.9.2-d9e23a88b.110 25 Aug 2026 C1 malicious ISC No Details →
2.9.2-9161425f7.107 24 Aug 2026 C1 malicious ISC No Details →
2.9.2-18e7fac1f.107 24 Aug 2026 C1 malicious ISC No Details →
2.9.2-14629096e.107 24 Aug 2026 C1 malicious ISC No Details →
2.9.2-7c60e1c1c.92 21 Aug 2026 C1 malicious ISC No Details →
2.9.2-d51eb8100.45 18 Aug 2026 C1 malicious ISC No Details →
2.9.2-31dcfb0ee.35 18 Aug 2026 C1 malicious ISC No Details →
2.9.2-473138ad3.30 14 Aug 2026 C1 malicious ISC No Details →
2.9.2-0d581a647.29 14 Aug 2026 C1 malicious ISC No Details →
2.9.2-20b00802c.25 14 Aug 2026 C1 malicious ISC No Details →
2.9.2-286ee6878.15 14 Aug 2026 C1 malicious ISC No Details →
2.9.2-45e722f10.16 13 Aug 2026 C1 malicious ISC No Details →
2.9.2-8be175f4a.13 12 Aug 2026 C1 malicious ISC No Details →
2.9.2-9d13f215e.13 12 Aug 2026 C1 malicious ISC No Details →
2.9.2-63bebbd19.11 11 Aug 2026 C1 malicious ISC No Details →
2.9.1 07 Aug 2026 C1 malicious ISC No Details →
2.9.1-0958ecfba.29 06 Aug 2026 C1 malicious ISC No Details →
2.9.1-85b35f2ac.16 05 Aug 2026 C1 malicious ISC No Details →
2.9.0 31 Jul 2026 C1 malicious ISC No Details →
2.8.1-44d1953ca.272 29 Jul 2026 C1 malicious ISC No Details →
2.8.1-61cffa6e9.270 29 Jul 2026 C1 malicious ISC No Details →
2.8.1-31410eaa3.269 29 Jul 2026 C1 malicious ISC No Details →
2.8.1-ac6ac340f.267 28 Jul 2026 C1 malicious ISC No Details →
2.8.1-d21853e0b.247 24 Jul 2026 C1 malicious ISC No Details →
2.8.1-6a6e0aaae.243 24 Jul 2026 C1 malicious ISC No Details →
2.8.1-37baf0d6f.240 23 Jul 2026 C1 malicious ISC No Details →
2.8.1-a9da8c975.239 23 Jul 2026 C1 malicious ISC No Details →
2.8.1-71a9f5292.219 23 Jul 2026 C1 malicious ISC No Details →
2.8.1-522234f61.219 21 Jul 2026 C1 malicious ISC No Details →
2.8.1-149b636b6.212 20 Jul 2026 C1 malicious ISC No Details →
2.8.1-9c8a8bc07.208 17 Jul 2026 C1 malicious ISC No Details →
2.8.1-e08341f9e.208 15 Jul 2026 C1 malicious ISC No Details →
2.8.1-0d0ceae8a.198 14 Jul 2026 C1 malicious ISC No Details →
2.8.1-204d2f837.201 14 Jul 2026 C1 malicious ISC No Details →
2.8.1-c30a607a8.191 13 Jul 2026 C1 malicious ISC No Details →
2.8.1-4e34726a2.191 13 Jul 2026 C1 malicious ISC No Details →
2.8.1-1f8446414.194 13 Jul 2026 C1 malicious ISC No Details →
2.8.1-d980e8f79.193 13 Jul 2026 C1 malicious ISC No Details →
2.8.1-250c38671.192 13 Jul 2026 C1 malicious ISC No Details →
2.8.1-8653a925e.191 13 Jul 2026 C1 malicious ISC No Details →
2.8.1-19e77c4d6.181 13 Jul 2026 C1 malicious ISC No Details →
2.8.1-9519252b9.179 10 Jul 2026 C1 malicious ISC No Details →
2.8.1-e659287e2.172 09 Jul 2026 C1 malicious ISC No Details →
2.8.1-dffa73b39.165 08 Jul 2026 C1 malicious ISC No Details →
2.8.1-9be143f1b.164 08 Jul 2026 C1 malicious ISC No Details →
2.8.1-b54f1f017.161 08 Jul 2026 C1 malicious ISC No Details →
2.8.1-554258d75.155 07 Jul 2026 C1 malicious ISC No Details →
2.8.1-0b5cacae0.142 03 Jul 2026 C1 malicious ISC No Details →
2.8.1-137bbba41.140 03 Jul 2026 C1 malicious ISC No Details →
2.8.1-37d220d74.128 29 Jun 2026 C1 malicious ISC No Details →
2.8.1-e84d54a9e.121 29 Jun 2026 C1 malicious ISC No Details →
2.8.1-0cc996736.121 26 Jun 2026 C1 malicious ISC No Details →
2.8.1-fd95ff62f.101 25 Jun 2026 C1 malicious ISC No Details →
2.8.1-1c2d1b3a1.101 24 Jun 2026 C1 malicious ISC No Details →
2.8.1-85cfde6dc.101 24 Jun 2026 C1 malicious ISC No Details →
2.8.1-631f50d53.75 18 Jun 2026 C1 malicious ISC No Details →
2.8.1-1c11761a5.75 18 Jun 2026 C1 malicious ISC No Details →
2.8.1-83635a9a5.53 17 Jun 2026 C1 malicious ISC No Details →
2.8.1-bde66a870.67 16 Jun 2026 C1 malicious ISC No Details →
2.8.1-63e4c99c8.63 15 Jun 2026 C1 malicious ISC No Details →
2.8.1-a2bf814f0.63 15 Jun 2026 C1 malicious ISC No Details →
2.8.1-96b870fba.66 12 Jun 2026 C1 malicious ISC No Details →
2.8.1-615e16f0e.65 12 Jun 2026 C1 malicious ISC No Details →
2.8.1-b8cd1f6db.61 12 Jun 2026 C1 malicious ISC No Details →
2.8.1-95bc38226.53 11 Jun 2026 C1 malicious ISC No Details →
2.8.1-680fac205.59 11 Jun 2026 C1 malicious ISC No Details →
2.8.1-da13d4640.58 11 Jun 2026 C1 malicious ISC No Details →
2.8.1-e9684e130.56 11 Jun 2026 C1 malicious ISC No Details →
2.8.1-6b79ca2c7.53 10 Jun 2026 C1 malicious ISC No Details →
2.8.1-bcad7ffa9.53 09 Jun 2026 C1 malicious ISC No Details →
2.8.1-4c3f548b2.20 01 Jun 2026 C1 malicious ISC No Details →
2.8.1-1fc5fd40f.17 29 May 2026 C1 malicious ISC No Details →
2.8.0 26 May 2026 C1 malicious ISC No Details →
2.7.1 22 May 2026 C1 malicious ISC No Details →
2.7.0 20 May 2026 C1 malicious ISC No Details →
2.6.2-12954b1c2.292 20 May 2026 C1 malicious ISC No Details →
2.6.2-d0be00613.280 15 May 2026 C1 malicious — No Details →
2.6.2-6b31736c3.282 13 May 2026 C1 malicious — No Details →
2.6.2-dd032143b.262 12 May 2026 C1 malicious — No Details →
2.6.2-08ebf8e07.279 12 May 2026 C1 malicious — No Details →
2.6.2-646d97c5e.259 12 May 2026 C1 malicious — No Details →
2.6.2-649bddf4d.262 08 May 2026 C1 malicious — No Details →
2.6.2-a0b458e10.252 07 May 2026 C1 malicious — No Details →
2.6.2-fe7b57551.254 06 May 2026 C1 malicious — No Details →
2.6.2-112023c9b.250 05 May 2026 C1 malicious — No Details →
2.6.2-3193b366a.239 30 Apr 2026 C1 malicious — No Details →
2.6.1 25 Feb 2026 C1 malicious — No Details →
2.6.0 07 Jan 2026 C1 malicious — No Details →
2.5.0 25 Nov 2025 C1 malicious — No Details →
2.4.4 24 Nov 2025 C1 malicious — No Details →
2.4.2-alpha.1 27 Jan 2025 C1 malicious — No Details →
2.4.2-alpha.0 27 Jan 2025 C1 malicious — No Details →
2.4.1 21 Jan 2025 C1 malicious — No Details →
2.4.0 04 Dec 2024 C1 malicious — No Details →
2.3.2 19 Aug 2024 C1 malicious — No Details →
2.3.1 16 Aug 2024 C1 malicious — No Details →

The newest 120 of 154 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 @voiceflow/logger

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 @voiceflow/logger Package N/A critical No fix published 25 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 @voiceflow/logger

Is @voiceflow/logger safe to use?

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

Vulert scores @voiceflow/logger 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 @voiceflow/logger affected?

Yes. 2.10.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.

Which version of @voiceflow/logger should I use?

2.10.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does @voiceflow/logger have?

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

1 vulnerability was recorded for @voiceflow/logger in the last 12 months, and the oldest entry in this database dates to 25 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 @voiceflow/logger 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 @voiceflow/logger for upcoming vulnerabilities?

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