@ethersphere/bee-js 13.3.0 on npm ran an install hook that loads remote code, reads Swarm Desktop wallet files and installs persistence.
Ethersphere publishes @ethersphere/bee-js, the JavaScript client for the Swarm network. GitHub lists 13.3.0 as malware with no patched version.
What happened
Version 13.3.0 added an install hook that runs remote code.
- StepSecurity reports that commit
de2f74e784b2eafa0d66fbb6d88b42ea11ee34cfwent straight to theupcomingbranch under thebee-workeridentity. - The release went out through the project's normal publish workflow, so it carries valid provenance.
package.jsonmovednode scripts/generate-version.cjsfrompreparetopostinstall.- The script gets JavaScript from
api.frameworkmetrics[.]xyzand runs it. - The payload looks for Swarm Desktop
config.yamlanddata-dir/keys/swarm.keyand sends them to/v1/swarm/report.
StepSecurity dates the npm release to 9 November 2026 at 00:09:50 UTC.
Affected versions
13.3.0: the malicious release.13.2.0: StepSecurity found no malicious hook in it.- Ranges that allow 13.3.0:
@ethersphere/swarm-cli3.7.0 (^13.2.0),@ethersphere/bee-dashboard0.37.1 (^13.0.0) and theswarm-desktoprepository (^13.0.0).
Indicators of compromise
- Domain
api.frameworkmetrics[.]xyz, paths/v1/analytics,/v1/assets/and/v1/swarm/report. - Request header
X-Ethersphere: 1. - Tarball SHA-1:
a205c8a5fed81e9a787645b2801f00be3db3348d. linux_amd64SHA-256:9b73e7cd4e1425e770392549d8df46c706139ef476f4f7b9ac405165dc8d9696.linux_arm64SHA-256:b601776817363b96295119f7221338a122d5247a35a77a64b04f286e1bbcc565.- Linux:
~/.solidity/.run.pyand~/.config/systemd/user/solidity-langsupport-runner.service. - macOS:
~/Library/LaunchAgents/com.solidity.langsupport.runner.plist. - Windows:
%TEMP%files that start with.stuffed-and%LOCALAPPDATA%\.<32-hex-guid>\app.msi.
How to check
Look for 13.3.0 in each project. This command only reads files.
npm ls @ethersphere/bee-js --all
On macOS or Linux, look for the persistence files.
ls -la ~/.solidity ~/.config/systemd/user/solidity-langsupport-runner.service ~/Library/LaunchAgents/com.solidity.langsupport.runner.plist 2>/dev/null
What to do now
- If 13.3.0 installed with scripts on, isolate the machine and rebuild it from a trusted image.
- From a clean machine, rotate every credential that the user or CI job can reach.
- If Swarm Desktop wallet files were present, treat the keystore and its password as exposed. Move funds to a new wallet.
- Pin
@ethersphere/bee-jsto 13.2.0 and blockapi.frameworkmetrics[.]xyz.
What Vigilance would show
Vigilance checks each update before it installs. This is what a customer sees, rebuilt from the facts on this page.
On the computer, at install
Vigilance blocked `@ethersphere/bee-js` 13.3.0. This version is too new or changed in a way Vigilance must check first. The last safe version is 13.2.0. Install that version.
In the owner report
Bad update
@ethersphere/bee-js 13.3.0
This update now runs a command on its own when it is installed, downloads from the internet and reads saved passwords and access keys. The version before it did not.
- Ask the AI tool to swap @ethersphere/bee-js to 13.2.0. That is the last safe version.
Frequently asked questions
Does removing bee-js 13.3.0 clean the machine?
No. Removal does not undo code that already ran. It also does not remove the service or LaunchAgent the payload installs.
Does --ignore-scripts protect against this attack?
It stops this hook at install time. It does not fix an earlier install that ran with scripts on.