TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Ledger's NPM account has been hacked

248 点作者 meehow超过 1 年前

21 条评论

lrvick超过 1 年前
And once again calls to allow optional signing support natively to NPM will be rejected citing that it might intimidate drive-by devs who do not want to learn to setup a yubikey or nitrokey for artifact signing.<p>I have talked to the NPM team about this multiple times over the last several years and they literally believe no signing at all is better than some devs feeling pressured to sign.<p>You need no stronger evidence of the NPM teams negligence than these two times they refused to even accept community contributed optional signing support saying they would come up with something better than PGP. Still waiting 10 years later.<p><a href="https:&#x2F;&#x2F;github.com&#x2F;npm&#x2F;npm&#x2F;pull&#x2F;4016">https:&#x2F;&#x2F;github.com&#x2F;npm&#x2F;npm&#x2F;pull&#x2F;4016</a><p><a href="https:&#x2F;&#x2F;github.com&#x2F;node-forward&#x2F;discussions&#x2F;issues&#x2F;29#issuecomment-144505785">https:&#x2F;&#x2F;github.com&#x2F;node-forward&#x2F;discussions&#x2F;issues&#x2F;29#issuec...</a><p>Meanwhile PGP secures the supply chain of the Linux distros that power the whole internet, and Debian signs hundreds of npm packages used in their dependency graph, but it is still not good enough for NPM.<p>You can use the well tested and rust-written Sequoia&#x2F;sq now and never touch GnuPG. You can also self certify your keys with keyoxide. The past complaints are largely moot and still people stick to their guns on this.<p><a href="https:&#x2F;&#x2F;openpgp.dev&#x2F;book&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;openpgp.dev&#x2F;book&#x2F;</a>
评论 #38647113 未加载
评论 #38650702 未加载
评论 #38646498 未加载
feross超过 1 年前
We&#x27;ve been building Socket [1] to detect and block this exact type of supply chain attack. Our Socket AI scanner [2] successfully detected this attack. It uses dozens of static signals combined with an LLM to detect novel attacks that evade traditional scanning tools.<p>This is what Socket AI produces when given @ledgerhq&#x2F;connect-kit 1.1.7 to analyze:<p>&gt; The obfuscated code block is highly suspicious and likely contains malicious behavior. The presence of obfuscation and the unclear purpose of the code raise significant red flags.<p>Feeling very proud of our team right now as this validates that our static analysis + LLM approach works well on novel malicious dependencies. If you&#x27;re interested, we maintain a listing of malicious packages detected by this system [3].<p>Small plug: If you’d like real-time protection against attacks like this, you can install Socket for GitHub to automatically scan every PR in your repo. The free plan is incredibly generous. If you do decide to install it, it’s important that you enable the ‘AI Detected Security Risk’ alert type in your Security Policy to activate this protection.<p>[1]: <a href="https:&#x2F;&#x2F;socket.dev" rel="nofollow noreferrer">https:&#x2F;&#x2F;socket.dev</a><p>[2]: <a href="https:&#x2F;&#x2F;socket.dev&#x2F;blog&#x2F;introducing-socket-ai-chatgpt-powered-threat-analysis" rel="nofollow noreferrer">https:&#x2F;&#x2F;socket.dev&#x2F;blog&#x2F;introducing-socket-ai-chatgpt-powere...</a><p>[3]: <a href="https:&#x2F;&#x2F;socket.dev&#x2F;npm&#x2F;issue&#x2F;malware" rel="nofollow noreferrer">https:&#x2F;&#x2F;socket.dev&#x2F;npm&#x2F;issue&#x2F;malware</a>
评论 #38646519 未加载
评论 #38646593 未加载
评论 #38653703 未加载
评论 #38645977 未加载
评论 #38646233 未加载
评论 #38645495 未加载
woah超过 1 年前
How did the exploit work? Obviously it looks really bad for Ledger to keep having these web security failures, but the entire point of a hardware wallet is to make it so that you don&#x27;t have to rely on the security of the code on your computer.<p>If the hardware wasn&#x27;t compromised (sounds like this was just JS), then there was no way for the exploit to take anyone&#x27;s private key. It sounds to me like the exploit would work by getting you to sign a transaction that would transfer out the funds, without the attacker ever getting your key.<p>The only way this is possible is if users are signing transactions on their Ledger without looking at them.<p>And this is place where the Ethereum community needs to look in the mirror. Blind signing is the default for using Ethereum with a Ledger. I&#x27;m not sure the technical reasons behind this, but I do happen to know that much of the information that gets signed is in very convoluted formats (meta transactions etc). This is not the case everywhere. Other ecosystems, like Cosmos, present the information to be signed in a plain text format that you can scroll through on the Ledger&#x27;s screen before you sign it.<p>Ethereum needs to put some serious effort into making sure that anything that gets signed can be viewed in a human-readable format before signing. Until then, hardware wallets are security theater.
评论 #38643895 未加载
评论 #38643938 未加载
评论 #38646524 未加载
zaphod420超过 1 年前
One of the comments on the github issue... <a href="https:&#x2F;&#x2F;github.com&#x2F;LedgerHQ&#x2F;connect-kit&#x2F;issues&#x2F;29">https:&#x2F;&#x2F;github.com&#x2F;LedgerHQ&#x2F;connect-kit&#x2F;issues&#x2F;29</a><p>&quot;The @ledgerhq&#x2F;connect-kit-loader allows dApps to load Connect Kit at runtime from a CDN so that we can improve the logic and UI without users having to wait for wallet libraries and dApps updating package versions and releasing new builds.<p>This looks like an extremely dangerous approach now, if I understand it correctly, connect-kit-loader trusts whatever the CDN throws at your dApps. So when connect-kit is comprised, all downstream dApps are automatically exposed.&quot;
评论 #38642794 未加载
评论 #38642131 未加载
nathell超过 1 年前
Just yesterday I watched a talk [0] at WarsawJS about LavaMoat [1], a set of tools to protect against malicious behaviour from npm dependencies. Guess it’s time to look into it deeper.<p>[0]: <a href="https:&#x2F;&#x2F;naugtur.pl&#x2F;pres3&#x2F;lava&#x2F;2023end.html" rel="nofollow noreferrer">https:&#x2F;&#x2F;naugtur.pl&#x2F;pres3&#x2F;lava&#x2F;2023end.html</a><p>[1]: <a href="https:&#x2F;&#x2F;github.com&#x2F;LavaMoat&#x2F;LavaMoat">https:&#x2F;&#x2F;github.com&#x2F;LavaMoat&#x2F;LavaMoat</a>
binarymax超过 1 年前
NPM forces 2fa, so I’m curious what the scenario was here. Was a committers phone compromised?
评论 #38641936 未加载
评论 #38642769 未加载
评论 #38644819 未加载
评论 #38641791 未加载
oefrha超过 1 年前
Pretty fascinating that the malicious code doesn’t seem to be obfuscated one bit. Even contains the word “drain” in multiple places. At least use innocuous looking variable names ffs.
coneonthefloor超过 1 年前
&gt; Discover what security feels like<p>Quote from their sales site.
评论 #38642983 未加载
评论 #38645390 未加载
activescott超过 1 年前
Shouldn&#x27;t this be considered an incident at <a href="https:&#x2F;&#x2F;status.ledger.com&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;status.ledger.com&#x2F;</a> ??
cantSpellSober超过 1 年前
&gt; Yes, .5&#x2F;.6&#x2F;.7 versions are compromised<p>So was there a threat to Ledger users? Elsewhere it&#x27;s said:<p>&gt; production build failed
评论 #38642530 未加载
asylteltine超过 1 年前
When will npm finally take security seriously? How many incidents do they need? Don’t allow non hardware mfa and add verified namespaces already!
评论 #38643383 未加载
评论 #38645470 未加载
neom超过 1 年前
I thought the whole point of ledger was that it&#x27;s a physical wallet that can&#x27;t easily be compromised. Not your keys not your crypto and all that?
评论 #38643561 未加载
jbirer超过 1 年前
I only have a Ledger because my required me in order to implement a crypto wallet on the website. I have 2 seed phrases written on the back of a book since 2017 and it has kept me well, no hacks so far.
评论 #38646495 未加载
wslh超过 1 年前
I have round up more information on this issue and the context here [1].<p>[1] <a href="https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=38646314">https:&#x2F;&#x2F;news.ycombinator.com&#x2F;item?id=38646314</a>
kossTKR超过 1 年前
Ledger has been hacked so many times now i&#x27;ve lost count.<p>I remember buying one in 2019, and shortly thereafter all customer data was dumped on the internet endangering everyone who bought one.<p>Then after deep diving the tech i threw it in the trash, it seemed like security theatre product.<p>There&#x27;s also been so many phishing attempts, fake ledgers sold, bricked ones losing funds, it&#x27;s total shitshow that ecosystem if you check their subreddit going back in time.<p>The more you rely on 3. parties, and the more obfuscated your setup is, the more unsafe your data is. I just use isolated cheap laptops and encrypted usb&#x27;s now.
评论 #38642496 未加载
评论 #38642328 未加载
评论 #38686604 未加载
评论 #38645533 未加载
评论 #38642262 未加载
评论 #38642275 未加载
评论 #38643240 未加载
评论 #38642171 未加载
NoGravitas超过 1 年前
LOL, I initially thought this was Ledger, the command-line personal finance management software, and was worried that it was actually something important.
评论 #38647036 未加载
评论 #38643822 未加载
tamimio超过 1 年前
&gt;minimal drain value<p>I actually laughed! Anyway, this is the list of affected software<p>github.com&#x2F;wevm&#x2F;wagmi github.com&#x2F;wevm&#x2F;wagmi github.com&#x2F;family&#x2F;connectkit github.com&#x2F;scaffold-eth&#x2F;scaffold-eth-2 github.com&#x2F;RevokeCash&#x2F;revoke.cash github.com&#x2F;blocknative&#x2F;web3-onboard github.com&#x2F;blocknative&#x2F;web3-onboard github.com&#x2F;liquity&#x2F;dev github.com&#x2F;matter-labs&#x2F;zksync-wallet-vue github.com&#x2F;bankisan&#x2F;zkShield github.com&#x2F;zkemail&#x2F;zk-email-verify github.com&#x2F;iron-wallet&#x2F;iron github.com&#x2F;gmx-io&#x2F;gmx-interface github.com&#x2F;blocknative&#x2F;web3-onboard github.com&#x2F;reservoirprotocol&#x2F;reservoir-kit github.com&#x2F;daimo-eth&#x2F;daimo github.com&#x2F;AztecProtocol&#x2F;aztec-packages github.com&#x2F;lifinance&#x2F;widget github.com&#x2F;matter-labs&#x2F;zksync-dapp-checkout github.com&#x2F;gnosis&#x2F;zodiac-modifier-roles github.com&#x2F;scaffold-eth&#x2F;Scaffold-ETH-DeFi-Challenges github.com&#x2F;cowprotocol&#x2F;cowswap github.com&#x2F;cowprotocol&#x2F;cowswap github.com&#x2F;cowprotocol&#x2F;cowswap github.com&#x2F;canvasxyz&#x2F;canvas github.com&#x2F;lifinance&#x2F;widget github.com&#x2F;parity-asia&#x2F;hackathon-2023-summer github.com&#x2F;ubiquity&#x2F;ubiquity-dollar github.com&#x2F;TalismanSociety&#x2F;talisman-web github.com&#x2F;BanklessDAO&#x2F;bankless-website github.com&#x2F;lifinance&#x2F;widget github.com&#x2F;TalismanSociety&#x2F;talisman github.com&#x2F;zkemail&#x2F;proof-of-twitter github.com&#x2F;Ifechukwudaniel&#x2F;Oracles github.com&#x2F;Ifechukwudaniel&#x2F;Oracles github.com&#x2F;noir-lang&#x2F;noir-examples github.com&#x2F;voteagora&#x2F;agora github.com&#x2F;coinbase&#x2F;build-onchain-apps github.com&#x2F;Midas-Protocol&#x2F;monorepo github.com&#x2F;austintgriffith&#x2F;stupid-staking github.com&#x2F;MetaMask&#x2F;metamask-sdk github.com&#x2F;threshold-network&#x2F;token-dashboard github.com&#x2F;threshold-network&#x2F;token-dashboard github.com&#x2F;privacy-scaling-explorations&#x2F;bandada github.com&#x2F;lidofinance&#x2F;lido-ethereum-sdk github.com&#x2F;haqq-network&#x2F;frontend github.com&#x2F;reservoirprotocol&#x2F;seaport-oracle github.com&#x2F;ameensol&#x2F;pools-ui github.com&#x2F;Web3Auth&#x2F;web3auth-wagmi-connector github.com&#x2F;Orbiter-Finance&#x2F;zkprover-dapp github.com&#x2F;xmtp&#x2F;xmtp-web github.com&#x2F;etherspot&#x2F;etherspot-react-transaction-buidler-demo-dapp github.com&#x2F;base-org&#x2F;web github.com&#x2F;unlock-protocol&#x2F;examples github.com&#x2F;saRvaGnyA&#x2F;decertify github.com&#x2F;scaffold-eth&#x2F;OP-RetroPGF3-Discovery-Voting github.com&#x2F;lukso-network&#x2F;universalprofile-test-dapp github.com&#x2F;ScopeLift&#x2F;token-shielder github.com&#x2F;givepraise&#x2F;praise github.com&#x2F;0xRusso&#x2F;fr3ela github.com&#x2F;BreadchainCoop&#x2F;breadchain-crowdstaking github.com&#x2F;unstoppabledomains&#x2F;uauth github.com&#x2F;unstoppabledomains&#x2F;uauth github.com&#x2F;hyperlane-xyz&#x2F;hyperlane-warp-ui-template github.com&#x2F;mento-protocol&#x2F;mento-web github.com&#x2F;harendra-shakya&#x2F;blockchain-lottery github.com&#x2F;harendra-shakya&#x2F;blockchain-lottery github.com&#x2F;harendra-shakya&#x2F;blockchain-lottery github.com&#x2F;harendra-shakya&#x2F;blockchain-lottery github.com&#x2F;Koniverse&#x2F;SubConnect github.com&#x2F;saqlain1020&#x2F;dapp-react-typescript-boiler github.com&#x2F;carletex&#x2F;notion-eip712 github.com&#x2F;BuidlGuidl&#x2F;event-wallet github.com&#x2F;scobru&#x2F;nimbus2000-ui github.com&#x2F;scobru&#x2F;nimbus2000-ui github.com&#x2F;yieldprotocol&#x2F;cacti-frontend github.com&#x2F;BuidlGuidl&#x2F;hacker-houses-streams github.com&#x2F;jaxernst&#x2F;scp github.com&#x2F;bee-io&#x2F;web3-connect github.com&#x2F;bee-io&#x2F;web3-connect github.com&#x2F;bee-io&#x2F;web3-connect github.com&#x2F;moodysalem&#x2F;eth-batch-deposit github.com&#x2F;AztecProtocol&#x2F;zk-money github.com&#x2F;BuidlGuidl&#x2F;zupass-scaffold-eth-2 github.com&#x2F;LedgerHQ&#x2F;connect-kit github.com&#x2F;LedgerHQ&#x2F;connect-kit github.com&#x2F;LedgerHQ&#x2F;connect-kit github.com&#x2F;LedgerHQ&#x2F;connect-kit github.com&#x2F;LedgerHQ&#x2F;connect-kit github.com&#x2F;LedgerHQ&#x2F;connect-kit github.com&#x2F;LedgerHQ&#x2F;connect-kit github.com&#x2F;LedgerHQ&#x2F;connect-kit github.com&#x2F;LedgerHQ&#x2F;connect-kit github.com&#x2F;elmol&#x2F;zk-proof-of-humanity github.com&#x2F;swing-xyz&#x2F;examples github.com&#x2F;ahmetson&#x2F;nft-bridge github.com&#x2F;RogerPodacter&#x2F;gas-lovers-nft github.com&#x2F;kmjones1979&#x2F;scaffold-eth-2-solidity github.com&#x2F;irfanbozkurt&#x2F;flashbot-recovery-bundler github.com&#x2F;amy-jung&#x2F;collectivedaoarchives.catalog github.com&#x2F;ERC-3643&#x2F;ERC-3643-DApp github.com&#x2F;austintgriffith&#x2F;impersonator-vision github.com&#x2F;scaffold-eth&#x2F;SablierV2_starterKit github.com&#x2F;gnosis&#x2F;mech npm&#x2F;web3-onboard&#x2F;ledger npm&#x2F;web3-onboard&#x2F;ledger npm&#x2F;web3-onboard&#x2F;ledger github.com&#x2F;succinctlabs&#x2F;telepathy-messenger-demo github.com&#x2F;Votes-Project&#x2F;votes-web github.com&#x2F;wevm&#x2F;wagmi github.com&#x2F;cowprotocol&#x2F;cowswap
ramijames超过 1 年前
Yikes.
rdl超过 1 年前
LOL <a href="https:&#x2F;&#x2F;twitter.com&#x2F;Ledger&#x2F;status&#x2F;1735326240658100414" rel="nofollow noreferrer">https:&#x2F;&#x2F;twitter.com&#x2F;Ledger&#x2F;status&#x2F;1735326240658100414</a><p>FINAL TIMELINE AND UPDATE TO CUSTOMERS:<p>4:49pm CET:<p>Ledger Connect Kit genuine version 1.1.8 is being propagated now automatically. We recommend waiting 24 hours until using the Ledger Connect Kit again.<p>The investigation continues, here is the timeline of what we know about the exploit at this moment:<p>- This morning CET, a former Ledger Employee fell victim to a phishing attack that gained access to their NPMJS account. - The attacker published a malicious version of the Ledger Connect Kit (affecting versions 1.1.5, 1.1.6, and 1.1.7). The malicious code used a rogue WalletConnect project to reroute funds to a hacker wallet. - Ledger’s technology and security teams were alerted and a fix was deployed within 40 minutes of Ledger becoming aware. The malicious file was live for around 5 hours, however we believe the window where funds were drained was limited to a period of less than two hours. - Ledger coordinated with @WalletConnect who quickly disabled the the rogue project. - The genuine and verified Ledger Connect Kit version 1.1.8 is now propagating and is safe to use. - For builders who are developing and interacting with the Ledger Connect Kit code: connect-kit development team on the NPM project are now read-only and can’t directly push the NPM package for safety reasons. - We have internally rotated the secrets to publish on Ledger’s GitHub. - Developers, please check again that you’re using the latest version, 1.1.8. - Ledger, along with @Walletconnect and our partners, have reported the bad actor’s wallet address. The address is now visible on @chainalysis . @Tether_to has frozen the bad actor’s USDT. - We remind you to always Clear Sign with your Ledger. What you see on the Ledger screen is what you actually sign. If you still need to blind sign, use an additional Ledger mint wallet or parse your transaction manually. - We are actively talking with customers whose funds might have been affected, and working proactively to help those individuals at this time. - We are filing a complaint and working with law enforcement on the investigation to find the attacker. - We’re studying the exploit in order to avoid further attacks. We believe the attacker’s address where the funds were drained is here: 0x658729879fca881d9526480b82ae00efc54b5c2d<p>Thank you to @WalletConnect , @Tether_io, @Chainalysis , @zachxbt , and the whole community that helped us and continue to help us identify and solve this attack.<p>Security will always prevail with the help of the whole ecosystem.
评论 #38642861 未加载
评论 #38642872 未加载
评论 #38642880 未加载
评论 #38643548 未加载
评论 #38644934 未加载
评论 #38645215 未加载
ashishbijlani超过 1 年前
Plug: we&#x27;ve been building Packj [1] to detect malicious Python&#x2F;NPM&#x2F;Ruby&#x2F;Rust&#x2F;Java&#x2F;PHP packages. It carries out static&#x2F;dynamic&#x2F;metadata analysis to look for &quot;suspicious” attributes such as spawning of shell, invalid&#x2F;expired email (i.e., no 2FA), use of files, network communication, use of decode+eval, mismatch of GitHub code vs packaged code, and several more.<p>1. <a href="https:&#x2F;&#x2F;github.com&#x2F;ossillate-inc&#x2F;packj">https:&#x2F;&#x2F;github.com&#x2F;ossillate-inc&#x2F;packj</a>
评论 #38642369 未加载
评论 #38642411 未加载
评论 #38645222 未加载
louislang超过 1 年前
Co-founder @ Phylum here (<a href="https:&#x2F;&#x2F;phylum.io" rel="nofollow noreferrer">https:&#x2F;&#x2F;phylum.io</a>). We&#x27;ve been actively scanning dependencies across most open source package registries (e.g., npm, PyPI, Crates.io, etc.) for a few years now. Quite successfully, I might add, with recent findings targeting financial institutions [1], North Korean state actors [2], and some of the first malware staging to be seen on Crates.io [3].<p>The fact that an attacker was able to pull this off against a _secure_ hardware device is shocking but not surprising. The mechanism by which they did it is interesting and fairly insidious. Unlike a lot of other attacks that will publish the malware to the registry, this one pulls the payload from a CDN. So, static analysis of the loader (i.e., the intermediary package on npm) is unlikely to yield sufficiently interesting results. Solely focusing on the obfuscation angle is also not of particular use since quite a bit of packages are obfuscated on npm (like, a surprising amount of it. In Q3 2023 we saw over 5,000 _new_ packages shipped with some form of obfuscation).<p>Nonetheless, our automated platform pinged us this morning about some changes to this package and our research team has been digging into it to determine the impacts.<p>With that said, we&#x27;ve produced (and open sourced!) several tools that aim to help with software supply chain style attacks:<p>1. Birdcage is a cross-platform embeddable sandbox [4]<p>2. Our CLI is extensible and integrates Birdcage so you can do things like `phylum npm install...` or `phylum pip install...` and have the package installations be sandboxed [5]<p>We&#x27;ve also got a variety of integrations [6] along with a threat feed of software supply chain attacks (of which the Ledger package and other APT attacks have appeared).<p>Happy to answer any questions! A collective of us are active in Discord (<a href="https:&#x2F;&#x2F;discord.gg&#x2F;Fe6pr5eW6p" rel="nofollow noreferrer">https:&#x2F;&#x2F;discord.gg&#x2F;Fe6pr5eW6p</a>), continuing to hunt attacks like these. If that&#x27;s something that interests you, we&#x27;d love to have you!<p>1. <a href="https:&#x2F;&#x2F;blog.phylum.io&#x2F;encrypted-npm-packages-found-targeting-major-financial-institution&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;blog.phylum.io&#x2F;encrypted-npm-packages-found-targetin...</a><p>2. <a href="https:&#x2F;&#x2F;blog.phylum.io&#x2F;junes-sophisticated-npm-attack-attributed-to-north-korea&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;blog.phylum.io&#x2F;junes-sophisticated-npm-attack-attrib...</a><p>3. <a href="https:&#x2F;&#x2F;blog.phylum.io&#x2F;rust-malware-staged-on-crates-io&#x2F;" rel="nofollow noreferrer">https:&#x2F;&#x2F;blog.phylum.io&#x2F;rust-malware-staged-on-crates-io&#x2F;</a><p>4. <a href="https:&#x2F;&#x2F;github.com&#x2F;phylum-dev&#x2F;birdcage">https:&#x2F;&#x2F;github.com&#x2F;phylum-dev&#x2F;birdcage</a><p>5. <a href="https:&#x2F;&#x2F;github.com&#x2F;phylum-dev&#x2F;cli">https:&#x2F;&#x2F;github.com&#x2F;phylum-dev&#x2F;cli</a><p>6. <a href="https:&#x2F;&#x2F;docs.phylum.io&#x2F;docs&#x2F;integrations_overview" rel="nofollow noreferrer">https:&#x2F;&#x2F;docs.phylum.io&#x2F;docs&#x2F;integrations_overview</a>