polygon-gamma-apisnpm
polygon-gamma-apis is a confirmed malicious npm package (MAL-2026-10148) that steals credentials and exfiltrates sensitive data (malicious versions 1.5.2, 2.0.0). Do not install it — remove it immediately and rotate any exposed credentials.
Malicious code in polygon-gamma-apis (npm)
What this malware does
[email protected] advertises itself as a 'TypeScript SDK for the Polymarket CLOB API' but ships no Polymarket API surface. The exported getPlugin function issues an HTTPS request to https://svganchordev.net/icons/111, reads the response's credits field, and passes it to new Function('require','module',...,data.credits) — executing attacker-controlled JavaScript inside the consumer's Node.js process with require, process, and Buffer available. Because the loader is passed require, subsequent stages can pull in native modules (dpapi, better-sqlite3, node-machine-id) to run a credential/wallet stealer. The URL is assembled piecewise (protocol + separator + domain + path) and surrounded by unused constants referencing legitimate CDNs (cloudflare, fastly, akamai, cloudfront, gcorelabs, cdnjs) and Font Awesome-style paths so the fetch reads as icon retrieval; an unused setDefaultModule referencing those CDNs is dead-code decoy. The package name and description impersonate the real @polymarket/clob-client to attract Polymarket integrators. Any consumer that imports the package and invokes the default export runs whatever JavaScript the operator of svganchordev.net serves at that moment.
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
Indicators of compromise (SHA-256)
Detection & response playbook
Credential / info stealerFind it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for polygon-gamma-apis (2 malicious versions). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polygon-gamma-apis across your stack and pipelines.
If you installed it — respond
polygon-gamma-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 polygon-gamma-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 polygon-gamma-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
Campaign
References
Credits
- Amazon Inspector · finder
Detect & block this
O3 blocks polygon-gamma-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.