1-minute read of a 5 min report

Ethersphere Release Hack Exposes Bee Developers and Swarm Desktop Users

By

1-minute read

What a defender needs to know

Ethersphere’s release automation published @ethersphere/bee-js 13.3.0 with a malicious postinstall loader and Swarm Desktop 0.56.2 with a loader in the Electron main process. Socket Research found the npm loader ran three times inside Ethersphere’s own publishing job. The npm package carried valid SLSA provenance; the macOS desktop build was signed and notarized. Each loader fetched JavaScript from api[.]frameworkmetrics[.]xyz, which could run with the installer’s or desktop process’s privileges.

Search lockfiles, package caches, mirrors and CI install logs for @ethersphere/bee-js 13.3.0 from 00:09:50 to 01:24:58 UTC on November 9. Replace that version with 13.2.0 and clear cached copies. On desktop systems, inspect the installed version and bee-desktop.log for Bee Desktop version: 0.56.2 (production); replace 0.56.2 with the project-listed 0.56.3 release. Linux packages require manual replacement.

For hosts that executed either loader, preserve process and network evidence, investigate ~/.solidity/, com.solidity.langsupport.runner, solidity-langsupport-runner.service and ScreenConnect service ID 5cbe79c9c25524df. Rotate credentials reachable from affected developer and CI environments; move Bee wallet funds to a new key from a clean machine if the desktop app ran. Verify installed and cached versions and account for past execution. A clean replacement package and an application uninstall do not remove an implant already on a host.

Primary sources