News for hackers. Stuff that matters.
Re:Ledger Wallet's LedgerHQ/connect-kit hit by supply chain ... by raghavsood on Thursday December 14, 2023 @08:41AM (#38641205)
A backdoored version of the package was pushed to NPM using leaked credentials from a GitHub Action[1] - this has been removed now[2].

[1]: https://twitter.com/bytes032/status/1735287204241461634

[2]: https://twitter.com/Ledger/status/1735291427100455293

Re:Ledger Wallet's LedgerHQ/connect-kit hit by supply chain ... by this_user on Thursday December 14, 2023 @10:59AM (#38642742)
So presumably they didn't even bother to sign their library to make sure that users can verify that it is an authorised build? This is exactly the kind of security practices that I expect from the so-called crypto "industry".
Re:Ledger Wallet's LedgerHQ/connect-kit hit by supply chain ... by waynesonfire on Thursday December 14, 2023 @01:05PM (#38644711)
but gpg is "complicated" I wouldn't even know how to verify the signature! Instead, I'd rather my wallet be drained instead of RTFM.
Re:Ledger Wallet's LedgerHQ/connect-kit hit by supply chain ... by VoidWhisperer on Thursday December 14, 2023 @09:08AM (#38641460)
It is concerning (although not surprising, I suppose) that they wouldn't have the option enabled to make it so that new contributors' PRs won't run github actions without approval.. although I guess without further detail on exactly what happened it is possible they do and someone who previously contributed did it which would've made that mitigation useless
Re:Ledger Wallet's LedgerHQ/connect-kit hit by supply chain ... by anotherhue on Thursday December 14, 2023 @08:55AM (#38641324)
Beware the term 'now' when CDNs are involved.