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

@wizloft/harness-project Updated 23 Sep 2026

Summary

23/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16432: Malicious code in @wizloft/harness-project (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-project package is an npm module designed for project management and harnessing development workflows. It is utilized by developers to streamline their project processes. However, this package has been compromised, embedding malicious code that poses significant security risks to any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the @wizloft/harness-project package. This code can fully compromise any computer that has the package installed, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this malicious code is linked to a known malware source, which has been documented in the GitHub security advisories. The ramifications include potential data breaches and loss of control over the affected systems, making it imperative for users to act swiftly.

How To Fix

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

npm uninstall @wizloft/harness-project

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. The only recommended action is to uninstall the compromised package and rotate any sensitive information that may have been exposed.

Conclusion

The @wizloft/harness-project package has been identified as containing malicious code that poses a severe security risk. Users are urged to uninstall the package and take necessary precautions to secure their sensitive information. Regular monitoring for vulnerabilities, such as through Vulert, can help maintain the security of your applications.

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

Share this vulnerability

FAQ

You should immediately uninstall the package using npm uninstall @wizloft/harness-project and rotate any sensitive information stored on your system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in real-time. Visit Vulert Scanner to check if your application is affected without requiring any installation.

No, there is currently no patched version available for the @wizloft/harness-project package. The only solution is to uninstall it.

Failing to address this vulnerability can lead to unauthorized access to sensitive data, potential data breaches, and loss of control over your systems.

No, it is highly recommended to uninstall the package immediately as it contains malicious code that compromises your system's security.

How To Fix

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

npm uninstall @wizloft/harness-project

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