Critical Alert: Malicious bee-js npm and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor
A recent supply chain attack compromised @ethersphere/bee-js npm package and Swarm Desktop, injecting the SleepyDuck Ethereum C2 backdoor. Learn about the incident, its impact, and crucial developer actions.

The digital landscape for developers was shaken on November 9, 2026, by a critical security incident involving the compromise of the popular @ethersphere/bee-js npm package and the Swarm Desktop application. A sophisticated supply chain attack led to the distribution of malicious versions embedded with the 'SleepyDuck' Ethereum Command-and-Control (C2) backdoor. This incident highlights the persistent and evolving threats targeting the software supply chain, underscoring the vital need for vigilance in open-source ecosystems and release pipelines.
The attack, analyzed by Socket's Threat Research Team, leveraged compromised maintainer accounts to push trojanized releases, posing a significant risk to developers and users of the Swarm decentralized storage network. Understanding the mechanics of this compromise, its immediate impact, and the necessary remediation steps is paramount for safeguarding development environments and deployed applications.
1. The Compromise Unveiled: How the Attack Unfolded
The security breach on November 9, 2026, originated from compromised GitHub accounts belonging to Ethersphere project maintainers. Specifically, the accounts 'nugaon', an early contributor with force-push rights, and 'bee-worker', the release automation identity, were implicated. These compromised credentials were used to inject malicious code into the project's release pipeline.
The threat actor successfully published a malicious version 13.3.0 of the @ethersphere/bee-js JavaScript client library to npm. This was achieved by rewriting the scripts/generate-version.cjs file into a remote-code loader and promoting it to a postinstall hook. Alarmingly, this malicious package was published via Ethersphere's legitimate trusted-publishing workflow, complete with valid SLSA provenance, and the loader executed three times within the publishing job itself.
Concurrently, a trojanized version 0.56.2 of Swarm Desktop was released on GitHub. All nine Linux, macOS, and Windows packages from the compromised CI run contained the same loader within the Electron main process. The macOS build even bore the project's Developer ID signature and was notarized by Apple, lending it a deceptive air of legitimacy. This allowed the malicious update to be offered to Apple Silicon and Windows x64 users via the app's auto-updater.
The Socket analysis indicated that the compromise of these GitHub accounts predated November 6, as an earlier attempt to harvest credentials on that date failed. The exact origin of the initial account compromises remains unexplained, emphasizing the stealth and persistence of the attackers.
2. Anatomy of the SleepyDuck Backdoor and its C2 Infrastructure
Both the malicious @ethersphere/bee-js 13.3.0 npm package and the trojanized Swarm Desktop 0.56.2 release carried a small loader. This loader was designed to fetch additional JavaScript from api[.]frameworkmetrics[.]xyz and execute it with full Node.js privileges. This capability allowed the attackers to achieve remote code execution on affected systems, effectively establishing a backdoor.
A critical aspect of this attack is the reuse of the 'SleepyDuck' (also known as 'EtherDuck') Ethereum-addressed Command-and-Control (C2) infrastructure. The Ethereum smart contract, located at 0xf8a900Db50b3331be6B768bA460BB59f3E40C344, served as a dead drop, providing the later stages of the malware with instructions on where to connect. This contract has been maintained by the same wallet since March 2026 and was previously utilized in malicious Solidity extensions on Open VSX, as documented by Pluto Security on October 1, 2026.
The use of an Ethereum smart contract for C2 communication offers several advantages for attackers, including resilience against traditional takedowns and a degree of anonymity. The shared infrastructure strongly links this incident to previous campaigns, indicating a persistent threat actor or group. The ability to dynamically fetch and execute further payloads makes this backdoor highly adaptable and dangerous, allowing attackers to pivot their operations based on the compromised environment.
3. Immediate Impact, Remediation, and Developer Recommendations
Upon discovery, swift actions were taken by the respective platforms. npm removed the malicious @ethersphere/bee-js 13.3.0 package approximately 75 minutes after its publication. The Swarm Desktop release, however, remained publicly available on GitHub for about eight and a half hours before Ethersphere maintainers deleted the v0.56.2 tag and made the release private.
However, deleting a release does not automatically roll back installations. Machines that had already updated to Swarm Desktop 0.56.2 will remain on that compromised version until a new, clean release (e.g., 0.56.3 or later) is published and installed. As of November 9, 2026, no such clean release had been published. This means that users who installed the malicious versions during their availability window are still at risk.
Recommendations for Developers:
- Immediate Verification: Developers using
@ethersphere/bee-jsshould verify their installed version. If 13.3.0 was installed, it must be immediately uninstalled and replaced with a known good version. - Swarm Desktop Users: If Swarm Desktop 0.56.2 was installed, users should assume compromise, disconnect from networks, and await official guidance for a clean update or reinstallation.
- Supply Chain Security: Implement and enforce robust supply chain security practices, including integrity checks, dependency scanning, and stricter access controls for release pipelines.
- Multi-Factor Authentication (MFA): Ensure MFA is enabled for all critical developer accounts, especially those with publishing or force-push rights to repositories.
- Audit Logs: Regularly review audit logs for unusual activity in GitHub repositories and CI/CD systems.
- Network Monitoring: Monitor network traffic for connections to suspicious domains like
api[.]frameworkmetrics[.]xyzor interactions with known SleepyDuck C2 Ethereum contracts. - Stay Informed: Keep abreast of security advisories from projects and security researchers.
4. Broader Implications for Software Supply Chain Security
This incident serves as a stark reminder of the persistent and evolving nature of software supply chain attacks. The fact that a malicious package could be published through a legitimate trusted-publishing workflow with valid SLSA provenance highlights the limitations of current security measures when foundational accounts are compromised.
The reliance on open-source components, while fostering innovation, also introduces significant attack vectors. A single compromised maintainer account can lead to widespread distribution of malware to thousands or millions of users. This necessitates a multi-layered security approach:
- Enhanced Account Security: Beyond MFA, consider hardware security keys and stricter access policies for critical roles.
- Automated Code Analysis: Implement advanced static and dynamic analysis tools to detect suspicious changes, especially in build scripts and post-install hooks.
- Behavioral Monitoring of CI/CD: Deploy systems that can detect anomalous behavior within CI/CD pipelines, such as unexpected modifications to release artifacts or unusual network connections during builds.
- Dependency Vetting: Tools and processes for vetting upstream dependencies, not just for known vulnerabilities but also for suspicious behavioral patterns.
- Incident Response Plans: Organizations must have clear and tested incident response plans for supply chain compromises, including rapid rollback strategies and communication protocols.
The reuse of the SleepyDuck C2 infrastructure also points to the need for better threat intelligence sharing across the industry. Understanding the tactics, techniques, and procedures (TTPs) of persistent threat actors can help in proactively defending against future attacks. As AI agents become more prevalent in the software development lifecycle, as highlighted by recent GitHub guides on AI agents across the SDLC, the attack surface could further expand, making robust security practices even more critical. The industry must collectively invest in stronger defenses to protect the integrity of the software supply chain.
Comparison Overview
| Characteristic | Legitimate Releases | Malicious Releases (bee-js 13.3.0 / Swarm Desktop 0.56.2) |
|---|---|---|
| Source of Compromise | None (assuming uncompromised state) | Compromised GitHub maintainer accounts (nugaon, bee-worker) |
| Distribution Channel | Official npm registry, GitHub releases | Official npm registry, GitHub releases (via compromised pipeline) |
| Code Integrity | Expected to be clean and verified | Contains remote-code loader, modified scripts/generate-version.cjs |
| Post-Install Hook | Standard, non-malicious operations | Rewritten to execute remote-code loader |
| C2 Infrastructure | None | Ethereum smart contract (0xf8a900Db50b3331be6B768bA460BB59f3E40C344) |
| Digital Signatures (macOS) | Project's Developer ID, Apple notarization | Project's Developer ID, Apple notarization (deceptively legitimate) |
| Detection/Removal | N/A | npm removed quickly; GitHub release up for ~8.5 hours |
| User Impact | Normal functionality | Potential remote code execution, system compromise |
Frequently Asked Questions (FAQ)
Q: How can I check if I'm affected by the malicious bee-js or Swarm Desktop release?
For @ethersphere/bee-js, check your project's package-lock.json or yarn.lock file for version 13.3.0. If found, immediately uninstall it. For Swarm Desktop, check your installed application's version. If it's 0.56.2, assume compromise. It's crucial to follow official guidance from Ethersphere for remediation.
Q: What immediate steps should I take if I'm affected?
If you have installed @ethersphere/bee-js 13.3.0 or Swarm Desktop 0.56.2, you should immediately isolate the affected systems from your network. Uninstall the compromised software. Change any credentials that might have been exposed or used on the compromised system. Monitor your network for suspicious outbound connections. Await and apply official, verified updates from Ethersphere.
Q: How can developers prevent similar supply chain attacks in the future?
Developers should implement strong security practices, including mandatory Multi-Factor Authentication (MFA) for all repository and package manager accounts, especially those with publishing rights. Regularly audit third-party dependencies for known vulnerabilities and suspicious behavior. Utilize supply chain security tools for integrity checks and artifact signing. Implement strict access controls and monitor CI/CD pipelines for anomalous activities. Consider using dependency-auditing tools and always verify the authenticity of new releases.
Q: What is the 'SleepyDuck Ethereum C2 Backdoor'?
The SleepyDuck backdoor is a malicious component that, once installed, fetches additional code from a remote server (e.g., api[.]frameworkmetrics[.]xyz) and executes it. Its Command-and-Control (C2) infrastructure leverages an Ethereum smart contract to receive instructions, making it resilient and harder to shut down. This specific C2 infrastructure has been linked to previous campaigns by the same threat actor.
Q: Why is this attack significant despite the quick removal of the packages?
This attack is significant because it highlights the vulnerability of trusted software supply chains. The malicious packages were distributed through legitimate channels and even bore valid digital signatures in some cases, bypassing typical security checks. Even with quick removal, users who downloaded the packages during the window of availability remain compromised until they manually remediate, as package managers typically don't roll back to older, safe versions.
Try Our Developer Utilities
Simplify your engineering workflows with our free browser-native tools: