If you hold cryptocurrency, you probably think about securing your private keys, using strong passwords, and maybe keeping your seed phrase in a safe place. But a massive attack that began on September 5, 2025, revealed a threat most crypto users never consider: the software supply chain. Attackers compromised eighteen widely-used software packages that were collectively downloaded over two billion times per week, and they used this access to target cryptocurrency wallets across six different blockchains. Here is what happened, why it matters to you, and what you can do about it.
The Basics
Every website and application you use is built on top of other software — packages, libraries, and frameworks created by developers around the world. When you visit a cryptocurrency exchange in your browser, that website loads dozens or even hundreds of these software packages behind the scenes. Most of this software is open source, meaning anyone can inspect it, but also that it relies on individual developers to maintain and secure it.
A supply chain attack happens when bad actors compromise one of these software packages. Instead of attacking you directly, they attack the tools that were used to build the applications you trust. Think of it like a criminal tampering with the water supply instead of trying to break into individual houses — one compromise affects everyone downstream.
In the September 2025 attack, criminals sent a fake email to a developer named Josh Junon, who maintains a popular software tool called chalk. The email looked like it came from npm, the official software repository, and warned that his account would be locked unless he updated his security settings. The email was so convincing — likely written with the help of artificial intelligence — that Junon entered his credentials into a fake website, giving attackers full access to his account.
Within sixteen minutes, the attackers had injected malicious code into chalk and seventeen other packages. This code was designed to intercept cryptocurrency transactions in web browsers, targeting Bitcoin, Ethereum, Solana, Tron, Litecoin, and Bitcoin Cash — essentially every major network.
Why It Matters
This attack matters because it reveals a fundamental vulnerability in how cryptocurrency security works today. You can have the strongest password in the world, use two-factor authentication on every account, and store your seed phrase in a bank vault — but if the website you use to send or receive cryptocurrency has loaded a compromised software package, your transactions can be silently redirected to an attacker wallet.
The scale is staggering. The compromised packages were downloaded over 2.6 billion times across all versions. Any cryptocurrency platform, exchange, or wallet interface that used these packages became a potential attack vector. With Bitcoin trading near $110,651 and Ethereum at $4,307 on September 5, 2025, the financial stakes were enormous.
Fortunately, the attack was detected and contained quickly. Direct financial losses were limited to approximately $500 in cryptocurrency. But the incident demonstrated that the attack vector is viable, and future attacks could be far more damaging if they go undetected for longer.
Getting Started Guide
So what can you do to protect yourself? Here are practical steps every cryptocurrency user should take.
First, use a hardware wallet for any significant cryptocurrency holdings. Hardware wallets like Ledger or Trezor sign transactions on the physical device itself, independent of what is happening in your browser. Even if a compromised software package tries to redirect your transaction, the hardware wallet displays the actual transaction details on its screen for you to confirm. If the details look wrong, you simply decline the transaction.
Second, verify transaction details before confirming. Whether you are using a hardware wallet or a software wallet, always check the recipient address and amount carefully. Supply chain attacks rely on users not noticing that their transaction is being redirected.
Third, limit your exposure to web-based wallet interfaces. Browser extensions and web wallets are convenient, but they are inherently more vulnerable to supply chain attacks because they operate within the browser environment where compromised packages can interfere. For large holdings, prefer desktop applications or hardware wallets that operate outside the browser.
Fourth, keep your software updated. When security incidents like the npm attack are discovered, software providers release patches. Using the latest versions of your wallet software, browser, and operating system ensures you benefit from these fixes.
Fifth, diversify your access methods. Do not rely on a single wallet or platform for all your cryptocurrency needs. If one platform is compromised, having assets spread across multiple independent wallets limits your exposure.
Common Pitfalls
Many cryptocurrency users fall into traps that increase their vulnerability to supply chain attacks. The most common pitfall is assuming that because a website or wallet looks legitimate, the underlying software is safe. The npm attack proved that even the most popular and trusted software packages can be compromised. Appearance of legitimacy is not the same as actual security.
Another pitfall is ignoring transaction confirmation details. When your wallet asks you to confirm a transaction, it is tempting to just click confirm without carefully reading the address and amount. This is exactly what supply chain attacks exploit — the assumption that the transaction you see matches the one you intended.
A third pitfall is using the same wallet for everyday transactions and long-term storage. Your everyday wallet inevitably interacts with more websites and applications, increasing its exposure to potential supply chain compromises. Long-term holdings should be kept in cold storage on a hardware wallet that rarely connects to any online service.
Finally, do not assume that two-factor authentication protects you from supply chain attacks. While 2FA is essential for protecting your account access, it does nothing to prevent malicious code from intercepting transactions within your browser. These are different threat vectors that require different defenses.
Next Steps
The cryptocurrency ecosystem is evolving rapidly, and the September 2025 npm attack is likely just the beginning of supply chain threats targeting digital assets. As a crypto user, your best defense is to understand the threat, adopt hardware wallets for significant holdings, and stay informed about security incidents that could affect the platforms you use.
Consider subscribing to security advisory feeds from the wallet providers and exchanges you use. When incidents like the npm attack occur, these organizations typically publish guidance on whether their users are affected and what steps to take. Staying informed allows you to respond quickly and minimize your exposure.
The bottom line: supply chain security is not just a concern for developers and security professionals. It affects every cryptocurrency user, and taking basic precautions can make the difference between keeping your assets safe and losing them to an attack you never saw coming.
Disclaimer: This article is for informational purposes only and does not constitute financial or security advice. Always conduct your own research and consult with qualified professionals before making security decisions.
npm requiring 2FA for maintainers of packages with over a billion downloads should have happened years ago. the fact it still isnt mandatory is a choice not an oversight
sixteen minutes from phishing email to malicious code injected into chalk. supply chain attacks are a speed game and developers are the weakest link
the chalk compromise took 16 minutes from phishing email to malicious code injection. supply chain attacks are a speed game
Hana Yoshida 16 minutes from phishing to malicious code is terrifying. no CI/CD pipeline can catch something that fast if the maintainer credentials are valid
Formal verification should be mandatory for high-value protocols
Real-time monitoring tools are getting better at catching exploits early
Bridge security is still the weakest link in the ecosystem
airdrop hunter is right but the real issue is npm having no 2FA requirement for maintainers of packages with 2 billion weekly downloads. one email compromise and its game over
Ravi is right. npm having no 2FA for maintainers of packages with 2 billion weekly downloads is negligence. one email compromise and its game over