Critical Malicious Code Vulnerability in @wizloft/harness-plugin-memory-context

Summary

23/09/2026
CRITICAL
No i
Critical
Not published

MAL-2026-16431: Malicious code in @wizloft/harness-plugin-memory-context (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 package @wizloft/harness-plugin-memory-context is an npm module designed to facilitate memory context management within applications. It is utilized by developers to enhance performance and manage state effectively. However, this package has been identified to contain malicious code, posing significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability stems from the inclusion of malicious code within the @wizloft/harness-plugin-memory-context package. This code can compromise the entire system, allowing unauthorized access to sensitive information such as secrets and keys. The origin of this vulnerability is linked to the package's malicious intent, which can lead to severe ramifications, including data breaches and loss of control over the affected systems.

How To Fix

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

npm uninstall @wizloft/harness-plugin-memory-context

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

Currently, there are no effective workarounds to mitigate the risks posed by this vulnerability other than removing the package entirely. It is recommended to monitor your system for any unusual activity following the uninstallation.

Conclusion

The discovery of malicious code in the @wizloft/harness-plugin-memory-context package poses a serious threat to systems that utilize it. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help in monitoring and preventing future vulnerabilities.

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

Share this vulnerability

FAQ

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

You can use Vulert, which monitors and alerts for open-source vulnerabilities. Visit Vulert Scanner to check your application without needing to sign up.

No, there is currently no patched version available for the @wizloft/harness-plugin-memory-context package.

Failure to address this vulnerability can lead to unauthorized access to sensitive information and potential data breaches.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert and keep your packages updated.

How To Fix

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

npm uninstall @wizloft/harness-plugin-memory-context

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