Why wasn't this vulnerability fixed before the attack happened?
A contributor flagged the workflow weakness and proposed a fix on May 17, 2026, but per Wiz and Chainguard it sat unmerged for 58 days before the July 14 exploit. Microsoft's own timeline traces the underlying proof-of-concept even earlier, to April 29 — months of visibility before anyone acted on it.
Answered in
A Misconfigured GitHub Action Backdoored Packages With 3M Weekly DownloadsA pull_request_target flaw in AsyncAPI's CI let attackers steal a token and trojan 4 npm packages — 3M+ weekly downloads — with credential-stealing code.
Read the full analysisOther questions this article answers
More development best practices questions
- How many outage reports did Claude and ChatGPT get on July 14, 2026?
- What did Anthropic's own status page say about the July 14 Claude outage?
- Did Claude have more outages after July 14?
- What did ChatGPT's status checker say was wrong?
- Is this outage pattern actually unusual for AI providers?
- What GitHub Actions vulnerability did the attacker exploit?
- How many npm packages were compromised, and how widely were they used?
- What did the malicious payload actually do?
Every answer on Crashtech is written by the editor of the article it comes from — never auto-summarised. Browse all answers or the Development Best Practices beat.