Open source package with 1 million monthly downloads stole user credentials - Ars Technica

An open source package with more than 1 million monthly downloads, `element-data`, was compromised after attackers exploited a flaw in the developers’ GitHub-based workflow. The vulnerability let the threat actor access signing keys and other sensitive account data, then publish a malicious release, version 0.23.3, to both Python Package Index and Docker accounts. The fake package was nearly identical to the legitimate one, making it difficult to detect. When executed, the malicious version searched infected systems for credentials and secrets, including user profiles, warehouse credentials, cloud provider keys, API tokens, SSH keys, and `.env` file contents. The developers said anyone who installed version 0.23.3 or ran the affected Docker image should assume exposed credentials may have been compromised. The malicious release was removed within about 12 hours, and the issue was discovered through a third-party report. The attackers reportedly abused a GitHub action tied to a pull request, running a bash script inside the developers’ account to steal data. After the incident, the maintainers rotated exposed credentials, fixed the flaw, and audited other GitHub actions for similar weaknesses. Users are advised to verify their installed version, uninstall 0.23.3, upgrade to 0.23.4, clear caches, check for the malware marker file, and rotate any potentially exposed secrets. The incident highlights the growing risk of supply-chain attacks against open source software.

Build this article’s timeline

Extract dated events, key actors, and open questions using the same timeline analysis available in Signal.

Log in to build

Timeline generation is available to signed-in community members.

Five Ws 🤖 4 AI prefills · 1 still unanswered
Who
HD Moore, Ars Technica, Elementary Cloud, and Elementary
🤖 AI prefill
What
An open source package with more than 1 million monthly downloads, `element-data`, was compromised after attackers exploited a flaw in the developers’ GitHub-based workflow.
🤖 AI prefill
When When did this happen, or what is the timeframe?
Where
San Francisco, macOS, and Linux
🤖 AI prefill
Why
Centers on supply-chain attack, open source package, and element-data
🤖 AI prefill

Login to answer and earn XP for each gap you fill.

Supply Chain Attack open source, package, malicious version, signing keys, compromised Credential Theft credentials, API tokens, SSH keys, cloud keys, warehouse credentials Incident Response remove, rotate, uninstall, patch, audit GitHub Workflow Flaw GitHub action, pull request, bash script, developer account, vulnerability
supply-chain attack98% open source package95% element-data94% GitHub action92% signing keys91% developer account workflow89% malicious package88% user credentials87% Python Package Index84% Docker image accounts82%
24
Manipulation Score: Low How much this article uses emotional framing vs. straight reporting
Loaded Language 1225%
Absolutist 815%
Threat/Panic 2825%
Us vs Them 415%
Engagement Bait 1820%
Manipulation score look right?

Factual Claims (10)

medium technology
An open source package with more than 1 million monthly downloads was compromised.
high technology
Attackers exploited a vulnerability in the developers’ account workflow to access signing keys and sensitive information.
high technology
The malicious package scoured systems for user profiles, warehouse credentials, cloud provider keys, API tokens, and SSH keys.
medium technology
The malicious version was 0.23.3 and was published to Python Package Index and Docker image accounts.
medium technology
The malicious package was removed about 12 hours later, on Saturday.
high technology
Users who installed 0.23.3 or ran the affected Docker image should assume credentials in that environment may have been exposed.
high technology
The threat actor gained access through a vulnerability in a GitHub Action created by the developers.
high technology
The attackers were able to run a bash script inside the developer’s account via a pull request.
medium technology
The developers learned of the compromise from a third-party issue report.
medium technology
The developers rotated exposed credentials, fixed the vulnerability, and audited other GitHub Actions.

Comments

Login to view and post comments.

🏠Portal 📰Links ❓Q&A 📅Events 💼Jobs