Critical Malicious Code Vulnerability in @wizloft/harness-commands Package

@wizloft/harness-commands Updated 23 Sep 2026

Summary

23/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16425: Malicious code in @wizloft/harness-commands (npm). Affected versions are not published. 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

The @wizloft/harness-commands package is an npm library designed to facilitate command execution within the Harness platform. It is utilized by developers to streamline deployment processes and manage CI/CD workflows. However, this package has been identified as containing malicious code, posing significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the @wizloft/harness-commands package. This code can compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The malicious nature of the code means that simply removing the package may not eliminate all traces of the compromise, as full control of the affected system may have been granted to an external entity.

How To Fix

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

npm uninstall @wizloft/harness-commands

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

There are no effective workarounds for this vulnerability other than removing the package entirely and rotating any compromised secrets and keys.

Conclusion

The @wizloft/harness-commands package contains malicious code that poses a serious security threat. Immediate action is required to remove the package and secure any compromised information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for @wizloft/harness-commands →

Share this vulnerability

FAQ

You should immediately uninstall the package and rotate any secrets or keys stored on the affected machine.

You can use Vulert to monitor and alert for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without requiring any signup.

Keeping the package installed can lead to unauthorized access to sensitive information and complete compromise of your system.

No, there is currently no patched version available for this package. The only solution is to remove it completely.

After removal, ensure that you rotate all secrets and keys stored on the affected machine and monitor for any unusual activity.

How To Fix

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

npm uninstall @wizloft/harness-commands

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