Which versions of polymarket-apis are malicious?

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

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

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

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

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

Malicious package

polymarket-apisnpm

polymarket-apis is a confirmed malicious npm package (MAL-2026-10067) that steals credentials and exfiltrates sensitive data (malicious version 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in polymarket-apis (npm)

MAL-2026-10067

Immediate action

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

npm uninstall polymarket-apis

What this malware does

The package impersonates the Polymarket brand (name polymarket-apis, author polymarket) but contains no Polymarket API integration. Its exported getPlugin function fetches JSON from https://svganchordev.net/icons/<token> and passes the response's credits field to the JavaScript Function constructor, executing the returned bytes with full Node context (require, module, exports, process, Buffer, __dirname). The remote URL is assembled from split string constants (protocol+separator+domain+path) and the surrounding code is framed as a benign icon/CDN helper (IconProvider, bearrtoken: 'logo') to disguise the eval. Because the fetched content is attacker-controlled and mutable, any caller invocation of the exported API runs arbitrary code on the installer with Node privileges. Declared runtime dependencies (@primno/dpapi, node-machine-id, better-sqlite3) are consistent with Windows credential and browser-data stealer payloads that the remote code can load. Package keywords (react, helper, svg) are inconsistent with the advertised Polymarket SDK purpose, confirming the cover-story framing.

Any computer that has this package installed or running should be considered fully compromised. All secrets and keys stored on that computer should be rotated immediately from a different computer. The package should be removed, but as full control of the computer may have been given to an outside entity, there is no guarantee that removing the package will remove all malicious software resulting from installing it.

Malicious versions

1 flagged

1.1.0

Indicators of compromise (SHA-256)

cd77c8861490c0b5607b4029f8f9e51f12efb83a6696fc51b953b0a3cde1356b

0cf3a190eff680afcf1cf8d5519bc3b46b32bd58fe5fe2b183a0f91bcfbc84d6

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-apis (version 1.1.0). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-apis across your stack and pipelines.
If you installed it — respond
polymarket-apis 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-apis 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-apis 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-apis on npm has been identified as a malicious package (version 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-009240GHSA-rwp8-c6qg-x8g3

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks polymarket-apis-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