Which versions of polymarket-data are malicious?

The following PyPI versions of polymarket-data are flagged malicious: 2.0.0, 2.0.1. Treat any of these as compromised.

How do I remediate polymarket-data if I installed it?

polymarket-data is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed polymarket-data — how do I know if it already compromised me?

If polymarket-data was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is polymarket-data part of a known attack campaign?

Yes — polymarket-data is associated with the 2026-05-polymarket-data, RLMA-2026-02105 campaign. Packages in the same campaign often share infrastructure and payloads, so check whether any related packages are also in your dependency tree.

How do I find polymarket-data across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for polymarket-data (2 malicious versions).

Malicious package

polymarket-dataPyPI

Advisory published May 30, 2026Updated Jul 9, 2026

polymarket-data is a confirmed malicious PyPI package (MAL-2026-5086) that steals credentials and exfiltrates sensitive data (malicious versions 2.0.0, 2.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in polymarket-data (PyPI)

MAL-2026-5086

Immediate action

Remove the package, then rotate any secrets the build/runtime could reach.

pip uninstall polymarket-data

What this malware does

The package attempts to exfiltrate sensitive data related to cryptocurrencies and API keys, as well as establish persistence. Likely related to 2026-05-polymarket-data-fetcher.

Category: MALICIOUS - The campaign has clearly malicious intent, like infostealers.

Campaign: 2026-05-polymarket-data

Reasons (based on the campaign):

crypto-related
exfiltration-crypto
exfiltration-credentials
persistence

Malicious versions

2 flagged

2.0.02.0.1

Indicators of compromise (SHA-256)

a690aea77d0d48fae2a4f500f434cc5d4fb5cde042b7b902b0ee647b97921dc4

8a855b177aec530b370028cfbabbfd0aca67e9735d7b3fd2f2010440050eba57

Detection & response playbook

Credential / info stealer

Find it
Search your lockfiles and build artifacts for polymarket-data (2 malicious versions).
If you installed it — respond
polymarket-data is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If polymarket-data was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. polymarket-data on PyPI has been identified as a malicious package (versions 2.0.0, 2.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

2026-05-polymarket-dataRLMA-2026-02105

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · analyst
ReversingLabs · finder

Detect & block this

O3 blocks polymarket-data-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database