cryptocurrency
6 articles with this tag
Ethersphere bee-js 13.3.0 and Swarm Desktop 0.56.2 Shipped Malware (November 2026): Affected Versions and What Users Should Do
Version 13.3.0 of the npm package @ethersphere/bee-js, from Ethersphere, the developer of the Swarm decentralized storage network, contained malicious code. A GitHub advisory (GHSA-hh7j-5m3j-23pf) published on November 9, 2026 lists 13.3.0 as the only affected version and says there is no patched version. It says any computer that has the package installed or running should be considered fully compromised, and that all secrets and keys on it should be rotated immediately from a different computer. Removing the package may not clear all malicious software the install caused. For Swarm Desktop, Ethersphere's release notes say version 0.56.3, released on November 9, replaces the compromised 0.56.2. According to a security firm's analysis, bee-js 13.3.0 appeared on npm at about 00:09 UTC on November 9 (09:09 Japan time) and was removed about 75 minutes later. Swarm Desktop 0.56.2 was public for about 8.5 hours and was also delivered by auto-update to Windows x64 and Apple Silicon. bee-js 13.2.0 and earlier, and Swarm Desktop 0.56.1, are reported as not affected. The same analysis says the Bee node's configuration file (which holds a plaintext password) and its wallet key were targeted, and that credentials used by the official release automation were abused. Our conclusion: rebuild any machine or CI environment that installed an affected version, move the wallet to a new key and move funds, and rotate credentials from a different machine.
October 2026 cyberattacks and data breaches: 36 exploited vulnerabilities and large-scale leaks
CISA added 36 vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog in October 2026, seven fewer than September's 43. Eleven were edge and remote-access products such as VPN appliances and firewalls, five were old flaws published between 2015 and 2023 (all added on October 8), ten were in Plex, PHP, Ahsay and Zammad, and ten were other products. This site published 115 first reports on incidents and vulnerabilities in October (65 Japanese incidents, 28 overseas, 4 global, 18 vulnerabilities); that is a count of this site's articles, not national statistics. In Japan, leaks from member and app databases kept coming. The largest announced figures were ShopServe (about 23.356 million people), the MUJI app (up to about 27.26 million records, possible), Club Tourism (about 4.32 million records, possible) and Hana Cupid (up to 4,238,242 records). Service-provider and SaaS breaches, crypto exchange thefts and AI developer platform incidents also continued. Our conclusion for November: patch the edge devices that reached KEV first, inventory the outside services that hold your customer lists, and prepare for phishing that pretends to be a breached company.
Binance crypto theft (about US$6.3 billion): are user funds covered, and what account holders should do
Binance said that its hot wallets were compromised at about 20:05 UTC on October 29, 2026 and that unauthorized withdrawals followed, with an estimated impact of about US$6.3 billion. On October 31, the FBI announced that North Korea was responsible for the theft of more than US$6 billion, and published 628 addresses that it says are holding or have held assets from the theft, asking exchanges and other services to block them. Binance says user funds are safe, that it will absorb the loss itself (it said on November 1 that about 95% of the impacted amount is now replenished), and that about US$3 billion was frozen on-chain. Its first update said the initial investigation suggested that a compromised DevOps engineer's laptop let an attacker reach a service container and submit unauthorized withdrawals; its second update said further investigation uncovered additional points of breach, and that no evidence of a wallet private key leak has been found. Binance's Update #4 scheduled phase one of withdrawals for 06:00 to 09:00 UTC on November 1, and Binance said in a post on X that by 12:36 UTC all 15 networks in the first phase had resumed; the remaining networks and assets are still being tested, and deposits are not affected. In Update #5 on November 2, Binance said the full zero-knowledge Proof of Reserves proof for ten tokens is complete and that the next phase of withdrawals is planned for November 3. In Update #6 on November 3, Binance said withdrawals reopen for more assets from 04:00 UTC that day, progressively as security checks finish. A post-mortem is still to come. This site's conclusion: in what has been disclosed, this was a theft from the exchange's own wallets, and Binance has not listed customer data as affected, so the main risk for account holders now is fake support, fake refund and fake recovery messages. Open Binance only from your own bookmark or official app, never share a seed phrase, private key or verification code, and turn on two-factor authentication.
Trezor reports a possible hardware implant in a Safe 5 from a former reseller (unconfirmed): what owners should do
On October 30, 2026, Trezor published a notice saying its security team received, on October 28, a responsible-disclosure report of a hardware implant in a Trezor Safe 5. The device was bought in August 2026 from a company that was an official Trezor reseller in Southeast Asia until October 2026, through an online marketplace. The report describes an extra circuit board with a cellular module and antenna between the main board and the screen, said to read what the screen shows, including the wallet backup (recovery phrase), and send it over a mobile network. Trezor has not received the device, so this is unverified, and it says no funds are known to have been stolen. For devices bought from that reseller since March 2026, Trezor says: do not set up a new one, and if you already use one, create a new wallet with a new recovery phrase on a new device and move your funds. Our conclusion: this is a report, not a confirmed finding, but the steps are cheap compared with the risk, so follow the manufacturer's guidance if your device came from that reseller.
Bitget crypto theft (about US$387.5 million): are customer balances covered, and what account holders should do
On September 24, 2026 (UTC), the crypto exchange Bitget detected unauthorized transfers from part of its hot and warm wallets. It first estimated about US$351.6 million and on September 25 confirmed about US$387.5 million sent to attacker-controlled addresses. Bitget says customer account balances were not affected, that the loss falls within its User Protection Fund, that cold wallets were not touched, and that the entry point was a zero-day vulnerability in third-party security products, now remediated. Withdrawals were paused, then restored in phases; Bitget's page says they were fully restored on October 2. Bitget has not published the name of the affected product or a full root-cause report. This site's take: this was a theft from the exchange's own wallets, not a leak of customer data, so the main risk for account holders now is fake 'recovery' and 'compensation' messages. Turn on two-factor authentication, open Bitget only from your own bookmark, and never share a seed phrase, private key or verification code.
Metabase vulnerability CVE-2026-72898: 2026 breaches and what to do
In August 2026 it emerged that an unauthenticated SQL injection in the BI (business intelligence) and analytics tool Metabase (CVE-2026-72898, CVSS 10.0) had been exploited before a fix was released. Metabase says fewer than 3% of its cloud customers and some internet-reachable self-hosted instances were compromised. Organizations that disclosed impact include Trezor, which sells cryptocurrency hardware wallets (80,689 customers' names, addresses, phone numbers and email addresses, via its logistics partner's analytics environment), laptop maker Framework, automation tool n8n, Anaconda's Kilo Code and wallet-infrastructure provider Privy. This site's take: what leaked matches what the compromised analytics tool could read at the time. Trezor customers should never type or share their wallet backup (recovery seed) and should assume their home address is known, so they should not follow instructions in letters or calls either. Operators of analytics tools should patch, and also limit the data the tool can read to the columns analysis actually needs.