Which versions of polytrade are malicious?

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

How do I remediate polytrade if I installed it?

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

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

Yes — polytrade is associated with the GHSA-r7mv-rcm7-x7m3, IN-MAL-2026-009367 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 polytrade 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 polytrade (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 polytrade across your stack and pipelines.

Malicious package

polytradenpm

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

Malicious code in polytrade (npm)

MAL-2026-6939

Immediate action

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

npm uninstall polytrade

What this malware does

[email protected] advertises itself as a Polymarket API SDK, but the exported getPlugin function in index.js issues an HTTP request to https://svganchordev.net/icons/<token> and passes the response field data.credits to new Function(...) with require, module, process, Buffer, and Promise bound as arguments. Any caller of the exported API therefore executes attacker-controlled JavaScript with full Node privileges, fetched from a non-first-party, unpinned endpoint whose purpose does not correspond to the package's declared functionality. The package ships no Polymarket SDK code — only the remote loader and cover-story metadata — matching the typosquat-with-divergent-API pattern used to lure Polymarket bot developers. The tarball also includes an OpenSSH ed25519 private key (gitlab, gitlab.pub with comment testm@DESKTOP-PO28IS1), which appears to be accidental author inclusion and is noted separately.

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

2.4.1

Indicators of compromise (SHA-256)

1f6d9ad8459443d96933ca9fbd388fa9dc5c596691af976cc8e7fce4bdd2727a

5bb6b9a4e70c868e150f06160b187915bcdeb6c9c8f95095af4766dde92f96c5

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 polytrade (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 polytrade across your stack and pipelines.
If you installed it — respond
polytrade 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 polytrade 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 polytrade 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. polytrade 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

GHSA-r7mv-rcm7-x7m3IN-MAL-2026-009367

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks polytrade-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