Which versions of polymarket-kit are malicious?

The following npm versions of polymarket-kit are flagged malicious: 2.4.1. Treat any of these as compromised.

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

polymarket-kit establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.

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

If polymarket-kit 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-kit part of a known attack campaign?

Yes — polymarket-kit is associated with the IN-MAL-2026-009235 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-kit 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-kit (version 2.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-kit across your stack and pipelines.

Malicious package

polymarket-kitnpm

polymarket-kit is a confirmed malicious npm package (MAL-2026-10071) that opens a backdoor for remote access (malicious version 2.4.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in polymarket-kit (npm)

MAL-2026-10071

Immediate action

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

npm uninstall polymarket-kit

What this malware does

Package name and description advertise a 'Polymarket API SDK', but the shipped code contains no Polymarket functionality. The exported getPlugin() helper fetches JSON from https://svganchordev.net/icons/106 and passes the response's credits field to a Function constructor invoked with require, module, process, Buffer, and related Node globals — giving the remote endpoint arbitrary code execution in the caller's Node.js process. The Polymarket branding and 'react/helper/svg' keywords are cover for a remote fetch-and-eval backdoor. The tarball also inadvertently ships an OpenSSH ed25519 private key (gitlab) belonging to the author, which does not harm the installer but should be rotated by the maintainer.

Malicious versions

1 flagged

2.4.1

Indicators of compromise (SHA-256)

63a4eba33a56521a94e4e0b3ab2923d58b0c5cd398c791e36433536591a1d6ff

Detection & response playbook

Backdoor / remote access

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for polymarket-kit (version 2.4.1). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-kit across your stack and pipelines.
If you installed it — respond
polymarket-kit establishes remote access, so treat any host that installed it as fully compromised. Isolate the machine, remove the package, rotate all credentials it could reach, and rebuild from a trusted image rather than cleaning in place — a backdoor may have planted additional persistence.
Did it already run?
If polymarket-kit 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-kit 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-kit on npm has been identified as a malicious package (version 2.4.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009235

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

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

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database