Open Source Package with 1 Million Monthly Downloads Stole User Credentials

Why It Matters

The breach demonstrates how a single compromised CI workflow can weaponize a widely used open‑source package, exposing thousands of downstream organizations to credential theft and downstream attacks.

Key Takeaways

• Malicious element-data 0.23.3 downloaded over 1M times monthly.
• Attack leveraged compromised GitHub Action to steal signing keys.
• Developers removed package within 12 hours and rotated credentials.
• Users urged to uninstall, upgrade to 0.23.4, and rotate secrets.
• Incident highlights supply‑chain risk in open‑source CI workflows.

Pulse Analysis

The element-data supply‑chain incident underscores a growing threat vector: attackers hijacking CI/CD pipelines to inject malicious code into trusted packages. By exploiting a vulnerable GitHub Action, the threat actor accessed the project’s signing keys and published a counterfeit version that silently harvested credentials from any environment it touched. With more than a million monthly downloads, the compromised package could have compromised a vast swath of data‑engineering workloads, from cloud warehouses to CI runners, before the developers detected and removed it within half a day.

Beyond the immediate fallout, this event amplifies concerns about the security hygiene of open‑source projects that rely on automated workflows. GitHub Actions, while accelerating development, often grant elevated permissions that, if misconfigured, become a backdoor for supply‑chain attacks. Industry experts note that many repositories lack rigorous code‑review policies for workflow files, making pull‑request‑based code execution a low‑hanging fruit for adversaries. Tools like zizmor can scan for such weaknesses, but proactive auditing and the principle of least privilege remain essential to mitigate risk.

For enterprises, the incident is a reminder to treat third‑party packages as potential attack surfaces. Organizations should enforce strict version pinning, regularly audit dependency trees, and implement runtime monitoring for anomalous credential access. Prompt incident response—such as rotating secrets, revoking compromised tokens, and scanning for indicator‑of‑compromise artifacts—can limit damage. As supply‑chain threats evolve, investing in secure CI/CD practices and continuous dependency hygiene will be critical to safeguarding the software supply chain.