MAL-2026-16087 Malicious code in polygon-toolkits-validator (npm)

[email protected] exports Node crypto helper wrappers, but validate(input) base64-encodes its argument and POSTs it to https://raydium-clmm.maingoal.xyz/v1/check as {action: "validator", content: btoa(input)} through check_validator() in dist/index.js, then returns true without validating anything, and randomBytes(size) forwards the hex output of crypto.randomBytes to the same host before returning it, so any key or nonce generated through it is disclosed at creation. Nothing runs on install or import; the send happens on the first call to either export. dist/index.js is the same file as [email protected] from the same npm account (luisdary), which also published raydium-clmm-sdk and pumpswap-sdk-v1 with the same function against *.maingoal.xyz. The check_validator shape matches MAL-2026-4642, MAL-2026-10640 and MAL-2026-10641, which used other hosts.

The package ships only a minified dist bundle that re-exports familiar node:crypto names (createCipheriv, createDecipheriv, createPrivateKey, randomBytes, checkPrime, scrypt), presenting itself as a drop-in crypto shim. Two exported paths covertly transmit sensitive data to a hardcoded remote host: randomBytes(n) generates bytes via crypto.randomBytes(n).toString('hex') and then passes the hex string to an internal check_validator() before returning it, and the exported validate() likewise passes its caller-supplied argument to check_validator(). check_validator() POSTs the value, base64-encoded, to https://raydium-clmm.maingoal.xyz/v1/check with body {action:"validator",content:btoa(e)}. The destination is hardcoded, not caller-configurable, and unrelated to the declared 'Polygon toolkits validator' purpose. Callers use randomBytes for keys, IVs, nonces, and seeds, and pass sensitive strings (private keys, mnemonics, transaction payloads) to validate(); those values are transmitted to the operator on every call, enabling reproduction of derived keys/nonces and disclosure of caller inputs.

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.