Which versions of pumpswap-sdk-v1 are malicious?

The following npm versions of pumpswap-sdk-v1 are flagged malicious: 0.0.1. Treat any of these as compromised.

How do I remediate pumpswap-sdk-v1 if I installed it?

Remove pumpswap-sdk-v1 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 pumpswap-sdk-v1 — how do I know if it already compromised me?

If pumpswap-sdk-v1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Is pumpswap-sdk-v1 part of a known attack campaign?

Yes — pumpswap-sdk-v1 is associated with the GHSA-5qr5-f8q7-r844 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 pumpswap-sdk-v1 across my projects, lockfiles, and CI pipelines?

Search your lockfiles and build artifacts for pumpswap-sdk-v1 (version 0.0.1).

Malicious package

pumpswap-sdk-v1npm

Advisory published Sep 9, 2026Updated Sep 10, 2026

pumpswap-sdk-v1 is a confirmed malicious npm package (MAL-2026-16088) that executes malicious code on install (malicious version 0.0.1). Do not install it — remove it immediately and rotate any exposed credentials.

Malicious code in pumpswap-sdk-v1 (npm)

MAL-2026-16088

Immediate action

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

npm uninstall pumpswap-sdk-v1

What this malware does

[email protected] presents crypto helpers for the PumpSwap SDK, but validate(input) base64-encodes its argument and POSTs it to https://pumpswap-sdk.maingoal.xyz/v1/check through check_validator() in dist/index.js, and randomBytes(size) forwards the hex output of crypto.randomBytes to the same host before returning it. Nothing runs on install or import; the send happens on the first call. The bundled pumpswap-sdk.rar holds a copy of the same source. Same publisher (luisdary) as raydium-clmm-sdk, crypto-validates and polygon-toolkits-validator.

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

0.0.1

Indicators of compromise (SHA-256)

542bdf00bacaa82bf9fea14d555598448a7bbff0f9514b2dd780be9e6d000c2a

Detection & response playbook

Malicious package

Find it
Search your lockfiles and build artifacts for pumpswap-sdk-v1 (version 0.0.1).
If you installed it — respond
Remove pumpswap-sdk-v1 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 pumpswap-sdk-v1 was installed, its post-install payload may already have run. Removing the package does not undo that — check outbound connections and credential use from the install window onward.

Frequently asked questions

No. pumpswap-sdk-v1 on npm has been identified as a malicious package (version 0.0.1 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-5qr5-f8q7-r844

References

Credits

pkgwarden · finder

Detect & block this

O3 blocks pumpswap-sdk-v1-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