{"investigation":{"slug":"ethersphere-swarm-bee-js-supply-chain-compromise","entity_name":"Ethersphere / Swarm (bee-js supply-chain compromise)","trust_score":15,"severity_base":null,"score_modifier":0,"confidence":0.65,"status":"published","content_type":"investigation","summary":"On November 9, 2026, attackers used compromised CI/CD or GitHub credentials to publish a malicious version of the @ethersphere/bee-js npm package (13.3.0) and a trojanized Swarm Desktop application (0.56.2), both designed to steal Swarm node wallet keys and deploy a backdoor. Security researchers at Socket, StepSecurity, and OX Security linked the payload to a backdoor dubbed 'SleepyDuck' with Ethereum-based command-and-control infrastructure. The malicious packages were removed within hours and no confirmed fund losses had been reported at the time of writing, but affected users were advised to rotate wallet keys.","sections":[{"content":"On November 9, 2026, a threat actor gained access to Ethersphere's own release pipeline (described by researchers as compromised CI/CD or stolen credentials, including a maintainer's npm/GitHub automation) and used it to publish two malicious artifacts: version 13.3.0 of the @ethersphere/bee-js npm package, and version 0.56.2 of the Swarm Desktop application, distributed via a GitHub release. According to The Hacker News and Socket, a file in the bee-js repository (scripts/generate-version.cjs) was rewritten into a remote-code loader and wired into the package's postinstall script, so that installing the package executed attacker-controlled code with full Node.js privileges. In Swarm Desktop, a similar loader executed each time the application started. GitHub's security advisory for the package reportedly stated that any computer with the compromised package installed or running should be considered fully compromised.","heading":"Nature of the compromise","sources":[{"url":"https://thehackernews.com/2026/11/hackers-compromise-etherspheres-bee-js.html","name":"Hackers Compromise Ethersphere's bee-js - The Hacker News","type":"news_article","credibility":2},{"url":"https://socket.dev/blog/bee-js-compromise","name":"Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor - Socket","type":"research","credibility":2},{"url":"https://www.stepsecurity.io/blog/ethersphere-bee-js-13-3-0-compromise","name":"Ethersphere bee-js 13.3.0 compromise - StepSecurity","type":"research","credibility":2}],"severity":"critical"},{"content":"Researchers reported that the malicious code searched for Swarm node keystore files (including a configuration file and a file referred to as data-dir/keys/swarm.key, which holds an encrypted node wallet key and its unlock password) and, when found, exfiltrated them to an attacker-controlled server. The payload was also reported to install a persistent backdoor: ScreenConnect remote-access software on Windows, and a Go-based backdoor on macOS and Linux. Socket and OX Security attributed the backdoor to a group previously linked to a malicious browser extension and C2 infrastructure dubbed 'SleepyDuck,' which researchers said used an Ethereum smart contract to store or rotate command-and-control server addresses, making takedown harder than with conventional domains. Allegedly, the attackers updated the backdoor's control-server address roughly 29 minutes before the malicious bee-js code was committed, which researchers cited as evidence of pre-planning.","heading":"Payload and wallet-theft mechanism","sources":[{"url":"https://socket.dev/blog/bee-js-compromise","name":"Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor - Socket","type":"research","credibility":2},{"url":"https://www.ox.security/blog/ethersphere-hijacked-with-crypto-stealing-malware-via-github-npm/","name":"Ethersphere hijacked with crypto-stealing malware via GitHub/npm - OX Security","type":"research","credibility":2},{"url":"https://thehackernews.com/2026/11/hackers-compromise-etherspheres-bee-js.html","name":"Hackers Compromise Ethersphere's bee-js - The Hacker News","type":"news_article","credibility":2}],"severity":"critical"},{"content":"According to The Hacker News and Socket, @ethersphere/bee-js 13.3.0 was published to npm and was listed as the package's latest version for approximately 75 minutes (roughly 00:09 to 01:25 UTC) before removal, during which it is estimated to have been downloaded around 10 times — a figure researchers described as a rough estimate, since npm download counts for brand-new or removed versions are not precise. Swarm Desktop 0.56.2 remained available via GitHub for longer, with reports ranging from roughly 8.5 hours to longer; one report put its download count at 65 by 08:27 UTC. Because bee-js is a dependency of other Ethersphere packages that use caret version ranges (such as @ethersphere/swarm-cli and @ethersphere/bee-dashboard, per Socket's report), projects that did not directly reference 13.3.0 could still have pulled it transitively during the exposure window. As of the sources reviewed, no confirmed theft of funds (xDAI, xBZZ tokens, chequebook balances, or staked tokens) had been publicly reported, though researchers noted the stolen data could in principle have enabled such theft.","heading":"Exposure window and scale","sources":[{"url":"https://thehackernews.com/2026/11/hackers-compromise-etherspheres-bee-js.html","name":"Hackers Compromise Ethersphere's bee-js - The Hacker News","type":"news_article","credibility":2},{"url":"https://socket.dev/blog/bee-js-compromise","name":"Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor - Socket","type":"research","credibility":2}],"severity":"high"},{"content":"Following removal of the malicious releases, npm's registry reverted to @ethersphere/bee-js 13.2.0 as the latest version, and Swarm Desktop 0.56.3 was published as a clean replacement; The Hacker News reported that 0.56.3's code matched the previously clean 0.56.1 release and was re-signed with a new Developer ID certificate. Researchers and the project advised that removing the compromised package or application does not by itself remediate a machine that already ran the malicious code: any backdoor already installed would persist, and any key or password already exfiltrated would remain compromised. Affected users were advised to treat machines that had run the malicious versions as fully compromised, rotate any exposed Swarm node wallet keys, and check logs (one guide pointed to a line reading 'Bee Desktop version: 0.56.2 (production)' in the application's log file) to determine whether the compromised version had run.","heading":"Remediation and clean versions","sources":[{"url":"https://thehackernews.com/2026/11/hackers-compromise-etherspheres-bee-js.html","name":"Hackers Compromise Ethersphere's bee-js - The Hacker News","type":"news_article","credibility":2},{"url":"https://www.stepsecurity.io/blog/ethersphere-bee-js-13-3-0-compromise","name":"Ethersphere bee-js 13.3.0 compromise - StepSecurity","type":"research","credibility":2}],"severity":"high"}],"timeline":[{"date":"2026-11","event":"Attackers, using compromised release-pipeline access, publish a trojanized Swarm Desktop 0.56.2 GitHub release and, roughly 73 seconds after a related malicious GitHub release, publish @ethersphere/bee-js 13.3.0 to npm with a postinstall script that fetches and executes remote code.","source":"The Hacker News","source_url":"https://thehackernews.com/2026/11/hackers-compromise-etherspheres-bee-js.html","date_original":"2026-11-09"},{"date":"2026-11","event":"The malicious @ethersphere/bee-js 13.3.0 is removed from npm as the package's latest version after being live for approximately 75 minutes; the registry reverts to 13.2.0.","source":"The Hacker News / Socket","source_url":"https://socket.dev/blog/bee-js-compromise","date_original":"2026-11-09"},{"date":"2026-11","event":"Swarm Desktop 0.56.2 is withdrawn from GitHub after remaining available for several hours (reports vary between approximately 8.5 hours and longer), reaching an estimated 65 downloads.","source":"StepSecurity / Socket","source_url":"https://www.stepsecurity.io/blog/ethersphere-bee-js-13-3-0-compromise","date_original":"2026-11-09"},{"date":"2026-11","event":"Swarm Desktop 0.56.3 is published as a clean replacement release, reported to match the code of the earlier clean 0.56.1 version, re-signed with a new certificate.","source":"The Hacker News","source_url":"https://thehackernews.com/2026/11/hackers-compromise-etherspheres-bee-js.html","date_original":"2026-11-09"}],"sources_used":[{"url":"https://thehackernews.com/2026/11/hackers-compromise-etherspheres-bee-js.html","name":"Hackers Compromise Ethersphere's bee-js - The Hacker News","type":"news_article","credibility":2},{"url":"https://socket.dev/blog/bee-js-compromise","name":"Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor - Socket","type":"research","credibility":2},{"url":"https://www.stepsecurity.io/blog/ethersphere-bee-js-13-3-0-compromise","name":"Ethersphere bee-js 13.3.0 compromise - StepSecurity","type":"research","credibility":2},{"url":"https://www.ox.security/blog/ethersphere-hijacked-with-crypto-stealing-malware-via-github-npm/","name":"Ethersphere hijacked with crypto-stealing malware via GitHub/npm - OX Security","type":"research","credibility":2}],"source_tags":[],"addresses":[],"reviewed":false,"reviewed_by":null,"model_used":"claude-code-investigator","created_at":"2026-11-19T12:13:19.140169+00:00","updated_at":"2026-11-19T12:13:25.608+00:00"},"source_quality":{"total":4,"tier1":0,"tier2":0,"tier3":0,"unrated":4},"follower_count":null,"content_updated_at":"2026-11-19T12:13:19.529Z","last_fact_checked_at":null,"fact_check_next_allowed_at":null,"update_next_allowed_at":null}