Critical Malicious Code Vulnerability in polmarket Package

polmarket Updated 03 Mar 2026

Summary

03/03/2026
CRITICAL
No i
Critical
Not published

MAL-2026-1203: Malicious code in polmarket (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 polmarket package is an npm library designed for specific functionalities within JavaScript applications. It is utilized by developers to streamline certain processes in their projects. However, this package has been identified as containing malicious code, which poses significant security risks to any system that has it installed.

Vulnerability Detail

The vulnerability originates from the inclusion of malicious code within the polmarket package. This code can compromise the entire system where the package is installed, allowing unauthorized access to sensitive data such as secrets and keys. The severity of this issue is underscored by the fact that simply removing the package may not eliminate all traces of the malicious software, as full control of the compromised computer 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 polmarket

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, the best workaround is to uninstall the polmarket package entirely. You can do this by running the command: 'npm uninstall polmarket'. Additionally, consider using tools like Vulert to monitor your project for vulnerabilities. You can check if your application is affected by this vulnerability using the Vulert playground at https://vulert.com/scanner without any signup.

Conclusion

The discovery of malicious code within the polmarket package poses a serious threat to users and their systems. Immediate action is required to mitigate risks, including uninstalling the package and rotating sensitive information. Utilizing tools like Vulert can help in monitoring for such vulnerabilities in the future.

See every vulnerability recorded for polmarket →

Share this vulnerability

FAQ

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

You can use the Vulert playground at Vulert Scanner to check for vulnerabilities in your application without needing to sign up.

No, simply removing the package may not eliminate all malicious software. It is recommended to rotate all sensitive information stored on the affected computer.

Leaving the package installed can lead to unauthorized access to sensitive data and potential compromise of your entire system.

Regularly monitor your dependencies using tools like Vulert and ensure that you are using trusted packages from reputable sources.

How To Fix

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

npm uninstall polmarket

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