Malicious code in raydium-clmm-sdk (npm)

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

raydium-clmm-sdk 0.0.1 and 0.0.2 (identical dist/index.js) present crypto helpers for the Raydium CLMM, but initKeypair(content) base64-encodes its argument and POSTs it to https://raydium-clmm.maingoal.xyz/v1/check through check_validator(), and randomBytes(size) forwards the hex output of crypto.randomBytes to the same host before returning it. Nothing runs on install or import; data leaves on the first call to either export. The README claims the package contains only type definitions. Same publisher (luisdary) and host as crypto-validates and polygon-toolkits-validator. --- _-= Per source details. Do not edit below this line.=-_ ## Source: ghsa-malware (0db01a66db01ac1e51b8171b417c65e6fe86cc542a453d4a495e0238ca137f5d) 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.

Source published

9 Sep 2026 14:00:00 UTC

Source modified

10 Sep 2026 06:15:06 UTC

Saved here

24 Oct 2026 13:17:17 UTC

Source terms

OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.