[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fYrZy-z6DUZhkNPJT05AGS920TOI3qiQYwsX0V_I88AA":3},{"lesson":4},{"id":5,"slug":6,"article_id":7,"title":8,"body":9,"prevention":10,"framework_refs":11,"framework_notes":19,"status":27,"created_at":28,"published_at":29,"article":30,"tags":34,"podcasts":47,"controls":48},"658f4cfc-70d4-4338-b78d-eb0e8537ce91","compromised-github-automation-injects-backdoor-into-ethereum-npm-package","177f1c38-7ea1-43f9-9b3a-be7a910dbd28","Compromised GitHub Automation Injects Backdoor into Ethereum npm Package","Threat actors compromised Ethersphere's GitHub automation pipeline to publish malicious versions of a trusted npm package and desktop application, embedding a loader that fetched and executed arbitrary JavaScript with full Node.js privileges. This is a classic software supply chain attack: by hijacking the build and release infrastructure rather than the source code directly, the attacker bypassed typical code review processes and inherited the trust users placed in the legitimate publisher. The reuse of infrastructure from a prior campaign (SleepyDuck\u002FEtherDuck) suggests a persistent, targeted threat actor operating against the Ethereum ecosystem. This matters because downstream developers and end users who automatically consume package updates are silently compromised with no visible warning. Trust in open-source ecosystems depends on the integrity of CI\u002FCD pipelines and package signing, both of which failed here.","**Immediate actions:**\n- Audit and rotate all GitHub automation credentials, secrets, and tokens associated with the compromised repositories immediately.\n- Yank or deprecate the malicious npm package versions and issue a public advisory to downstream consumers specifying safe version ranges.\n- Scan all systems that consumed the malicious package versions for indicators of compromise tied to SleepyDuck\u002FEtherDuck infrastructure.\n\n**Long-term improvements:**\n- Enforce multi-party approval (e.g., required reviewers + protected branch rules) for any automated workflow that publishes packages to npm or GitHub Releases.\n- Implement npm package provenance and code signing (e.g., Sigstore\u002Fnpm provenance attestations) so consumers can cryptographically verify that published artifacts originate from the expected CI pipeline.\n- Apply the principle of least privilege to all CI\u002FCD service accounts, ensuring automation tokens cannot publish releases without a secondary human or policy gate.\n\n**Detection measures:**\n- Monitor npm publish events and GitHub Release creation via audit logs and alert on any release triggered outside of normal business hours or from unexpected runner environments.\n- Integrate software composition analysis (SCA) tools into consumer pipelines to flag newly introduced remote code fetching behavior or unexpected network calls in updated dependencies.",[12,13,14,15,16,17,18],"CIS Control 7: Continuous Vulnerability Management","NIST SP 800-53 SI-2: Flaw Remediation","NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control","ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities","MITRE ATT&CK T1566: Phishing","OWASP A06:2021 Vulnerable and Outdated Components","NIS2 Article 21(2)(b)",{"NIS2 Article 21(2)(b)":20,"MITRE ATT&CK T1566: Phishing":21,"NIST SP 800-53 SI-2: Flaw Remediation":22,"OWASP A06:2021 Vulnerable and Outdated Components":23,"CIS Control 7: Continuous Vulnerability Management":24,"ISO\u002FIEC 27001:2022 A.8.8: Management of technical vulnerabilities":25,"NIST CSF 2.0 PR.AA: Identity Management, Authentication, and Access Control":26},"NIS2 requires entities to implement measures covering supply chain security including relationships with direct suppliers and service providers; vetting and monitoring the integrity of CI\u002FCD pipelines and published packages falls squarely within this obligation.","While the initial vector may have been credential compromise, the campaign's broader technique of trojanizing trusted packages to deliver a remote-code-fetching loader maps to supply-chain compromise techniques; awareness of these TTPs enables better detection rules for outbound C2 traffic from npm-based loaders.","SI-2 requires organizations to identify and remediate flaws in information systems, which extends to the integrity of the software release pipeline; a process for verifying published artifact integrity would have detected or blocked the malicious publish.","Consumers who automatically pull the latest version of bee-js without verifying provenance or reviewing changelogs exemplify the risk OWASP A06 warns against — blindly trusting third-party components without integrity verification.","Regularly assessing the security posture of CI\u002FCD pipeline configurations and automation credentials would have surfaced the weakened access controls that allowed the attacker to publish malicious releases.","A.8.8 requires timely identification and remediation of vulnerabilities in software and supporting infrastructure, including the third-party automation tooling used in the release pipeline that was subverted here.","The attacker exploited compromised GitHub automation credentials; enforcing strong authentication, least-privilege, and regular rotation of CI\u002FCD secrets directly addresses this attack vector.","published","2026-11-09T16:22:11.666051+00:00","2026-11-09T16:22:11.646+00:00",{"id":7,"url":31,"slug":32,"title":33},"https:\u002F\u002Fsocket.dev\u002Fblog\u002Fbee-js-compromise?utm_medium=feed","malicious-bee-js-npm-release-and-swarm-desktop-releases-deliver-sleepyduck-ether-c711ee","Malicious bee-js npm Release and Swarm Desktop Releases Deliver SleepyDuck Ethereum C2 Backdoor",[35,41],{"id":36,"name":37,"slug":38,"description":39,"color":40},"1ec88fde-2d0f-4ed8-932a-33f5ccc0fdc7","Access Control","access-control","Excessive privileges, missing MFA, weak auth","#f97316",{"id":42,"name":43,"slug":44,"description":45,"color":46},"f0c2a0af-58aa-4128-87c9-6acd30f2dc48","Supply Chain","supply-chain","Third-party risk, compromised dependencies","#8b5cf6",[],[49,53,57],{"slug":50,"name":51,"problem":52},"secrets-management","Secrets management","API keys, tokens and passwords stop leaking from code, chat and configuration files.",{"slug":54,"name":55,"problem":56},"threat-intelligence","Threat intelligence","Attack campaigns reach your sector, suppliers or software before your team hears about them.",{"slug":58,"name":59,"problem":60},"software-supply-chain","Software supply chain security","Malicious and vulnerable open-source packages are caught before they ship."]