DevOps News • Technical Intelligence"wfx-loot" Campaign Hits 61,764 GitHub Repos, Executing 1,500-Line Secret-Stealing Malware in 1,806+ CI Pipelines via npm Hooks
Researchers at Aikido Security, GitGuardian, and StepSecurity uncovered a massive GitHub supply-chain attack (wfx-loot) in which 4,837 hijacked accounts (including tokens leaked via .git/config files from the Fly.io GitHub App) opened probe PRs titled docs: dependency audit notes across 61,764 repositories and executed a 1,500-line shell script in at least 1,806 repos before reverting commits and deleting workflow run logs within 60 seconds. Bypassing GitHub's action_required workflow holds by injecting a postinstall hook into package.json triggered by existing CI npm install steps, the payload dumps runner process memory for unreferenced secrets, harvests OpenAI/Anthropic/Copilot/Cursor keys, exchanges OIDC tokens for AWS/GCP/Azure sessions, mints persistent AWS IAM keys, and exfiltrates archives over Telegram.
DevOps News Analysis & SRE Takeaway
Also covered by: Aikido Security Research, GitGuardian Security Advisory
Infrastructure & Production Blast Radius
For platform engineering and site reliability teams, updates in this sector demand swift operational posture reviews. Critical language vulnerabilities, container runtime boundaries, and foundational AI agent architectures require continuous cross-checking of ingress rules, kernel syscall monitoring, container image base layers, and least-privilege IAM policies across production clusters and sovereign cloud environments.
Ensure automated CI/CD deployment pipelines enforce container image provenance scanning, dependency SBOM verification, and proactive canary rollouts with telemetry-driven automated rollback triggers before promoting runtime updates across enterprise workloads.
Operational Reliability & Incident Mitigation
When deploying remediation patches or architecture upgrades, DevOps engineers should execute canary deployments against non-critical ingress routes first. Verify service level objectives (SLOs), error budgets, p99 latency distributions, and CPU memory utilization baselines through Prometheus and OpenTelemetry dashboards before completing complete cluster rotation.
Audit ingress logs for anomalous payload signatures, inspect container egress connections to unapproved endpoints, and validate that runtime security agents maintain active eBPF syscall capture across all application namespaces to maintain zero-trust reliability.
Continuous automated verification across CI/CD delivery pipelines ensures runtime dependencies and base images meet stringent zero-trust benchmarks before promotion. Integrate security policy engines into staging gates, and maintain comprehensive audit trails for regulatory compliance, post-incident reviews, and enterprise resilience.
Cross-Functional Collaboration & Governance
Coordinate across security, platform, and product engineering teams to establish clear patching SLAs. Integrate automated vulnerability notifications into developer Slack channels and PagerDuty escalation policies, ensuring continuous alignment and audit readiness across distributed infrastructure tiers. Maintaining resilient platform infrastructure requires continuous observability, proactive posture management, automated testing of rollback procedures, and comprehensive post-incident blameless reviews.
This is a verified engineering summary of the primary source publication, curated for platform, DevOps, and SRE practitioners. The original publication remains the primary record.