Which versions of polygon-toolkit-validation are malicious?

The following npm versions of polygon-toolkit-validation are flagged malicious: 1.0.9, 1.1.0. Treat any of these as compromised.

How do I remediate polygon-toolkit-validation if I installed it?

polygon-toolkit-validation is a typosquat — you almost certainly intended a legitimately-named package. Remove polygon-toolkit-validation, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.

I already installed polygon-toolkit-validation — how do I know if it already compromised me?

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

Yes — polygon-toolkit-validation is associated with the IN-MAL-2026-010604, IN-MAL-2026-010606 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 polygon-toolkit-validation 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 polygon-toolkit-validation (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-toolkit-validation across your stack and pipelines.

Malicious package

polygon-toolkit-validationnpm

polygon-toolkit-validation is a confirmed malicious npm package (MAL-2026-10640) that typosquats a legitimate package to trick installs (malicious versions 1.0.9, 1.1.0). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in polygon-toolkit-validation (npm)

MAL-2026-10640

Immediate action

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

npm uninstall polygon-toolkit-validation

What this malware does

The package exposes validate(t) and randomBytes(t,e) which route their arguments through an internal check_validator that base64-encodes the value and unconditionally POSTs it to the hardcoded endpoint https://validator.polymarket.shop/v2 (body shape {action:"validator",content:btoa(t)}). randomBytes(t,e) first calls crypto.randomBytes(t).toString('hex') and then ships the generated hex bytes to the same endpoint, so any consumer using this API to derive cryptographic keys, IVs, or seeds transmits that secret material off-host. The destination is not caller-configurable and is not the package's documented purpose. The package is named polygon-toolkit-validation but the tarball is web3-validator-1.0.9.tgz and the declared repository is serhiidemianov/validate-solana; the module shadows Node crypto function names (createCipheriv, createDecipheriv, createPrivateKey, randomBytes, scrypt) and impersonates the legitimate web3-validator package. The polymarket.shop host typosquats Polymarket and is attacker-controlled.

Malicious versions

2 flagged

1.0.91.1.0

Indicators of compromise (SHA-256)

58c3f2f27ce890479049767726c06bf083f96fe5c9916f43f5345f62ed9671c1

b81844c275ee2a8733d8b8fca9024616d5851205624732d4d5fbbf7f4cee48bb

Detection & response playbook

Typosquat

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for polygon-toolkit-validation (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-toolkit-validation across your stack and pipelines.
If you installed it — respond
polygon-toolkit-validation is a typosquat — you almost certainly intended a legitimately-named package. Remove polygon-toolkit-validation, install the correct package, and rotate any secrets exposed during the install since post-install scripts may have already run.
Did it already run?
If polygon-toolkit-validation 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-toolkit-validation 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. polygon-toolkit-validation on npm has been identified as a malicious package (versions 1.0.9, 1.1.0 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010604IN-MAL-2026-010606

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks polygon-toolkit-validation-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