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

@wizloft/harness-memory Updated 23 Sep 2026

Summary

23/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16428: Malicious code in @wizloft/harness-memory (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 Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The @wizloft/harness-memory package is an npm library designed for memory management in applications. It provides functionalities that allow developers to optimize memory usage and improve application performance. However, this package has been compromised, leading to severe security risks for any application that utilizes it.

Vulnerability Detail

The vulnerability stems from embedded malicious code within the @wizloft/harness-memory 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 malicious nature of this code poses a significant risk, as it may lead to data breaches and loss of control over the affected systems. Users are advised to treat any system running this package as compromised and take immediate action.

How To Fix

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

npm uninstall @wizloft/harness-memory

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 workaround, if you need similar functionality, consider using alternative memory management libraries that are known to be secure. Always verify the integrity of packages before installation.

Conclusion

The @wizloft/harness-memory package has been identified as containing malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

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

Share this vulnerability

FAQ

Immediately uninstall the package and rotate any sensitive information stored on the affected system.

You can use the Vulert platform to monitor and alert for open-source vulnerabilities. Visit Vulert Scanner to check if your application is affected without needing to sign up.

Currently, there is no patched version available for this package. It is recommended to remove it entirely.

Failure to address this vulnerability may lead to unauthorized access to sensitive data, data breaches, and loss of control over your systems.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and ensure to review package integrity before installation.

How To Fix

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

npm uninstall @wizloft/harness-memory

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