Which versions of @polymarket-developers/clob-client are malicious?

The following npm versions of @polymarket-developers/clob-client are flagged malicious: 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.1.1. Treat any of these as compromised.

How do I remediate @polymarket-developers/clob-client if I installed it?

Remove @polymarket-developers/clob-client from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.

I already installed @polymarket-developers/clob-client — how do I know if it already compromised me?

If @polymarket-developers/clob-client was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is @polymarket-developers/clob-client part of a known attack campaign?

Yes — @polymarket-developers/clob-client is associated with the RLMA-2026-01046 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-developers/clob-client across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for @polymarket-developers/clob-client (5 malicious versions).

Malicious package

@polymarket-developers/clob-clientnpm

Advisory published Mar 18, 2026Updated Mar 23, 2026

@polymarket-developers/clob-client is a confirmed malicious npm package (MAL-2026-1635) that executes malicious code on install (malicious versions 1.0.7, 1.0.8, 1.0.9…). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in @polymarket-developers/clob-client (npm)

MAL-2026-1635

Immediate action

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

npm uninstall @polymarket-developers/clob-client

What this malware does

The package @polymarket-developers/clob-client was found to contain malicious code.

Malicious versions

5 flagged

1.0.71.0.81.0.91.1.01.1.1

Indicators of compromise (SHA-256)

e29eb24d991ea515f487658796596a71f9423b67ca0072ff01c288de78b64fbb

345ca83f0d4f9589714459a50b08e9f733a7d56bbb131b029748ad244a2d447b

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for @polymarket-developers/clob-client (5 malicious versions).
If you installed it — respond
Remove @polymarket-developers/clob-client from your project and lockfile, then assume any secrets accessible to the build or runtime were exposed: rotate API keys, tokens, and credentials, and audit for unexpected outbound activity or persistence.
Did it already run?
If @polymarket-developers/clob-client was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. @polymarket-developers/clob-client on npm has been identified as a malicious package (versions 1.0.7, 1.0.8, 1.0.9, 1.1.0, 1.1.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

RLMA-2026-01046

Credits

Amazon Inspector · finder
ReversingLabs · finder

Detect & block this

O3 blocks @polymarket-developers/clob-client-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the malicious outbound activity and severs the channel.

Malware detection Runtime egress monitoring

Explore

All malware advisories How O3 detects malware Vulnerability database