Critical Malicious Code Vulnerability in mcp-polymarket Package

mcp-polymarket Updated 25 Nov 2025

Summary

25/11/2025
CRITICAL
No i
Critical
Not published

MAL-2025-191465: Malicious code in mcp-polymarket (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 mcp-polymarket package is an npm library designed for interacting with the Polymarket platform, which allows users to trade on the outcome of various events. This package is utilized in applications that require real-time data and interaction with the Polymarket API. However, it has been found to contain malicious code that compromises the security of any system where it is installed.

Vulnerability Detail

The vulnerability stems from the presence of embedded malicious code within the mcp-polymarket 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, and its ramifications include potential data breaches and complete control of the affected system by external entities. Users are advised to treat any system running this package as compromised.

How To Fix

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

npm uninstall mcp-polymarket

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 other than removing the package and securing your system. It is essential to monitor your system for any signs of compromise after the removal.

Conclusion

The mcp-polymarket package contains malicious code that poses a significant security risk. Immediate action is required to remove the package and secure any compromised systems. Users should remain vigilant and utilize tools like Vulert to monitor for future vulnerabilities.

See every vulnerability recorded for mcp-polymarket →

Share this vulnerability

FAQ

You should immediately uninstall the package using the command 'npm uninstall mcp-polymarket' and rotate any sensitive information stored on the affected system.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check your application without requiring any signup.

Failing to address this vulnerability can lead to unauthorized access to your system, data breaches, and potential exploitation of sensitive information.

No, there is currently no patch available for this package. The only solution is to uninstall it.

Regularly monitor your dependencies for vulnerabilities using tools like Vulert, and ensure that you only install packages from trusted sources.

How To Fix

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

npm uninstall mcp-polymarket

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