VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@freeday-ai/webchat: vulnerability history, versions and safety

@freeday-ai/webchat 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 @freeday-ai/webchat vulnerabilities

Vulert verdict on @freeday-ai/webchat 2025.6.0-4.10.34.8523 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @freeday-ai/webchat 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 35/100
  • Security Malicious code published
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

Malicious code has been published under this package before, 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 2025.6.0-4.10.34.8523 — unaffected 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
  • Last release this month 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 @freeday-ai/webchat, 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
2026.10.23-09-23-19606 23 Oct 2026 C1 malicious — No Details →
2026.10.23-08-37-19605 23 Oct 2026 C1 malicious — No Details →
2026.10.22-10-34-19563 22 Oct 2026 C1 malicious — No Details →
2026.10.21-09-01-19496 21 Oct 2026 C1 malicious — No Details →
2026.10.20-12-26-19417 20 Oct 2026 C1 malicious — No Details →
2026.10.19-18-16-9679 19 Oct 2026 C1 malicious — No Details →
2026.10.19-16-04-19413 19 Oct 2026 C1 malicious — No Details →
2026.10.19-16-08-6157 19 Oct 2026 C1 malicious — No Details →
2026.10.19-15-24-19403 19 Oct 2026 C1 malicious — No Details →
2026.10.19-13-57-5661 19 Oct 2026 C1 malicious — No Details →
2026.10.19-13-50-19237 19 Oct 2026 C1 malicious — No Details →
2026.10.19-13-29-9893 19 Oct 2026 C1 malicious — No Details →
2026.10.19-13-06-3577 19 Oct 2026 C1 malicious — No Details →
2026.10.19-12-34-9954 19 Oct 2026 C1 malicious — No Details →
2026.10.19-12-19-6039 19 Oct 2026 C1 malicious — No Details →
2026.10.19-09-27-19212 19 Oct 2026 C1 malicious — No Details →
2026.10.19-07-32-19362 19 Oct 2026 C1 malicious — No Details →
2026.10.16-18-52-5438 16 Oct 2026 C1 malicious — No Details →
2026.10.16-18-24-2327 16 Oct 2026 C1 malicious — No Details →
2026.10.16-15-04-9177 16 Oct 2026 C1 malicious — No Details →
2026.10.16-14-29-4814 16 Oct 2026 C1 malicious — No Details →
2026.10.16-07-59-19238 16 Oct 2026 C1 malicious — No Details →
2026.10.15-19-28-5455 15 Oct 2026 C1 malicious — No Details →
2026.10.15-13-40-19215 15 Oct 2026 C1 malicious — No Details →
2026.10.15-12-17-19222 15 Oct 2026 C1 malicious — No Details →
2026.10.15-11-55-19221 15 Oct 2026 C1 malicious — No Details →
2026.10.15-07-46-19198 15 Oct 2026 C1 malicious — No Details →
2026.10.14-16-06-4089 14 Oct 2026 C1 malicious — No Details →
2026.10.14-15-42-19233 14 Oct 2026 C1 malicious — No Details →
2026.10.14-15-24-3315 14 Oct 2026 C1 malicious — No Details →
2026.10.14-14-52-19219 14 Oct 2026 C1 malicious — No Details →
2026.10.14-14-01-5081 14 Oct 2026 C1 malicious — No Details →
2026.10.14-07-33-6905 14 Oct 2026 C1 malicious — No Details →
2026.10.14-06-47-1730 14 Oct 2026 C1 malicious — No Details →
2026.10.13-21-07-8095 13 Oct 2026 C1 malicious — No Details →
2026.10.13-20-36-9206 13 Oct 2026 C1 malicious — No Details →
2026.10.13-17-54-9138 13 Oct 2026 C1 malicious — No Details →
2026.10.13-17-35-8014 13 Oct 2026 C1 malicious — No Details →
2026.10.13-17-20-19184 13 Oct 2026 C1 malicious — No Details →
2026.10.13-16-55-19183 13 Oct 2026 C1 malicious — No Details →
2026.10.13-15-32-7479 13 Oct 2026 C1 malicious — No Details →
2026.10.13-15-12-8156 13 Oct 2026 C1 malicious — No Details →
2026.10.13-14-38-8657 13 Oct 2026 C1 malicious — No Details →
2026.10.13-11-11-9450 13 Oct 2026 C1 malicious — No Details →
2026.10.13-09-48-5046 13 Oct 2026 C1 malicious — No Details →
2026.10.13-08-40-3307 13 Oct 2026 C1 malicious — No Details →
2026.10.13-07-56-19073 13 Oct 2026 C1 malicious — No Details →
2026.10.13-05-48-5763 13 Oct 2026 C1 malicious — No Details →
2026.10.12-18-39-19140 12 Oct 2026 C1 malicious — No Details →
2026.10.12-17-07-8751 12 Oct 2026 C1 malicious — No Details →
2026.10.12-16-33-7432 12 Oct 2026 C1 malicious — No Details →
2026.10.12-15-09-19128 12 Oct 2026 C1 malicious — No Details →
2026.10.12-14-56-19130 12 Oct 2026 C1 malicious — No Details →
2026.10.12-14-02-18914 12 Oct 2026 C1 malicious — No Details →
2026.10.12-10-58-7875 12 Oct 2026 C1 malicious — No Details →
2026.10.12-07-38-18846 12 Oct 2026 C1 malicious — No Details →
2026.10.11-15-15-1489 11 Oct 2026 C1 malicious — No Details →
2026.10.11-14-33-7936 11 Oct 2026 C1 malicious — No Details →
2026.10.11-14-07-9045 11 Oct 2026 C1 malicious — No Details →
2026.10.11-13-49-3612 11 Oct 2026 C1 malicious — No Details →
2026.10.11-06-54-1068 11 Oct 2026 C1 malicious — No Details →
2026.10.9-21-22-4214 09 Oct 2026 C1 malicious — No Details →
2026.10.9-21-04-3701 09 Oct 2026 C1 malicious — No Details →
2026.10.9-20-53-3806 09 Oct 2026 C1 malicious — No Details →
2026.10.9-20-02-4429 09 Oct 2026 C1 malicious — No Details →
2026.10.9-19-46-1019 09 Oct 2026 C1 malicious — No Details →
2026.10.9-19-38-6739 09 Oct 2026 C1 malicious — No Details →
2026.10.9-19-09-9290 09 Oct 2026 C1 malicious — No Details →
2026.10.9-13-04-19053 09 Oct 2026 C1 malicious — No Details →
2026.10.9-07-58-2575 09 Oct 2026 C1 malicious — No Details →
2026.10.9-07-13-18996 09 Oct 2026 C1 malicious — No Details →
2026.10.9-07-10-18995 09 Oct 2026 C1 malicious — No Details →
2026.10.8-13-38-18994 08 Oct 2026 C1 malicious — No Details →
2026.10.8-13-16-6549 08 Oct 2026 C1 malicious — No Details →
2026.10.8-12-46-19030 08 Oct 2026 C1 malicious — No Details →
2026.10.8-10-22-18911 08 Oct 2026 C1 malicious — No Details →
2026.10.8-07-28-18900 08 Oct 2026 C1 malicious — No Details →
2026.10.8-07-07-18970 08 Oct 2026 C1 malicious — No Details →
2026.10.7-13-40-18979 07 Oct 2026 C1 malicious — No Details →
2026.10.7-10-03-18963 07 Oct 2026 C1 malicious — No Details →
2026.10.7-09-44-18957 07 Oct 2026 C1 malicious — No Details →
2026.10.6-14-37-2957 06 Oct 2026 C1 malicious — No Details →
2026.10.6-13-22-18615 06 Oct 2026 C1 malicious — No Details →
2026.10.6-12-56-18877 06 Oct 2026 C1 malicious — No Details →
2026.10.6-12-50-18867 06 Oct 2026 C1 malicious — No Details →
2026.10.6-12-44-18868 06 Oct 2026 C1 malicious — No Details →
2026.10.6-04-38-6125 06 Oct 2026 C1 malicious — No Details →
2026.10.5-20-47-2203 05 Oct 2026 C1 malicious — No Details →
2026.10.5-20-34-9405 05 Oct 2026 C1 malicious — No Details →
2026.10.5-19-33-4301 05 Oct 2026 C1 malicious — No Details →
2026.10.5-15-00-18886 05 Oct 2026 C1 malicious — No Details →
2026.10.5-11-13-6794 05 Oct 2026 C1 malicious — No Details →
2026.10.2-20-39-7771 02 Oct 2026 C1 malicious — No Details →
2026.10.2-12-16-18771 02 Oct 2026 C1 malicious — No Details →
2026.10.2-11-50-18815 02 Oct 2026 C1 malicious — No Details →
2026.10.1-10-58-2413 01 Oct 2026 C1 malicious — No Details →
2026.9.29-12-33-7379 29 Sep 2026 C1 malicious — No Details →
2026.9.29-10-49-18644 29 Sep 2026 C1 malicious — No Details →
2026.9.29-10-49-18550 29 Sep 2026 C1 malicious — No Details →
2026.9.29-10-24-18708 29 Sep 2026 C1 malicious — No Details →
2026.9.29-09-00-18641 29 Sep 2026 C1 malicious — No Details →
2026.9.29-08-26-18646 29 Sep 2026 C1 malicious — No Details →
2026.9.24-09-17-18562 24 Sep 2026 C1 malicious — No Details →
2026.9.23-17-43-8783 23 Sep 2026 C1 malicious — No Details →
2026.9.23-14-32-6547 23 Sep 2026 C1 malicious — No Details →
2026.9.23-06-59-18511 23 Sep 2026 C1 malicious — No Details →
2026.9.22-15-41-1741 22 Sep 2026 C1 malicious — No Details →
2026.9.22-15-06-18494 22 Sep 2026 C1 malicious — No Details →
2026.9.22-14-06-7151 22 Sep 2026 C1 malicious — No Details →
2026.9.22-12-31-18500 22 Sep 2026 C1 malicious — No Details →
2026.9.22-11-26-18459 22 Sep 2026 C1 malicious — No Details →
2026.9.22-08-32-2315 22 Sep 2026 C1 malicious — No Details →
2026.9.22-08-35-18409 22 Sep 2026 C1 malicious — No Details →
2026.9.22-08-23-2857 22 Sep 2026 C1 malicious — No Details →
2026.9.22-03-49-5045 22 Sep 2026 C1 malicious — No Details →
2026.9.21-18-07-3622 21 Sep 2026 C1 malicious — No Details →
2026.9.21-13-39-1423 21 Sep 2026 C1 malicious — No Details →
2026.9.21-10-20-5559 21 Sep 2026 C1 malicious — No Details →
2026.9.21-10-16-18443 21 Sep 2026 C1 malicious — No Details →
2026.9.21-08-54-1704 21 Sep 2026 C1 malicious — No Details →

The newest 120 of 2,439 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 @freeday-ai/webchat

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 @freeday-ai/webchat 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 @freeday-ai/webchat

Is @freeday-ai/webchat safe to use?

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

Vulert scores @freeday-ai/webchat 35/100, which reads as risky. 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). Malicious code has been published under this package before, which caps this score.

Which version of @freeday-ai/webchat should I use?

2025.6.0-4.10.34.8523 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 @freeday-ai/webchat have?

1 vulnerability is recorded for @freeday-ai/webchat 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 @freeday-ai/webchat vulnerabilities disclosed?

1 vulnerability was recorded for @freeday-ai/webchat 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 @freeday-ai/webchat 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 @freeday-ai/webchat for upcoming vulnerabilities?

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