# Socket links compromised Swarm releases to wallet and CI risks

Published 2026-11-10 · Crypto.world Team · Crypto.world

> Socket says compromised accounts published malicious versions of the bee-js library and Swarm Desktop, each carrying code that downloads and runs JavaScript. The report says the desktop app stores a Bee node key and plaintext password, while the code also ran inside the npm publishing job; the report could not determine what the downloaded code did there.

## Two releases carried loaders

[Socket](https://badge.socket.dev/blog/bee-js-compromise)'s Threat Research Team says compromised accounts pushed malicious releases of the bee-js library and Swarm Desktop on Nov. 9. The affected versions were @ethersphere/bee-js 13.3.0 on npm and Swarm Desktop 0.56.2 on GitHub. Both releases contained code that fetched JavaScript from api[.]frameworkmetrics[.]xyz and executed it with Node.js privileges, according to Socket.

In the npm package, the actor changed scripts/generate-version.cjs into a remote-code loader and made it run as a postinstall hook. The script sent the operating system as a request header and passed the server's response into a JavaScript function with access to the installer's require, console and process objects, Socket says. It did not check the response's status, content type or size.

Package-manager defaults differ, the report notes. npm 11 and earlier, Yarn Classic, and Yarn Berry before 4.14.0 run dependency postinstall scripts by default, Socket says. npm 12, pnpm 10 and later, Yarn Berry 4.14.0 and later, Bun and Deno skip unreviewed dependency scripts by default, according to the report.

## The publishing job also ran the code

During Ethersphere's publishing job, the compromised npm release ran the loader three times: during npm ci, the build, and the build run by npm publish, Socket says. That job had id-token: write permission for trusted publishing. The command-and-control server returned JavaScript to the GitHub-hosted runner during those executions, but the public job log does not show what the downloaded code did beyond printing a line, according to the report.

Whether the served code read the runner's environment or requested an OIDC token remains undetermined; Socket could not determine either. The package's provenance attestation was genuine, Socket also says: it identified the release workflow, tag and commit used to build the package, but showed where it was built rather than whether its source had been reviewed.

The compromised release workflow accepted a GitHub release even when the test and check jobs were skipped, Socket says. The publish environment had no required reviewers or tag policy, and the deployment completed without an approval step, according to the report. npm published version 13.3.0 at 00:09:50 UTC on Nov. 9 and removed it at 01:24:58 UTC, according to Socket.

## Desktop build and access

For Swarm Desktop 0.56.2, the same loader was found in the Electron main process across the packages Socket examined. The code ran when the application launched and fetched JavaScript from the same host, using a different request path, according to the report. The release was built, signed and notarized by the project's CI, Socket says.

The build workflow was manually triggered and supplied Apple and Windows signing certificates, their passwords and the Apple ID used for notarization, Socket says. The app stores the Bee node's config.yaml, which contains a plaintext password, and the node key under data-dir/keys/ on every install, according to the report.

## Earlier credential attempts

The two compromised GitHub accounts were nugaon and bee-worker; Socket says their compromise predates Nov. 6, and the origin remains unexplained. The report describes a separate set of Nov. 6 attempts to harvest repository secrets through workflows and changes to an existing workflow file.

With moderate confidence, Socket assesses that nothing was exfiltrated in those Nov. 6 attempts. The collectors' captured requests contained no body data, Socket says, while the outcome of one collector remained ambiguous. That assessment concerns the earlier credential-harvesting attempts; Socket's report does not determine what the JavaScript served to the Nov. 9 publishing job did.

## Sources

1. Original source · Blog post [Socket](https://badge.socket.dev/blog/bee-js-compromise) badge.socket.dev

## Related stories

- [Report URI finds Optimizely malware on 178 organizations’ sites](https://crypto.world/news/report-uri-optimizely-malware-178-organizations)
- [Trezor Warns CryptoBilis Buyers After Safe 5 Implant Report](https://crypto.world/news/trezor-cryptobilis-safe-5-implant-report)
- [X Wallet Changed Deposit Routes as User Payouts Paused](https://crypto.world/news/x-wallet-deposit-routes-user-payouts-paused)
- [Aave community proposes study of temporary borrowing controls](https://crypto.world/news/aave-community-proposes-temporary-borrowing-controls-study)
- [ACryptoS says exploit hit 77 vaults across five chains](https://crypto.world/news/acryptos-exploit-77-vaults-five-chains)

## Explore

[More articles](https://crypto.world/news)

---

Canonical: https://crypto.world/news/socket-compromised-swarm-releases-wallet-ci-risks
