Malicious Ethersphere bee-js 13.3.0 and Swarm Desktop 0.56.2 releases deliver wallet-stealing malware
TLDR
- bee-js 13.3.0 and Swarm Desktop 0.56.2 downloaded code built to steal Swarm wallet keys and install a backdoor.1
- bee-js 13.3.0 was live on npm for about 75 minutes; Swarm Desktop 0.56.2 was withdrawn about 8.5 hours after appearing.14
- Treat machines that installed bee-js 13.3.0 as fully compromised and rotate secrets from another computer, GitHub's advisory says.6
The Hacker News reports that attackers used the Ethersphere project's own release automation to publish malicious versions of two tools for the Swarm decentralised storage network: bee-js 13.3.0 and Swarm Desktop 0.56.2.1 Both download and run code built to steal the wallet key that Swarm Desktop keeps for its node, along with the stored password that unlocks it, and to install a backdoor on Windows, macOS and Linux.1 StepSecurity says bee-js 13.3.0 was published to npm at 00:09:50 UTC on 9 November 2026, and it opened GitHub issue #1294 to notify the maintainers at 00:53:54 UTC.27 The Hacker News reports that the package was npm's latest bee-js version from 00:09 to 01:25 UTC, and that Swarm Desktop 0.56.2 appeared on GitHub at about 00:36 UTC and was withdrawn about 8.5 hours later.1 The maintainers replaced it with version 0.56.3, published on GitHub at 12:52 UTC on 9 November with the note "replace compromised 0.56.2 release".8
Both releases came from bee-worker, the account Ethersphere uses to automate releases, and neither change was signed or submitted as a pull request, The Hacker News reports.1 StepSecurity says the bee-js change was an unsigned direct commit under the bee-worker identity at 23:59:54 UTC on 8 November, followed by a GitHub release at 00:06:01 UTC that triggered the repository's existing npm publishing workflow.2 Because that workflow built the package, it carries valid provenance, the record linking an npm package to the repository and workflow that built it, which The Hacker News says shows where a package was built, not whether anyone reviewed the code inside it.12 For Swarm Desktop, the attackers manually started a build workflow that held the project's Apple and Windows signing certificates and needed no approval, and the macOS app was signed and notarised, The Hacker News reports.1 OX Security points to a suspected compromised developer access key, and a maintainer wrote that 0.56.2 "was published by an attacker using stolen CI credentials".15 StepSecurity and SafeDep point to misuse of the bee-worker identity, and SafeDep says this indicates a compromised bot account or token rather than a stolen npm token.23 Socket says two GitHub accounts were compromised, a long-time maintainer's and bee-worker, and that it could not explain how either was taken; it also reports failed attempts on 6 November to dump secrets from Ethersphere's CI, which it assesses with moderate confidence exfiltrated nothing.4
The loader is a few lines of code that fetch more code from api.frameworkmetrics[.]xyz and run it with the user's permissions; in bee-js it is a postinstall script, so a project did not need to import the library for it to run, while in Swarm Desktop it runs each time the app starts.13 SafeDep and StepSecurity say the downloaded code looks for two files in Swarm Desktop's data folder, config.yaml and data-dir/keys/swarm.key, and sends them to the attackers' server.23 The key file is an encrypted Ethereum keystore, but SafeDep says Swarm Desktop keeps its password in plain text in config.yaml, so with both files the attacker can take the node wallet's xDAI and xBZZ tokens, its chequebook funds and its stake.3 On Linux and macOS the backdoor is a Go remote shell called evjawbreaker, kept in a hidden ~/.solidity folder, and on Windows it is a ConnectWise ScreenConnect client that connects to the attackers' relay, SafeDep reports.3 StepSecurity says it did not retrieve the macOS executable or the Windows installer, and did not run the Linux executables, so their full capabilities are unverified.2 Socket and The Hacker News link the payloads to an Ethereum contract used in the earlier SleepyDuck and EtherDuck campaign involving Open VSX extensions, and Socket says the same group is behind these releases.14
The scale of exposure is unclear. The Hacker News says no reports gave a count of infected machines and that no theft of funds had been reported at the time of writing; StepSecurity likewise says its report does not establish how many wallets were exposed or whether funds were stolen.12 The Hacker News cites a rough estimate of about 10 downloads of bee-js 13.3.0, including by security scanners and mirrors, and a Swarm Desktop 0.56.2 count of 65 by 08:27 UTC, including researchers, while OX Security reports 44 downloads of the Swarm Desktop release and over 16,800 monthly downloads across the affected package and its dependents.15 Ethersphere's own swarm-cli and bee-dashboard packages accepted version ranges that included 13.3.0, so a fresh install in that period could have pulled it in.12 The GitHub advisory lists 13.3.0 as the affected version with no patched version, and says any computer with the package installed or running should be considered fully compromised, with all secrets rotated from a different computer, because removing the package may not remove the malware.6 The Hacker News advises pinning bee-js 13.2.0, installing Swarm Desktop 0.56.3, and, if 0.56.2 ever ran, moving the node's funds, chequebook and stake to a new key from a clean computer; it adds that updating or removing the app does not remove the backdoor, so affected machines should be rebuilt from a trusted image where possible.1
Why it matters: the malicious bee-js package carried valid provenance, which The Hacker News says shows where a package was built, not whether the code inside it was reviewed.12
Sources
- Hackers Compromise Ethersphere's bee-js and Swarm Desktop to Deliver Wallet-Stealing Malware (The Hacker News)
- @ethersphere/bee-js 13.3.0 Compromised (StepSecurity)
- Compromised bee-js and Swarm Desktop Steal Swarm Wallet Keys (SafeDep)
- Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor (Socket)
- Ethersphere Hijacked With Crypto Stealing Malware Via Github & npm (OX Security)
- Malware in @ethersphere/bee-js (GitHub Advisory Database)
- ethersphere/bee-js npm package version 13.3.0 is compromised (GitHub (ethersphere/bee-js))
- v0.56.3 (GitHub (ethersphere/swarm-desktop))