Which versions of polymarket-data-fetcher are malicious?

The following PyPI versions of polymarket-data-fetcher are flagged malicious: 1.2.4. Treat any of these as compromised.

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

polymarket-data-fetcher 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-fetcher — how do I know if it already compromised me?

If polymarket-data-fetcher was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.

Is polymarket-data-fetcher part of a known attack campaign?

Yes — polymarket-data-fetcher is associated with the 2026-05-polymarket-data-fetcher 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-fetcher across my projects, lockfiles, and CI pipelines?

Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for polymarket-data-fetcher (version 1.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-data-fetcher across your stack and pipelines.

Malicious package

polymarket-data-fetcherPyPI

Malicious code in polymarket-data-fetcher (PyPI) Remove it immediately and rotate any exposed credentials.

MAL-2026-4286

Immediate action

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

pip uninstall polymarket-data-fetcher

What this malware does

The code attempts to monitor the clipboard and replace copied cryptocurrency addresses, as well as establish persistence.

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

Campaign: 2026-05-polymarket-data-fetcher

Reasons (based on the campaign):

peristence-autorun
obfuscation
crypto-related
The package contains code to detect if it is running in a sandbox environment.
clipboard-modify
persistence

Malicious versions

1 flagged

1.2.4

Indicators of compromise (SHA-256)

b6b5ac8b803d36ef490adff8a4d3110c4030063bbd2345e4b23d1871909638e9

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for polymarket-data-fetcher (version 1.2.4). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-data-fetcher across your stack and pipelines.
If you installed it — respond
polymarket-data-fetcher 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-fetcher was ever installed, its post-install/runtime payload may have already executed. O3's L7 egress monitoring and runtime eBPF sensors detect the credential exfiltration or command-and-control callback after install and block the malicious outbound channel, so you catch and contain the actual compromise — not just the presence of the package.
How O3 protects you
O3 blocks polymarket-data-fetcher before install through its supply-chain scanner, and if it has already run, detects and severs the exfiltration or C2 callback at runtime through L7 egress monitoring and eBPF.

Frequently asked questions

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

Campaign

2026-05-polymarket-data-fetcher

References

bad-packages.kam193.eu

Credits

Kamil Mańkowski (kam193) · reporter

Detect & block this

O3 blocks polymarket-data-fetcher-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