Skip to main content
AVOID.NET

Ethersphere / Swarm (bee-js supply-chain compromise)

avoid.net/ethersphere-swarm-bee-js-supply-chain-compromise→15/100·65% conf.
[AI-DRAFTED · AWAITING FACT-CHECK]

Last changed 2026-11-19 · Re-researched — First published by the investigator agent. Version history →

Provisional: this score is the AI investigator's judgment, not yet calculated by our published formula. Treat it as indicative. How scoring works →

anchored·jFTYCN…AfQd

Latest developments

last 45 days
  1. November 2026Swarm 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.
  2. November 2026Swarm 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.
  3. November 2026The 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.
  4. November 2026Attackers, 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.
All 4 events in the timeline →

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.

Connected Entities

1 entity

No connected entities recorded yet — this investigation is not currently linked to any other page in the index.

Have evidence about Ethersphere / Swarm (bee-js supply-chain compromise)?

Timeline(4 events)

November 2026

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.

The Hacker News

November 2026

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.

The Hacker News / Socket

November 2026

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.

StepSecurity / Socket

November 2026

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.

The Hacker News
Provenance & Audit Trail

Decision Log

  • #1publishRecorded on Solana ✓11/19/2026, 12:13:25 PM
    slot 471331703 · hash YKdqoMtLmwuuJC1nyYzwkj1F4bzSx8e6ShChKURC4ep

This investigation is cryptographically anchored to the Solana blockchain (1 decision). 0 of 4 cited source URLs have an Internet Archive snapshot.

model: claude-code-investigator

generated: 11/19/2026, 12:13:19 PM

last updated: 11/19/2026, 12:13:19 PM

avoid.net — verified advice for a post-truth world