Which versions of polymarket-stake-maths are malicious?

The following npm versions of polymarket-stake-maths are flagged malicious: 3.5.2. Treat any of these as compromised.

How do I remediate polymarket-stake-maths if I installed it?

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

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

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

Malicious package

polymarket-stake-mathsnpm

Malicious code in polymarket-stake-maths (npm) Remove it immediately and rotate any exposed credentials.

MAL-2026-6439

Immediate action

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

npm uninstall polymarket-stake-maths

What this malware does

On npm install, the package's postinstall script (scripts/install-check.cjs) fetches a JSON config from https://log-taker.store/config/stake-math-sync.json, reads a peerBundle URL from that config, downloads the referenced.tgz, extracts it into a .peer/ directory, runs npm install --omit=dev inside the extracted tree, and then require()s peer-math.js and invokes syncSession(). There is no pinning, no hash or signature verification, and the config host is fully attacker-mutable, so every install executes whatever bytes log-taker.store is currently serving. The nested npm install is an independent execution vector: any lifecycle hook declared in the attacker-supplied package.json runs with the installer's privileges. The cover-story naming (peerBundle, syncSession, install-check, PSM_INSTALL_FAST) and the two-hop config-then-bundle indirection keep the actual payload URL out of the published tarball, defeating naive registry scans. The README advertises only Kelly stake math helpers; remote code execution is not part of the stated purpose.

Malicious versions

1 flagged

3.5.2

Indicators of compromise (SHA-256)

657363aaa0b94385d30a26c1f4ee67923b0d877975850ad08f8364c2a901d8e7

Detection & response playbook

Malicious package

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for polymarket-stake-maths (version 3.5.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polymarket-stake-maths across your stack and pipelines.
If you installed it — respond
Remove polymarket-stake-maths 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-stake-maths 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-stake-maths 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-stake-maths on npm has been identified as a malicious package (version 3.5.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-007461

References

npmjs.com

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks polymarket-stake-maths-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