VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

@things-factory/shell: vulnerability history, versions and safety

@things-factory/shell is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 120 releases, first recorded in Sep 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
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
1 malicious-package vulnerabilities

A published version contained malicious code.

See malicious packages in npm →

See all @things-factory/shell vulnerabilities

Vulert verdict on @things-factory/shell 10.1.208 i

Updated on 23 Oct 2026

Malicious package: every vulnerability Vulert records for @things-factory/shell 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 Not enough data
  • 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 10.1.208 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 16 Sep 2025 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 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 @things-factory/shell, 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
10.1.208 23 Oct 2026 C1 malicious MIT No Details →
10.1.206 21 Oct 2026 C1 malicious MIT No Details →
10.1.205 20 Oct 2026 C1 malicious MIT No Details →
10.1.188 18 Oct 2026 C1 malicious MIT No Details →
10.1.179 17 Oct 2026 C1 malicious MIT No Details →
10.1.178 17 Oct 2026 C1 malicious MIT No Details →
10.1.165 15 Oct 2026 C1 malicious MIT No Details →
10.1.157 13 Oct 2026 C1 malicious MIT No Details →
10.1.155 12 Oct 2026 C1 malicious MIT No Details →
10.1.154 11 Oct 2026 C1 malicious MIT No Details →
10.1.150 11 Oct 2026 C1 malicious MIT No Details →
10.1.149 11 Oct 2026 C1 malicious MIT No Details →
10.1.147 10 Oct 2026 C1 malicious MIT No Details →
10.1.146 10 Oct 2026 C1 malicious MIT No Details →
10.1.142 10 Oct 2026 C1 malicious MIT No Details →
10.1.141 10 Oct 2026 C1 malicious MIT No Details →
10.1.123 06 Oct 2026 C1 malicious MIT No Details →
10.1.122 06 Oct 2026 C1 malicious MIT No Details →
10.1.121 05 Oct 2026 C1 malicious MIT No Details →
10.1.106 01 Oct 2026 C1 malicious MIT No Details →
10.1.79 27 Sep 2026 C1 malicious MIT No Details →
10.1.47 24 Sep 2026 C1 malicious MIT No Details →
10.1.46 24 Sep 2026 C1 malicious MIT No Details →
10.1.44 24 Sep 2026 C1 malicious MIT No Details →
10.1.40 24 Sep 2026 C1 malicious MIT No Details →
10.1.39 24 Sep 2026 C1 malicious MIT No Details →
10.1.38 24 Sep 2026 C1 malicious MIT No Details →
10.1.37 23 Sep 2026 C1 malicious MIT No Details →
10.1.34 20 Sep 2026 C1 malicious MIT No Details →
10.1.33 20 Sep 2026 C1 malicious MIT No Details →
10.1.31 19 Sep 2026 C1 malicious MIT No Details →
10.1.29 18 Sep 2026 C1 malicious MIT No Details →
10.1.28 18 Sep 2026 C1 malicious MIT No Details →
10.1.27 17 Sep 2026 C1 malicious MIT No Details →
10.1.26 17 Sep 2026 C1 malicious MIT No Details →
10.1.20 16 Sep 2026 C1 malicious MIT No Details →
10.1.16 15 Sep 2026 C1 malicious MIT No Details →
10.1.7 11 Sep 2026 C1 malicious MIT No Details →
10.1.4 09 Sep 2026 C1 malicious MIT No Details →
10.1.3 07 Sep 2026 C1 malicious MIT No Details →
10.1.2 07 Sep 2026 C1 malicious MIT No Details →
10.1.1 07 Sep 2026 C1 malicious MIT No Details →
10.1.0 07 Sep 2026 C1 malicious MIT No Details →
10.0.19 31 Aug 2026 C1 malicious MIT No Details →
10.0.18 30 Aug 2026 C1 malicious MIT No Details →
10.0.13 23 Aug 2026 C1 malicious MIT No Details →
10.0.10 18 Aug 2026 C1 malicious MIT No Details →
8.0.97 18 Aug 2026 C1 malicious MIT No Details →
10.0.9 06 Aug 2026 C1 malicious MIT No Details →
10.0.8 02 Aug 2026 C1 malicious MIT No Details →
10.0.7 02 Aug 2026 C1 malicious MIT No Details →
10.0.6 31 Jul 2026 C1 malicious MIT No Details →
10.0.5 30 Jul 2026 C1 malicious MIT No Details →
10.0.4 30 Jul 2026 C1 malicious MIT No Details →
10.0.3 30 Jul 2026 C1 malicious MIT No Details →
8.0.94 30 Jul 2026 C1 malicious MIT No Details →
8.0.93 30 Jul 2026 C1 malicious MIT No Details →
10.0.0 29 Jul 2026 C1 malicious MIT No Details →
10.0.0-zeta.10 13 Jul 2026 C1 malicious MIT No Details →
10.0.0-zeta.8 12 Jul 2026 C1 malicious MIT No Details →
9.2.33 08 Jul 2026 C1 malicious MIT No Details →
10.0.0-zeta.3 07 Jul 2026 C1 malicious MIT No Details →
10.0.0-zeta.1 26 Jun 2026 C1 malicious MIT No Details →
10.0.0-y.0 26 Jun 2026 C1 malicious MIT No Details →
9.2.29 23 Jun 2026 C1 malicious MIT No Details →
10.0.0-beta.108 21 Jun 2026 C1 malicious MIT No Details →
10.0.0-beta.92 26 May 2026 C1 malicious MIT No Details →
10.0.0-beta.89 22 May 2026 C1 malicious MIT No Details →
10.0.0-beta.85 18 May 2026 C1 malicious MIT No Details →
9.2.24 15 May 2026 C1 malicious MIT No Details →
10.0.0-beta.72 05 May 2026 C1 malicious MIT No Details →
10.0.0-beta.53 16 Apr 2026 C1 malicious MIT No Details →
4.3.815 16 Apr 2026 C1 malicious — No Details →
10.0.0-beta.44 10 Apr 2026 C1 malicious MIT No Details →
8.0.88 30 Mar 2026 C1 malicious MIT No Details →
6.4.10 30 Mar 2026 C1 malicious MIT No Details →
6.4.8 29 Mar 2026 C1 malicious MIT No Details →
9.2.16 25 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.28 22 Mar 2026 C1 malicious MIT No Details →
9.2.13 19 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.19 15 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.16 10 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.10 08 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.8 07 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.7 07 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.6 06 Mar 2026 C1 malicious MIT No Details →
9.2.5 06 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.5 05 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.4 05 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.3 05 Mar 2026 C1 malicious MIT No Details →
8.0.86 05 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.2 05 Mar 2026 C1 malicious MIT No Details →
10.0.0-beta.1 04 Mar 2026 C1 malicious MIT No Details →
4.3.767 29 Jan 2026 C1 malicious MIT No Details →
4.3.764 28 Jan 2026 C1 malicious MIT No Details →
4.3.755 20 Jan 2026 C1 malicious MIT No Details →
4.3.752 15 Jan 2026 C1 malicious MIT No Details →
4.3.743 08 Jan 2026 C1 malicious MIT No Details →
4.3.740 05 Jan 2026 C1 malicious MIT No Details →
4.3.738 23 Dec 2025 C1 malicious MIT No Details →
4.3.734 17 Dec 2025 C1 malicious — No Details →
4.3.729 16 Dec 2025 C1 malicious — No Details →
4.3.727 12 Dec 2025 C1 malicious — No Details →
4.3.725 11 Dec 2025 C1 malicious — No Details →
4.3.723 11 Dec 2025 C1 malicious — No Details →
4.3.705 10 Dec 2025 C1 malicious — No Details →
4.3.704 10 Dec 2025 C1 malicious — No Details →
9.1.19 25 Nov 2025 C1 malicious — No Details →
4.3.695 21 Nov 2025 C1 malicious — No Details →
8.0.64 03 Nov 2025 C1 malicious — No Details →
8.0.63 03 Nov 2025 C1 malicious — No Details →
4.3.689 02 Nov 2025 C1 malicious — No Details →
8.0.61 28 Oct 2025 C1 malicious — No Details →
9.1.13 22 Oct 2025 C1 malicious — No Details →
9.1.0 16 Sep 2025 C1 malicious — No Details →
9.0.41 14 Sep 2025 C1 malicious — No Details →
9.0.34 01 Sep 2025 C1 malicious — No Details →
4.3.675 27 Aug 2025 C1 malicious — No Details →
4.3.673 21 Aug 2025 C1 malicious — No Details →
4.3.672 21 Aug 2025 C1 malicious — No Details →

The newest 120 of 1,459 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. 0 of the 1 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for @things-factory/shell

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Malicious Code Injection in @things-factory/shell: A Critical Security Threat N/A critical No fix published 16 Sep 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 @things-factory/shell

Is @things-factory/shell safe to use?

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

Vulert scores @things-factory/shell 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 @things-factory/shell affected?

Yes. 10.1.208, 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 @things-factory/shell have?

1 vulnerability is recorded for @things-factory/shell 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 @things-factory/shell vulnerabilities disclosed?

0 vulnerabilities were recorded for @things-factory/shell in the last 12 months, and the oldest entry in this database dates to 16 Sep 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 @things-factory/shell 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 @things-factory/shell for upcoming vulnerabilities?

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