MAL-2026-18204: Malicious code in @factiii/runner can compromise computers

@factiii/runner Updated 23 Oct 2026

Summary

22/10/2026
CRITICAL
No i
Critical
Not published

MAL-2026-18204: Installing or running the package can fully compromise a computer, exposing stored secrets and keys and potentially leaving additional malicious software behind. Affects @factiii/runner versions 0.28.0. 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

@factiii/runner is a package in the npm ecosystem, written in JavaScript. It is distributed as a software dependency for applications that use npm packages. The supplied advisory identifies the package as containing malicious code and lists a specific affected release; it does not describe the package’s intended functionality or provide further usage details.

Vulnerability Detail

The malicious code can give an outside entity full control of a computer where @factiii/runner is installed or running. The advisory classifies the issue as embedded malicious code (CWE-506) and warns that stored secrets and keys may be exposed. Removing the package may not remove other malicious software introduced during installation, so affected computers should be treated as compromised.

How To Fix

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

npm uninstall @factiii/runner

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

Remove @factiii/runner and rotate all secrets and keys stored on the affected computer from a different computer. Treat the affected system as fully compromised; package removal alone may not eliminate malicious software introduced during installation.

Conclusion

No fixed version is published for @factiii/runner. Remove the package, treat any computer where it was installed or run as compromised, and rotate stored secrets and keys from a different computer. Removing the package may not eliminate other malicious software introduced during installation. Vulert monitors the dependencies in package-lock.json and alerts when a new vulnerability affects them; check an application at https://vulert.com/scanner.

See every vulnerability recorded for @factiii/runner →

Share this vulnerability

FAQ

@factiii/runner version 0.28.0 is listed as affected in the advisory.

@factiii/runner can give an outside entity full control of a computer and expose secrets and keys stored there.

No fixed version is published for @factiii/runner; remove the package and follow the compromise response guidance.

Do not keep @factiii/runner installed; remove it and rotate stored secrets and keys from a different computer.

Manually inspect package-lock.json for @factiii/runner. Vulert can scan a manifest or SBOM and monitor the dependency at Vulert Scanner.

How To Fix

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

npm uninstall @factiii/runner

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