VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

altcha: vulnerability history, versions and safety

altcha is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 110 releases, first recorded in Dec 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 M1
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 08 Dec 2025.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all altcha vulnerabilities

Vulert verdict on altcha 3.5.0 i

Updated on 23 Oct 2026

Careful: 3.5.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 3.5.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 08 Dec 2025 i
  • Highest CVSS 6.9 i
  • With no published fix 1 i
  • Stars 2,830 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 altcha, 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
3.5.0 22 Oct 2026 M1 MIT No Details →
3.4.1 19 Oct 2026 M1 MIT No Details →
3.4.0 15 Oct 2026 M1 MIT No Details →
3.3.0 05 Oct 2026 M1 MIT No Details →
3.2.4 30 Sep 2026 M1 MIT No Details →
3.2.3 20 Sep 2026 M1 MIT No Details →
3.2.2 19 Aug 2026 M1 MIT No Details →
3.2.1 12 Jul 2026 M1 MIT No Details →
3.2.0 08 Jul 2026 M1 MIT No Details →
3.1.0 11 Jun 2026 M1 MIT No Details →
3.0.11 01 Jun 2026 M1 MIT No Details →
3.0.10 23 May 2026 M1 MIT No Details →
3.0.9 12 May 2026 M1 MIT No Details →
3.0.8 06 May 2026 M1 MIT No Details →
3.0.7 06 May 2026 M1 MIT No Details →
3.0.6 04 May 2026 M1 MIT No Details →
3.0.5 02 May 2026 M1 MIT No Details →
3.0.4 19 Apr 2026 M1 MIT No Details →
3.0.3 18 Apr 2026 M1 MIT No Details →
3.0.2 10 Apr 2026 M1 MIT No Details →
3.0.1 07 Apr 2026 M1 MIT No Details →
3.0.0 07 Apr 2026 M1 MIT No Details →
3.0.0-beta.4 06 Apr 2026 M1 MIT No Details →
3.0.0-beta.3 21 Mar 2026 M1 MIT No Details →
3.0.0-beta.2 12 Mar 2026 M1 MIT No Details →
3.0.0-beta.1 22 Feb 2026 M1 MIT No Details →
2.3.0 18 Dec 2025 M1 MIT No Details →
2.2.4 27 Sep 2025 M1 MIT No Details →
2.2.3 09 Sep 2025 M1 MIT No Details →
2.2.2 02 Sep 2025 M1 MIT No Details →
2.2.1 31 Aug 2025 M1 MIT No Details →
2.2.0 30 Aug 2025 M1 MIT No Details →
2.2.0-beta.2 30 Aug 2025 M1 MIT No Details →
2.2.0-beta.1 30 Aug 2025 M1 MIT No Details →
2.1.0 21 Jul 2025 M1 MIT No Details →
2.1.0-beta.4 21 Jul 2025 M1 MIT No Details →
2.1.0-beta.3 21 Jul 2025 M1 MIT No Details →
2.1.0-beta.2 01 Jul 2025 M1 MIT No Details →
2.0.5 01 Jul 2025 M1 MIT No Details →
2.0.4 29 Jun 2025 M1 MIT No Details →
2.1.0-beta.1 09 Jun 2025 M1 MIT No Details →
2.0.3 04 Jun 2025 M1 MIT No Details →
2.0.2 24 May 2025 M1 MIT No Details →
2.0.1 21 May 2025 M1 MIT No Details →
2.0.0 19 May 2025 M1 MIT No Details →
2.0.0-beta.12 15 May 2025 M1 MIT No Details →
2.0.0-beta.11 14 May 2025 M1 MIT No Details →
1.5.1 14 May 2025 M1 MIT No Details →
2.0.0-beta.10 14 May 2025 M1 MIT No Details →
2.0.0-beta.9 14 May 2025 M1 MIT No Details →
1.5.0 13 May 2025 M1 MIT No Details →
2.0.0-beta.8 13 May 2025 M1 MIT No Details →
2.0.0-beta.7 10 May 2025 M1 MIT No Details →
2.0.0-beta.6 10 May 2025 M1 MIT No Details →
1.4.4 10 May 2025 M1 MIT No Details →
2.0.0-beta.5 05 May 2025 M1 MIT No Details →
1.4.3 28 Apr 2025 M1 MIT No Details →
2.0.0-beta.4 28 Apr 2025 M1 MIT No Details →
2.0.0-beta.3 27 Apr 2025 M1 MIT No Details →
2.0.0-beta.2 27 Apr 2025 M1 MIT No Details →
2.0.0-beta.1 25 Apr 2025 M1 MIT No Details →
1.4.2 30 Mar 2025 M1 MIT No Details →
1.4.1 29 Mar 2025 M1 MIT No Details →
1.4.0 16 Mar 2025 M1 MIT No Details →
1.3.0 10 Mar 2025 M1 MIT No Details →
1.2.0 20 Feb 2025 M1 MIT No Details →
1.1.1 31 Jan 2025 M1 MIT No Details →
1.1.0 28 Dec 2024 M1 MIT No Details →
1.1.0-beta.1 21 Dec 2024 M1 MIT No Details →
1.0.7 14 Nov 2024 M1 MIT No Details →
1.0.6 19 Oct 2024 M1 MIT No Details →
1.0.5 11 Oct 2024 M1 MIT No Details →
1.0.4 11 Oct 2024 M1 MIT No Details →
1.0.3 11 Oct 2024 M1 MIT No Details →
1.0.2 11 Oct 2024 M1 MIT No Details →
1.0.1 11 Oct 2024 M1 MIT No Details →
1.0.0 02 Sep 2024 M1 MIT No Details →
0.9.0 18 Aug 2024 M1 MIT No Details →
0.8.0 09 Aug 2024 M1 MIT No Details →
0.7.0 04 Aug 2024 M1 MIT No Details →
0.6.7 29 Jul 2024 M1 MIT No Details →
0.6.6 28 Jul 2024 M1 MIT No Details →
0.6.5 23 Jul 2024 M1 MIT No Details →
0.6.4 19 Jul 2024 M1 MIT No Details →
0.6.3 09 Jul 2024 M1 MIT No Details →
0.6.2 06 Jul 2024 M1 MIT No Details →
0.6.1 04 Jul 2024 M1 MIT No Details →
0.6.0 24 Jun 2024 M1 MIT No Details →
0.5.1 17 Jun 2024 M1 MIT No Details →
0.5.0 14 Jun 2024 M1 MIT No Details →
0.4.3 03 Jun 2024 M1 MIT No Details →
0.4.2 26 May 2024 M1 MIT No Details →
0.4.1 18 May 2024 M1 MIT No Details →
0.4.0 12 May 2024 M1 MIT No Details →
0.3.2 30 Apr 2024 M1 MIT No Details →
0.3.1 28 Apr 2024 M1 MIT No Details →
0.3.0 28 Apr 2024 M1 MIT No Details →
0.2.3 10 Apr 2024 M1 MIT No Details →
0.2.2 13 Mar 2024 M1 MIT No Details →
0.2.1 08 Mar 2024 M1 MIT No Details →
0.2.0 08 Mar 2024 M1 — No Details →
0.1.9 25 Feb 2024 M1 — No Details →
0.1.8 22 Feb 2024 M1 — No Details →
0.1.7 22 Feb 2024 M1 — No Details →
0.1.6 12 Feb 2024 M1 — No Details →
0.1.5 22 Jan 2024 M1 — No Details →
0.1.4 20 Jan 2024 M1 — No Details →
0.1.2 18 Dec 2023 M1 — No Details →
0.1.1 05 Dec 2023 M1 — No Details →
0.1.0 18 Nov 2023 M1 — No Details →

All 110 versions Vulert tracks for this package. 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 altcha

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2025-65849: Altcha Package Suffers from Proof-of-Work Obfuscation Mode Cryptanalytic Break 6.9 medium No fix published 08 Dec 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 altcha

Is altcha safe to use?

Vulert records 1 vulnerabilities for altcha in npm: 0 critical, 0 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is altcha's Vulert package health score?

Vulert scores altcha 60/100, which reads as usable, but worth attention. 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 has a vulnerability with no published fix, which caps this score.

Is the latest version of altcha affected?

Yes. 3.5.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 altcha have?

1 vulnerability is recorded for altcha in the npm ecosystem: 0 critical, 0 high, 1 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 altcha vulnerabilities disclosed?

1 vulnerability was recorded for altcha in the last 12 months, and the oldest entry in this database dates to 08 Dec 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 altcha 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.

How do I monitor altcha for upcoming vulnerabilities?

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