Which versions of polygon-toolkit-validator are malicious?

The following npm versions of polygon-toolkit-validator are flagged malicious: 1.1.2. Treat any of these as compromised.

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

polygon-toolkit-validator is a typosquat — you almost certainly intended a legitimately-named package. Remove polygon-toolkit-validator, 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-validator — how do I know if it already compromised me?

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

Yes — polygon-toolkit-validator is associated with the IN-MAL-2026-010605, GHSA-67fh-9pjj-6cpw 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-validator 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-validator (version 1.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polygon-toolkit-validator across your stack and pipelines.

Malicious package

polygon-toolkit-validatornpm

polygon-toolkit-validator is a confirmed malicious npm package (MAL-2026-10641) that typosquats a legitimate package to trick installs (malicious version 1.1.2). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in polygon-toolkit-validator (npm)

MAL-2026-10641

Immediate action

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

npm uninstall polygon-toolkit-validator

What this malware does

The package presents itself as a web3/polygon validator but its exported API silently relays caller-supplied data and generated cryptographic material to a hardcoded third-party host. The validate(content) export base64-encodes its input and POSTs it to https://polymarket.hanaai.online/v2 with {action:"validator",content:btoa(t)}. The randomBytes(n) export wraps node crypto's randomBytes and forwards the resulting hex string to the same endpoint via a check_validator() call before returning the bytes to the caller, so any key/IV/nonce derived from this function is disclosed to the operator of that host. The package name and bundled web3-validator-1.0.9.tgz file mimic the legitimate web3-validator library, consistent with a typosquat/impersonation lure. The remote endpoint is not documented or caller-configurable.

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

1.1.2

Indicators of compromise (SHA-256)

f56f0404b5e3f35ed475dae417f9351d4d149e163598eb72380fb6c025099e12

3a8284e0fd750df33fa07403851fb3e5ebef89cf00b02c212ec0e33069937842

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-validator (version 1.1.2). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging polygon-toolkit-validator across your stack and pipelines.
If you installed it — respond
polygon-toolkit-validator is a typosquat — you almost certainly intended a legitimately-named package. Remove polygon-toolkit-validator, 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-validator 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-validator 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-validator on npm has been identified as a malicious package (version 1.1.2 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

IN-MAL-2026-010605GHSA-67fh-9pjj-6cpw

References

Credits

Amazon Inspector · finder

Detect & block this

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