Critical Malicious Code Vulnerability in pinecone-js Package

pinecone-js Updated 12 Jan 2026

Summary

12/01/2026
CRITICAL
No i
Critical
Not published

MAL-2026-231: Malicious code in pinecone-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 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 pinecone-js package is a JavaScript library used in Node.js applications for various functionalities, including data management and integration with Pinecone's vector database. It is widely utilized in machine learning and AI applications for efficient data handling. However, this package has been compromised, leading to severe security risks for any system using it.

Vulnerability Detail

The vulnerability stems from the presence of malicious code within the pinecone-js package, identified as GHSA-vrwr-h8hh-fj7r. Any system with this package installed is considered fully compromised, potentially allowing unauthorized access to sensitive data, including secrets and keys. The malicious code can lead to complete control of the affected computer by external entities, making it imperative for users to act swiftly to mitigate risks.

How To Fix

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

npm uninstall pinecone-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

Currently, there are no effective workarounds to mitigate the risks posed by the malicious code. The best course of action is to uninstall the package and secure the system.

Conclusion

The discovery of malicious code in the pinecone-js package poses a significant threat to users and their systems. Immediate action is required to remove the package and secure any sensitive information. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.

See every vulnerability recorded for pinecone-js →

Share this vulnerability

FAQ

Immediately uninstall the pinecone-js package and rotate any sensitive keys or secrets stored on the affected system.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential control by malicious actors.

Yes, Vulert provides real-time monitoring and alerts for open-source vulnerabilities using just the package-lock.json file.

It is advisable to avoid using the pinecone-js package until it has been thoroughly reviewed and verified as safe by the community.

How To Fix

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

npm uninstall pinecone-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