Criticalnpm1 affected version

swap-sdk-87

swap-sdk-87 has 1 version on the npm registry flagged in 1 incident we track. Other versions of this package are not implicated - only the exact versions listed below were named by the source advisories.

Affected versions

Check what you actually have installed with npm ls swap-sdk-87.

swap-sdk-87@4.63.78

The incident that flagged it

Critical9 Jun 2026

SeedSweep: 10-package npm crypto-wallet drainer published by `aicrypto-xzggg`

On 2026-06-09 between 03:23 and 03:57 UTC the brand-new npm account aicrypto-xzggg (vipsyria88@gmail.com) shipped 10 Web3-flavoured packages - wallet-sdk-9, swap-sdk-87, defi-tools-39, farming-tools-12, and six others - each carrying an identical postinstall payload that reads wallet keystores, seed-phrase files, SSH keys, and .env files across six chains and exfiltrates them to Telegram bot id 8227918239. npm unpublished every release ~8 hours later. Disclosed by Xygeni as the SeedSweep campaign.

Versions named here: 4.63.78

What to do if you installed one of these

Treat the machine as compromised rather than simply upgrading. Packages in these incidents typically execute at install time, so the payload has already run with whatever credentials were in the environment.

1.Rotate every credential that machine or CI job could reach - registry tokens, cloud keys, SSH keys, CI secrets - from a different machine.
2.Pin to a version not listed above, then reinstall from a clean lockfile.
3.Clear caches and private mirrors. Artifactory, Nexus, Verdaccio, and devpi routinely keep serving a tarball after the public registry has pulled it.
4.Read the incident write-up above - recommended actions differ per incident, and some have specific indicators of compromise worth grepping your logs for.

Check your whole project

swap-sdk-87 is one of many packages in these incidents, and it is usually pulled in as a transitive dependency rather than one you installed directly. Paste your package-lock.json to check every dependency at once - it runs in your browser and nothing is uploaded.

Check my package-lock.json All flagged npm packages

Other packages in the same incident

If swap-sdk-87 is in your tree, these are worth checking too - they were published by the same campaign.

See the full incident

Version data comes from the public advisories cited on each incident page. We list only versions those advisories name - we don't infer additional ones. Think this is wrong or incomplete? Tell us.