Critical Malicious Code Vulnerability in quickswap-default-token-list Package
Summary
MAL-2025-191407: Malicious code in quickswap-default-token-list (npm). Affects quickswap-default-token-list versions 1.5.16. No fix is published. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
The quickswap-default-token-list package is an npm library used for managing token lists in decentralized finance applications. It allows developers to easily integrate token information into their projects. However, this package has been compromised, leading to severe security risks for any application utilizing it.
Vulnerability Detail
The vulnerability originates from a malicious payload introduced by the Sha1-Hulud: The Second Coming NPM worm. This worm is designed to steal tokens and credentials from affected systems and publish them to GitHub. It can propagate itself to other npm packages owned by the user and establish persistence through GitHub actions. Additionally, it poses a risk of destroying the user's home directory, making it a critical threat to system integrity and security.
How To Fix
This package is malicious. Remove it and rotate any credentials it could have accessed.
npm uninstall quickswap-default-token-listIf it arrived as a transitive dependency, remove the package that pulled it in, then reinstall.
Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →
Workaround
As a temporary measure, you can isolate the affected application from the internet and monitor for any unusual activity. However, this does not eliminate the risk, and complete removal of the package is recommended.
Conclusion
The quickswap-default-token-list package has been compromised by a malicious worm that poses significant risks to users. Immediate action is required to remove the package and secure any affected systems. Utilizing tools like Vulert can help monitor for such vulnerabilities in the future.
See every vulnerability recorded for quickswap-default-token-list →
FAQ
Immediately remove the package and rotate any secrets or keys stored on the affected machine.
The worm propagates by infecting npm packages owned by the user and establishing persistence through GitHub actions.
Yes, you can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without any signup.
Failure to address this vulnerability can lead to compromised credentials, unauthorized access to your systems, and potential data loss.
Yes, Vulert can monitor and alert you in real-time for open-source vulnerabilities in your software using just package-lock.json.
