<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
  <title>pwn.watch: Crypto incident updates</title>
  <link>https://pwn.watch/t/crypto</link>
  <description>Live security incidents worldwide: CVEs, patch status, fixed versions, advisories and the posts that broke them.</description>
  <language>en</language>
  <lastBuildDate>Fri, 31 Oct 2025 00:00:00 GMT</lastBuildDate>
  <atom:link href="https://pwn.watch/t/crypto/feed.xml" rel="self" type="application/rss+xml" />
  <item>
    <title>[high] GlassWorm: self-spreading VS Code / OpenVSX extension worm hidden in invisible Unicode</title>
    <link>https://pwn.watch/i/glassworm-vscode-openvsx-worm-october-2025</link>
    <guid isPermaLink="true">https://pwn.watch/i/glassworm-vscode-openvsx-worm-october-2025</guid>
    <pubDate>Fri, 31 Oct 2025 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;Koi Security found extensions on OpenVSX (and one on Microsoft's marketplace) carrying JavaScript hidden in invisible Unicode variation selectors. The malware stole npm, GitHub, Git and OpenVSX credentials to infect more extensions, went after crypto wallets, and set up SOCKS proxies and hidden VNC.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; Malicious releases removed from the marketplaces&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2025-10-20: Wider coverage; Microsoft marketplace extension also affected (&lt;a href=&quot;https://www.bleepingcomputer.com/news/security/self-spreading-glassworm-malware-hits-openvsx-vs-code-registries/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-10-17: Koi Security discloses GlassWorm on OpenVSX (&lt;a href=&quot;https://www.koi.ai/blog/glassworm-first-self-propagating-worm-using-invisible-code-hits-openvsx-marketplace&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
  <item>
    <title>[critical] chalk, debug and 16 other npm packages (2B+ weekly downloads) hijacked via fake 2FA email</title>
    <link>https://pwn.watch/i/chalk-debug-npm-hijack-september-2025</link>
    <guid isPermaLink="true">https://pwn.watch/i/chalk-debug-npm-hijack-september-2025</guid>
    <pubDate>Mon, 15 Sep 2025 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>&lt;p&gt;Maintainer Josh Junon (qix) was phished by a fake npm 2FA-reset email from npmjs.help. The attacker published malicious versions of 18 packages, including chalk, debug, ansi-styles and strip-ansi, with code that hijacked crypto wallet transactions in browsers. They were live for about two hours.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; chalk 5.6.2, ansi-styles 6.2.3, strip-ansi 7.1.2, supports-color 10.2.2, ansi-regex 6.2.2, wrap-ansi 9.0.2, slice-ansi 7.1.2, has-ansi 6.0.2, chalk-template 1.1.2, supports-hyperlinks 4.1.2, debug and others: republished by the maintainer on 2025-09-13&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2025-09-15: Initial CVEs posted (&lt;a href=&quot;https://github.com/debug-js/debug/issues/1005&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-09-13: All remaining affected packages republished by the maintainer (&lt;a href=&quot;https://github.com/debug-js/debug/issues/1005&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-09-08: Malicious versions start appearing on npm (13:16 UTC) (&lt;a href=&quot;https://www.aikido.dev/blog/npm-debug-and-chalk-packages-compromised&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
  <item>
    <title>[high] Coinbase: bribed support contractors leak data of 69,461 customers, $20M ransom refused</title>
    <link>https://pwn.watch/i/coinbase-bribed-support-agents-breach-may-2025</link>
    <guid isPermaLink="true">https://pwn.watch/i/coinbase-bribed-support-agents-breach-may-2025</guid>
    <pubDate>Fri, 30 May 2025 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;Criminals bribed overseas support staff to pull customer data (names, contact details, partial financial data, ID images, balances and transactions), then demanded $20M. Coinbase refused, offered a matching bounty, and estimated $180M to $400M in costs. No passwords, private keys or funds were accessed directly.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; no-fix-needed&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2025-05-15: Coinbase discloses the breach in an SEC filing and refuses the $20M ransom (&lt;a href=&quot;https://www.sec.gov/Archives/edgar/data/1679788/000167978825000094/coin-20250514.htm&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-05-11: Coinbase receives the extortion demand and discovers the breach (&lt;a href=&quot;https://www.bleepingcomputer.com/news/security/coinbase-says-recent-data-breach-impacts-69-461-customers/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-05: Breach notice puts affected customers at 69,461 (&lt;a href=&quot;https://www.bleepingcomputer.com/news/security/coinbase-says-recent-data-breach-impacts-69-461-customers/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
  <item>
    <title>[critical] Bybit loses ~$1.5B in ETH after Safe{Wallet} frontend is trojanized (North Korea)</title>
    <link>https://pwn.watch/i/bybit-1-5b-hack-safe-wallet-february-2025</link>
    <guid isPermaLink="true">https://pwn.watch/i/bybit-1-5b-hack-safe-wallet-february-2025</guid>
    <pubDate>Thu, 06 Mar 2025 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>&lt;p&gt;North Korean TraderTraitor/Lazarus hackers compromised a Safe{Wallet} developer's Mac, took over AWS session tokens and injected JavaScript into Safe's S3-hosted frontend. Bybit's signers approved what looked like a routine transfer but was a malicious transaction. It is the largest crypto theft on record; the FBI attributed it to North Korea.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; no-fix-needed&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2025-03-06: Safe{Wallet} confirms a developer machine compromise by TraderTraitor (&lt;a href=&quot;https://thehackernews.com/2025/03/safewallet-confirms-north-korean.html&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-02-26: FBI attributes the theft to North Korea ('TraderTraitor') (&lt;a href=&quot;https://www.ic3.gov/psa/2025/psa250226&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2025-02-21: About $1.5B in ETH drained from a Bybit cold wallet&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
  <item>
    <title>[high] @solana/web3.js npm package backdoored to steal private keys</title>
    <link>https://pwn.watch/i/solana-web3-js-npm-compromise-cve-2024-54134</link>
    <guid isPermaLink="true">https://pwn.watch/i/solana-web3-js-npm-compromise-cve-2024-54134</guid>
    <pubDate>Wed, 04 Dec 2024 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;A publish-access account for @solana/web3.js was compromised. Malicious versions 1.95.6 and 1.95.7, live on npm from 15:20 to 20:25 UTC on 2024-12-03, exfiltrated private key material from apps and bots that handle keys directly. Non-custodial wallets were generally not affected. Fixed in 1.95.8.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; 1.95.8&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2024-12-04: GitHub advisory GHSA-jcxm-7wvp-g6p5 published; upgrade to 1.95.8 (&lt;a href=&quot;https://github.com/solana-labs/solana-web3.js/security/advisories/GHSA-jcxm-7wvp-g6p5&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2024-12-03: Malicious 1.95.6 and 1.95.7 published to npm (15:20-20:25 UTC), then unpublished (&lt;a href=&quot;https://github.com/solana-labs/solana-web3.js/security/advisories/GHSA-jcxm-7wvp-g6p5&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;CVEs:&lt;/strong&gt; CVE-2024-54134&lt;/p&gt;</description>
  </item>
  <item>
    <title>[high] @lottiefiles/lottie-player npm package hijacked with a crypto wallet drainer</title>
    <link>https://pwn.watch/i/lottiefiles-lottie-player-npm-compromise</link>
    <guid isPermaLink="true">https://pwn.watch/i/lottiefiles-lottie-player-npm-compromise</guid>
    <pubDate>Thu, 31 Oct 2024 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;A LottieFiles developer's npm access was abused to publish @lottiefiles/lottie-player 2.0.5, 2.0.6 and 2.0.7 on 2024-10-30. Sites loading the 'latest' build from CDNs like unpkg and jsDelivr showed a wallet-connect popup that tried to drain visitors' crypto wallets. LottieFiles unpublished the versions and released 2.0.8, a copy of 2.0.4.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; 2.0.8&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2024-10-30: Malicious 2.0.5, 2.0.6 and 2.0.7 pushed to npm; users report a wallet popup (&lt;a href=&quot;https://github.com/LottieFiles/lottie-player/issues/254&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2024-10-30: LottieFiles removes the compromised access, unpublishes the versions and publishes 2.0.8 (&lt;a href=&quot;https://github.com/LottieFiles/lottie-player/issues/254&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
  <item>
    <title>[critical] Ledger Connect Kit npm package hijacked to drain crypto wallets</title>
    <link>https://pwn.watch/i/ledger-connect-kit-npm-supply-chain-2023</link>
    <guid isPermaLink="true">https://pwn.watch/i/ledger-connect-kit-npm-supply-chain-2023</guid>
    <pubDate>Thu, 14 Dec 2023 00:00:00 GMT</pubDate>
    <category>critical</category>
    <description>&lt;p&gt;Attackers phished a former Ledger employee's npm account and published malicious @ledgerhq/connect-kit versions 1.1.5 to 1.1.7. Because many dApps load it from a CDN without pinning a version, their users were shown wallet-drainer prompts. Ledger shipped a clean 1.1.8 within about 40 minutes of finding out.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; patched · &lt;strong&gt;Fixed in:&lt;/strong&gt; 1.1.8&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2023-12-14: Malicious connect-kit versions published to npm via a phished ex-employee account; Ledger ships 1.1.8 and the npm versions are removed (&lt;a href=&quot;https://www.ledger.com/blog/security-incident-report&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
  <item>
    <title>[high] Retool breach: SMS phishing, deepfaked voice call and synced MFA codes</title>
    <link>https://pwn.watch/i/retool-sms-phishing-google-authenticator-sync-2023</link>
    <guid isPermaLink="true">https://pwn.watch/i/retool-sms-phishing-google-authenticator-sync-2023</guid>
    <pubDate>Wed, 13 Sep 2023 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;An attacker phished a Retool employee by SMS, then called them with a deepfaked voice to get an MFA code. Because Google Authenticator synced codes to the employee's Google account, the attacker got their MFA codes too, and took over 27 cloud customer accounts, all in crypto.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; no-fix-needed&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2023-09-13: Retool publishes its write-up (&lt;a href=&quot;https://retool.com/blog/mfa-isnt-mfa&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2023-08-27: SMS phishing and voice call lead to compromise of a Retool employee account and 27 cloud customers (&lt;a href=&quot;https://retool.com/blog/mfa-isnt-mfa&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
  <item>
    <title>[high] JumpCloud breached by North Korean hackers to reach crypto customers</title>
    <link>https://pwn.watch/i/jumpcloud-nation-state-breach-2023</link>
    <guid isPermaLink="true">https://pwn.watch/i/jumpcloud-nation-state-breach-2023</guid>
    <pubDate>Thu, 20 Jul 2023 00:00:00 GMT</pubDate>
    <category>high</category>
    <description>&lt;p&gt;A spear-phishing attack let a nation-state actor into JumpCloud's infrastructure. The attacker abused its command framework to target a small set of customers. JumpCloud force-rotated all customer API keys, and researchers tied the attack to North Korea, aimed at crypto companies.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; closed · &lt;strong&gt;Patch:&lt;/strong&gt; no-fix-needed&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Latest updates:&lt;/strong&gt;&lt;/p&gt;&lt;ul&gt;&lt;li&gt;2023-07-20: SentinelOne links the intrusion infrastructure to North Korean APT activity (&lt;a href=&quot;https://www.sentinelone.com/labs/jumpcloud-intrusion-attacker-infrastructure-links-compromise-to-north-korean-apt-activity/&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2023-07-12: JumpCloud publishes incident details and indicators (&lt;a href=&quot;https://jumpcloud.com/blog/security-update-incident-details&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;li&gt;2023-07-05: JumpCloud rotates all customer API keys (&lt;a href=&quot;https://jumpcloud.com/blog/security-update-incident-details&quot;&gt;source&lt;/a&gt;)&lt;/li&gt;&lt;/ul&gt;</description>
  </item>
</channel>
</rss>
