VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@apexacc/cli: vulnerability history, versions and safety

@apexacc/cli is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Oct 2026. 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 16 Oct 2026.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @apexacc/cli vulnerabilities

Vulert verdict on @apexacc/cli 1.6.2 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @apexacc/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 Deprecated
  • 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 1.6.2 — affected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 16 Oct 2026 i
  • Highest CVSS n/a i
  • With no published fix 1 i
  • Malicious packages 1 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 @apexacc/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
1.6.2 27 Sep 2026 C1 malicious MIT No Details →
1.6.1 18 Sep 2026 C1 malicious MIT No Details →
1.6.0 18 Sep 2026 C1 malicious MIT No Details →
1.5.122 17 Sep 2026 C1 malicious MIT No Details →
1.5.121 17 Sep 2026 C1 malicious MIT No Details →
1.5.120 17 Sep 2026 C1 malicious MIT No Details →
1.5.119 17 Sep 2026 C1 malicious MIT No Details →
1.5.117 17 Sep 2026 C1 malicious MIT No Details →
1.5.118 17 Sep 2026 C1 malicious MIT No Details →
1.5.116 17 Sep 2026 C1 malicious MIT No Details →
1.5.114 17 Sep 2026 C1 malicious MIT No Details →
1.5.113 17 Sep 2026 C1 malicious MIT No Details →
1.5.112 16 Sep 2026 C1 malicious MIT No Details →
1.5.110 15 Sep 2026 C1 malicious MIT No Details →
1.5.111 15 Sep 2026 C1 malicious MIT No Details →
1.5.109 11 Sep 2026 C1 malicious MIT No Details →
1.5.108 10 Sep 2026 C1 malicious MIT No Details →
1.5.107 10 Sep 2026 C1 malicious MIT No Details →
1.5.106 10 Sep 2026 C1 malicious MIT No Details →
1.5.105 10 Sep 2026 C1 malicious MIT No Details →
1.5.104 10 Sep 2026 C1 malicious MIT No Details →
1.5.103 10 Sep 2026 C1 malicious MIT No Details →
1.5.102 10 Sep 2026 C1 malicious MIT No Details →
1.5.101 10 Sep 2026 C1 malicious MIT No Details →
1.5.100 10 Sep 2026 C1 malicious MIT No Details →
1.5.99 10 Sep 2026 C1 malicious MIT No Details →
1.5.98 10 Sep 2026 C1 malicious MIT No Details →
1.5.96 10 Sep 2026 C1 malicious MIT No Details →
1.5.94 09 Sep 2026 C1 malicious MIT No Details →
1.5.92 09 Sep 2026 C1 malicious MIT No Details →
1.5.91 09 Sep 2026 C1 malicious MIT No Details →
1.5.90 08 Sep 2026 C1 malicious MIT No Details →
1.5.89 08 Sep 2026 C1 malicious MIT No Details →
1.5.88 08 Sep 2026 C1 malicious MIT No Details →
1.5.87 08 Sep 2026 C1 malicious MIT No Details →
1.5.86 08 Sep 2026 C1 malicious MIT No Details →
1.5.84 07 Sep 2026 C1 malicious MIT No Details →
1.5.83 07 Sep 2026 C1 malicious MIT No Details →
1.5.82 07 Sep 2026 C1 malicious MIT No Details →
1.5.80 07 Sep 2026 C1 malicious MIT No Details →
1.5.81 07 Sep 2026 C1 malicious MIT No Details →
1.5.79 07 Sep 2026 C1 malicious MIT No Details →
1.5.78 07 Sep 2026 C1 malicious MIT No Details →
1.5.77 07 Sep 2026 C1 malicious MIT No Details →
1.5.76 07 Sep 2026 C1 malicious MIT No Details →
1.5.75 07 Sep 2026 C1 malicious MIT No Details →
1.5.74 07 Sep 2026 C1 malicious MIT No Details →
1.5.73 07 Sep 2026 C1 malicious MIT No Details →
1.5.72 07 Sep 2026 C1 malicious MIT No Details →
1.5.71 07 Sep 2026 C1 malicious MIT No Details →
1.5.69 07 Sep 2026 C1 malicious MIT No Details →
1.5.67 07 Sep 2026 C1 malicious MIT No Details →
1.5.66 06 Sep 2026 C1 malicious MIT No Details →
1.5.64 06 Sep 2026 C1 malicious MIT No Details →
1.5.65 06 Sep 2026 C1 malicious MIT No Details →
1.5.63 06 Sep 2026 C1 malicious MIT No Details →
1.5.62 06 Sep 2026 C1 malicious MIT No Details →
1.5.51 06 Sep 2026 C1 malicious MIT No Details →
1.5.49 06 Sep 2026 C1 malicious MIT No Details →
1.5.44 06 Sep 2026 C1 malicious MIT No Details →
1.5.43 06 Sep 2026 C1 malicious MIT No Details →
1.5.42 06 Sep 2026 C1 malicious MIT No Details →
1.5.41 06 Sep 2026 C1 malicious MIT No Details →
1.5.40 06 Sep 2026 C1 malicious MIT No Details →
1.5.38 06 Sep 2026 C1 malicious MIT No Details →
1.5.39 06 Sep 2026 C1 malicious MIT No Details →
1.5.37 05 Sep 2026 C1 malicious MIT No Details →
1.5.36 05 Sep 2026 C1 malicious MIT No Details →
1.5.35 05 Sep 2026 C1 malicious MIT No Details →
1.5.31 05 Sep 2026 C1 malicious MIT No Details →
1.5.30 05 Sep 2026 C1 malicious MIT No Details →
1.5.29 05 Sep 2026 C1 malicious MIT No Details →
1.5.28 05 Sep 2026 C1 malicious MIT No Details →
1.5.27 05 Sep 2026 C1 malicious MIT No Details →
1.5.26 05 Sep 2026 C1 malicious MIT No Details →
1.5.25 05 Sep 2026 C1 malicious MIT No Details →
1.5.24 25 Aug 2026 C1 malicious MIT No Details →
1.5.23 25 Aug 2026 C1 malicious MIT No Details →
1.5.22 25 Aug 2026 C1 malicious MIT No Details →
1.5.21 25 Aug 2026 C1 malicious MIT No Details →
1.5.20 25 Aug 2026 C1 malicious MIT No Details →
1.5.17 24 Aug 2026 C1 malicious MIT No Details →
1.5.16 24 Aug 2026 C1 malicious MIT No Details →
1.5.15 24 Aug 2026 C1 malicious MIT No Details →
1.5.12 24 Aug 2026 C1 malicious MIT No Details →
1.5.11 24 Aug 2026 C1 malicious MIT No Details →
1.5.10 24 Aug 2026 C1 malicious MIT No Details →
1.5.8 18 Aug 2026 C1 malicious MIT No Details →
1.5.7 17 Aug 2026 C1 malicious MIT No Details →
1.5.6 17 Aug 2026 C1 malicious MIT No Details →
1.5.5 16 Aug 2026 C1 malicious MIT No Details →
1.5.4 16 Aug 2026 C1 malicious MIT No Details →
1.5.3 15 Aug 2026 C1 malicious MIT No Details →
1.5.0 15 Aug 2026 C1 malicious MIT No Details →
1.4.9 15 Aug 2026 C1 malicious MIT No Details →
1.4.8 15 Aug 2026 C1 malicious MIT No Details →
1.4.7 15 Aug 2026 C1 malicious MIT No Details →
1.4.6 15 Aug 2026 C1 malicious MIT No Details →
1.4.5 15 Aug 2026 C1 malicious MIT No Details →
1.4.4 15 Aug 2026 C1 malicious MIT No Details →
1.4.1 15 Aug 2026 C1 malicious — No Details →
1.4.0 15 Aug 2026 C1 malicious — No Details →
1.3.8 14 Aug 2026 C1 malicious — No Details →
1.3.7 14 Aug 2026 C1 malicious — No Details →
1.3.6 14 Aug 2026 C1 malicious — No Details →
1.3.5 14 Aug 2026 C1 malicious — No Details →
1.3.4 14 Aug 2026 C1 malicious — No Details →
1.3.3 14 Aug 2026 C1 malicious — No Details →
1.3.2 14 Aug 2026 C1 malicious — No Details →
1.3.1 14 Aug 2026 C1 malicious — No Details →
1.3.0 14 Aug 2026 C1 malicious — No Details →
1.2.9 14 Aug 2026 C1 malicious — No Details →
1.2.8 14 Aug 2026 C1 malicious — No Details →
1.2.6 14 Aug 2026 C1 malicious — No Details →
1.2.5 14 Aug 2026 C1 malicious — No Details →
1.2.4 10 Aug 2026 C1 malicious — No Details →
1.2.3 10 Aug 2026 C1 malicious — No Details →
1.2.2 10 Aug 2026 C1 malicious — No Details →
1.2.1 09 Aug 2026 C1 malicious — No Details →
1.2.0 09 Aug 2026 C1 malicious — No Details →

The newest 120 of 122 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 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 @apexacc/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 @apexacc/cli Package N/A critical No fix published 16 Oct 2026

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 @apexacc/cli

Is @apexacc/cli safe to use?

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

Vulert scores @apexacc/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 @apexacc/cli affected?

Yes. 1.6.2, 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 @apexacc/cli have?

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

1 vulnerability was recorded for @apexacc/cli in the last 12 months, and the oldest entry in this database dates to 16 Oct 2026. 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 @apexacc/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 @apexacc/cli for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the @apexacc/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.