NPM Attack: Javascript Library Compromise Goes After Bitcoin Wallets
Bitcoin Magazine NPM Attack: Javascript Library Compromise Goes After Bitcoin Wallets A major NPM developer, qix, has had their account compromised. It was used to push malware that targets and searches for bitcoin and c...
Archive context
Older archive item. Useful for background and entity history, but not a fresh market-moving signal.
Bitcoin Magazine
NPM Attack: Javascript Library Compromise Goes After Bitcoin Wallets
A major NPM developer, qix, has had their account compromised. It was used to push malware that targets and searches for bitcoin and cryptocurrency wallets on users devices. If detected, the malware would patch the code functions used to coordinate transaction signing, and replace the address a user is trying to send money to with one of the malware creator’s own addresses.
This should mostly be a concern for web wallet users, so in the Bitcoin ecosystem Ordinals or Runes/other token users, as unless an update for your normal software wallet happened to be pushed just earlier today with the compromised dependency, or if your wallet dynamically loads code directly from the wallet back end bypassing the app-store, you should be fine.
NPM is a package manager for Node.js, a popular Javascript framework. This means it is used to grab large sets of pre-written code used for common functionality to be integrated into different programs without the developer having to rewrite basic functions themselves.
The targeted packages were not cryptocurrency specific, but packages used by countless numbers of normal applications built with Node.js, not just cryptocurrency wallets.
If you are using a hardware wallet in combination with your web wallet, take extra care to verify on the device itself that the destination address you are sending too is correct before signing anything.
If you are using software keys in the web wallet itself, it would be advisable to not open them or transact until you are certain you are not running a vulnerable version of the wallet. The safest course of action would be waiting for an announcement from the team developing the wallet you use.
This post NPM Attack: Javascript Library Compromise Goes After Bitcoin Wallets first appeared on Bitcoin Magazine and is written by Shinobi.
Why this matters
This bitcoin story adds another data point to the current market tape and is useful when read alongside nearby source coverage.
Original source
Read on Bitcoin MagazineRelated market context
Europol warns crypto wallets are the weak spot for future quantum attacks
The crypto industry must urgently adopt quantum-resistant cryptography to prevent future vulnerabilities and secure digital assets...
Europol Urges Crypto Wallet Providers to Start Testing Post-Quantum Upgrades Now
Europol published two reports on Wednesday about the security risks of quantum computing, and the one on cryptocurrencies names wa...
Europol says quantum computing won’t break Bitcoin, but some wallets are exposed
Quantum computing's threat to Bitcoin highlights the need for proactive wallet security, shifting responsibility to individual use...
US government moves $470 million in seized crypto to Coinbase wallets, raising Bitcoin sale questions
The US government moved about $470 million in seized crypto to likely Coinbase Prime addresses, according to Arkham, reviving ques...
Cardano’s Programmable Token Standard Goes Live With Built-In KYC and Freeze Controls
The Cardano Foundation announced on Wednesday at TOKEN2049 that CIP-0113, Cardano’s programmable token standard, is live on Cardan...
Samsung Wallet to add USDC transfers for US Galaxy users in October
Eligible US Galaxy will be able to send USDC to crypto wallets and transfer funds to bank accounts in more than 60 countries.