
Git fixes, supply-chain evidence and operating limits — Week 46 Tech News
Track Git security patches, bee-js and CI compromise investigations, Cloudflare spend controls, Servo infrastructure, and ESLint’s contributor-pool closure. Compiled for immediate developer deployment.

wfx-loot campaign pushes CI secret stealer to tens of thousands of repositories

Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor
@ethersphere/bee-js 13.3.0 and Swarm Desktop 0.56.2 releases associated with the SleepyDuck backdoor. Compromised project identities introduced loader code into legitimate release paths, so trusted publishing and build provenance could accurately identify a build that still contained attacker-controlled changes. The npm package used an installation hook, while the desktop release placed its loader in Electron’s main process, creating different exposure paths. The investigation does not establish how the first credentials were stolen, and download counts cannot be treated as confirmed infected machines. Check exact versions and whether code executed, contain affected systems, and assess credentials and persistence; removing a release or uninstalling an application alone does not undo a payload that already ran.Introducing Spend Management: Spending limits and alerts for Cloudflare
Retiring the contributor pool
Sovereign Tech Fund and Servo

Git security vulnerabilities announced
wfx-loot campaign pushes CI secret stealer to tens of thousands of repositories
Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor
@ethersphere/bee-js 13.3.0 and Swarm Desktop 0.56.2 releases associated with the SleepyDuck backdoor. Compromised project identities introduced loader code into legitimate release paths, so trusted publishing and build provenance could accurately identify a build that still contained attacker-controlled changes. The npm package used an installation hook, while the desktop release placed its loader in Electron’s main process, creating different exposure paths. The investigation does not establish how the first credentials were stolen, and download counts cannot be treated as confirmed infected machines. Check exact versions and whether code executed, contain affected systems, and assess credentials and persistence; removing a release or uninstalling an application alone does not undo a payload that already ran.Introducing Spend Management: Spending limits and alerts for Cloudflare
Retiring the contributor pool
Sovereign Tech Fund and Servo
Three security reports require different responses. Git’s fixed releases address vulnerable repository processing; Socket’s investigation shows why genuine build provenance cannot establish that source changes were benign; Aikido separates broad write-access probes from evidence that a secret-stealing workflow ran.
Operational controls also have boundaries. Cloudflare’s beta spends time aggregating usage and propagating caps, so a pause policy is neither an instantaneous ceiling nor a substitute for planning service interruption.
The maintenance stories broaden the week beyond incident response: Igalia describes funded Servo integration and testing work, while ESLint closes a compensation program whose attribution policy became costly to enforce. Match the action to the proven condition, whether that condition is an affected executable, a compromised workflow, a delayed cap, or a maintenance constraint.
- Inventory affected Git and package versions, and distinguish download or probe counts from confirmed code execution.
- Investigate workflow and identity-trust changes when assessing persistence after credential theft.
- Plan for asynchronous spend enforcement and treat sustainable browser and maintainer work as operational infrastructure.