Critical Malicious Code Vulnerability in weaviate-js Package

weaviate-js Updated 23 Jan 2026

Summary

21/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-434: Malicious code in weaviate-js (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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The weaviate-js package is a JavaScript client for interacting with Weaviate, an open-source vector search engine. It allows developers to integrate advanced AI capabilities into their applications. However, this package has been found to contain malicious code, posing significant security risks to any system utilizing it.

Vulnerability Detail

The vulnerability originates from the discovery of embedded malicious code within the weaviate-js package. This code can compromise any computer that has the package installed, potentially 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 weaviate-js

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 to maintain functionality while addressing the vulnerability, consider using an alternative package that provides similar capabilities without the associated risks. Additionally, ensure that all secrets and keys stored on the affected system are rotated from a secure environment.

Conclusion

The discovery of malicious code within the weaviate-js package poses a serious threat to users. Immediate action is required to remove the package and secure any sensitive information. Regular monitoring and updates are essential to maintain security in your applications.

See every vulnerability recorded for weaviate-js →

Share this vulnerability

FAQ

weaviate-js is a JavaScript client designed for interacting with the Weaviate vector search engine, enabling developers to leverage AI functionalities in their applications.

If you have the weaviate-js package installed, your system may be compromised. It is recommended to remove the package and rotate any sensitive information.

If immediate removal is not possible, consider using an alternative package and ensure that all sensitive information is secured and rotated.

Currently, there is no patch available for the weaviate-js package. The best course of action is to remove the package from your project.

Vulert monitors and alerts you in real-time for open-source vulnerabilities using just your package-lock.json file. You can check if your application is affected by this vulnerability using the Vulert playground without any signup.

How To Fix

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

npm uninstall weaviate-js

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