Malicious Code Injection in @things-factory/shell: A Critical Security Threat

@things-factory/shell Updated 02 Oct 2025

Summary

16/09/2025
CRITICAL
No i
Critical
Not published

MAL-2025-47392: Malicious code in @things-factory/shell (npm). Affects @things-factory/shell versions 9.0.42 – 9.0.45. No fix is published. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @things-factory/shell package is a component of the Things Factory ecosystem, primarily used for building and managing applications. It provides essential functionalities for developers, including shell commands and utilities. However, this package has been compromised, leading to the introduction of malicious code that poses significant security risks to users and their applications.

Vulnerability Detail

The vulnerability stems from a compromise of the @things-factory/shell package by the Shai-Hulud NPM worm. This malicious payload is designed to steal sensitive tokens and credentials from users, subsequently publishing this information to GitHub. Furthermore, it propagates itself to other NPM packages owned by the affected user, amplifying the risk of widespread compromise across multiple projects. The technical implications of this vulnerability include unauthorized access to user accounts and potential data breaches.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @things-factory/shell

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, users can remove the @things-factory/shell package from their project until a secure version is confirmed. This can be done using the command: npm uninstall @things-factory/shell. Additionally, users should review their NPM packages for any suspicious activity or unauthorized changes.

Conclusion

The @things-factory/shell package has been compromised, leading to the introduction of malicious code that poses serious security threats. Users are urged to update to the latest secure versions immediately and monitor their applications for any signs of compromise. Utilizing tools like Vulert can help in real-time monitoring for such vulnerabilities.

See every vulnerability recorded for @things-factory/shell →

Share this vulnerability

FAQ

The malicious code is designed to steal user tokens and credentials, which can lead to unauthorized access to user accounts and data.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.

If immediate updates are not possible, consider removing the package temporarily and reviewing your other NPM packages for any suspicious activity.

The worm propagates by injecting itself into other NPM packages owned by the affected user, thereby increasing the risk of further compromises.

Detailed information can be found in the vulnerability report on the GitHub repository of the malicious package.

How To Fix

This package is malicious. Remove it and rotate any credentials it could have accessed.

npm uninstall @things-factory/shell

If it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

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 →
Help improve this record
Report an issue or send feedback