Security · Contributed
The Seal Was Genuine
On November 9, attackers pushed a malicious package and a malicious desktop app through a project's own release machinery. Both looked legitimate by every badge a user can check. Here is what the reporting confirms, what nobody knows yet, and what a badge actually proves.
What the sources agree on
Ethersphere maintains bee-js and Swarm Desktop, tooling for building on and running Swarm Bee nodes. On November 9 (UTC), Socket reports, attackers published a malicious @ethersphere/bee-js 13.3.0 to npm and a trojanized Swarm Desktop 0.56.2 on GitHub. The Hacker News reaches the same account. The npm version stayed live for about 75 minutes. The desktop release stayed up for about eight and a half hours, and the app's built-in updater could offer it to Windows and Apple Silicon Mac users within minutes of its release.
Both carry a small loader that downloads more code from a remote server and runs it. Per Socket, the second stage looks for the node's config.yaml, which stores the keystore password in plain text, and its swarm.key file, and sends both out. Those two files together unlock the node's wallet. A third stage installs a remote-access backdoor: a ScreenConnect client on Windows, a hidden shell on macOS and Linux. Reinstalling the app does not remove it.
Why the badges didn't help
This is the part worth sitting with. Socket says the npm publish ran through Ethersphere's real trusted-publishing workflow, so the provenance attestation is genuine. The macOS build was signed with the project's Developer ID and notarized by Apple. Nothing was forged. The attackers used the project's own pipeline, which Socket says accepted a release event or arbitrary branch input without an approval step.
A provenance record and a notarization stamp answer one question: did this come from this project's build system? They don't answer whether the build system was telling the truth. When the people or accounts driving the pipeline are compromised, the seal is genuine and the contents are not.
What nobody has said
How the attackers got in is unexplained. The maintainer attributes it to stolen CI credentials, per The Hacker News. Socket points to two compromised GitHub accounts, a maintainer's and the release bot's, and says the origin predates November 6. Neither source explains how they were taken.
There is also no confirmed victim count and no reported theft. Socket counts 65 downloads of the desktop release by 08:27 UTC and calls those upper bounds that include researchers. It estimates about ten fetches of the npm version, and flags that as unconfirmed. The sources differ on the fix, too. Socket's snapshot at 10:30 UTC said no clean desktop release was out yet. The Hacker News says 0.56.3 shipped the same day. If you're acting on this, check the project's own releases page.
Socket links the infrastructure to the SleepyDuck and EtherDuck campaigns. That attribution is Socket's, with the on-chain evidence in its post.
What I'd do
I've written node-ecosystem guides, and what stands out to me here is simple: the key and the password to open it sat side by side on a machine that auto-updates and runs third-party code. That's like taping the safe's combination inside the door. Concretely:
Check whether you were exposed. Search lockfiles, caches and CI logs for [email protected]. For the desktop app, look for 0.56.2 in bee-desktop.log. If either ran, treat the key and password as stolen, and move funds to a new key from a clean machine. Don't just update.
Look for persistence. Socket lists a ~/.solidity/ folder, a com.solidity.langsupport.runner LaunchAgent, and a ScreenConnect service. A rebuild from a trusted image beats cleaning by hand.
Pin versions on machines that hold keys. Turn off auto-update on anything that stores a wallet key. Update on purpose, a day or two after release, after reading what changed. A 75-minute window never reaches you if you wait.
Keep keys off the build box. If you maintain a project, the same logic applies to signing credentials: don't hand them to a workflow that anyone with release access can trigger from any branch. Socket recommends protected branches and required reviewers on publishing environments.
Hold only a working balance on a node machine. Anything you don't need this week belongs behind a key that the machine can't read.
The boring conclusion
A badge tells you who built it. It doesn't tell you the builder is still in control of the build. Treat a trust mark as the start of checking, and keep the wallet key away from anything that updates itself.
Verify everything, including the things that look verified.