Which versions of quickswap-default-token-list are malicious?

The following npm versions of quickswap-default-token-list are flagged malicious: 1.5.16. Treat any of these as compromised.

How do I remediate quickswap-default-token-list if I installed it?

quickswap-default-token-list is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.

I already installed quickswap-default-token-list — how do I know if it already compromised me?

If quickswap-default-token-list 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 quickswap-default-token-list part of a known attack campaign?

Yes — quickswap-default-token-list is associated with the GHSA-4jf5-q7wr-9jgf 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 quickswap-default-token-list 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 quickswap-default-token-list (version 1.5.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging quickswap-default-token-list across your stack and pipelines.

Malicious package

quickswap-default-token-listnpm

Malicious code in quickswap-default-token-list (npm) Remove it immediately and rotate any exposed credentials.

MAL-2025-191407

Immediate action

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

npm uninstall quickswap-default-token-list

What this malware does

The package quickswap-default-token-list was found to contain malicious code.

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.

This package was compromised by the Sha1-Hulud: The Second Coming NPM worm. The malicious payload steals tokens and credentials and publishes them to GitHub. The worm will propogate itself to NPM packages the user owns and establish persistence is a GitHub action. The package may also destroy the user's home directory.

Malicious versions

1 flagged

1.5.16

Indicators of compromise (SHA-256)

a2b3acb081e56f1e7de5db89e19d81512267b02695bb5ede8644183a69e65203

703b952c207c60490f8c07fd7938a5fb3aef60adf35b4bdfd04785c3a9404b63

b4b3edd2c22842f2e65d4b70184d67745f91228b3e8a335561def81900e84ddd

Detection & response playbook

Credential / info stealer

Find it
Scan your lockfiles (package-lock.json, pnpm-lock.yaml, yarn.lock, requirements.txt, poetry.lock, etc.) and build artifacts for quickswap-default-token-list (version 1.5.16). O3 Security's supply-chain scanner checks every dependency against known-malicious package intelligence at install time and in CI, flagging quickswap-default-token-list across your stack and pipelines.
If you installed it — respond
quickswap-default-token-list is built to steal secrets, so assume every credential the build or runtime could read is compromised. Remove it from your project and lockfile, then rotate ALL exposed secrets — npm/registry tokens, cloud keys, CI/CD secrets, SSH keys, and any .env values — from a known-clean machine. Audit logs for unauthorized use of those credentials.
Did it already run?
If quickswap-default-token-list 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 quickswap-default-token-list 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. quickswap-default-token-list on npm has been identified as a malicious package (version 1.5.16 flagged). It should be removed immediately — do not install or keep it in your dependency tree.

Campaign

GHSA-4jf5-q7wr-9jgf

References

Credits

Amazon Inspector · finder

Detect & block this

O3 blocks quickswap-default-token-list-class packages before install and in CI — and if it already ran, its runtime egress monitoring catches the credential exfiltration and severs the channel.

Malware detection Runtime egress monitoring