Industry shifts, security alerts, hardware, and AI/ML Compiled for immediate developer deployment.
calendar_todaysummarizeWeek 18-2026bolt2 CRITICAL
article
Fake "tanstack" npm Package Publishes Four Malicious Versions in 27 Minutes to Steal .env Files
TAG: SECURITY
On April 29, 2026, an attacker published four versions of the unscoped tanstack npm package — 2.0.4 through 2.0.7 — in just 27 minutes, each containing a postinstall hook that silently exfiltrates .env and .env.local files to a Svix webhook endpoint under the attacker's control. The real TanStack organization (publisher of @tanstack/query, @tanstack/router, and related packages with millions of weekly downloads) has no connection to the unscoped tanstack name, which the attacker registered separately. Version 2.0.6 escalated the attack by sweeping all .env.* variants in the working directory. The attacker visibly iterated on their payload across the four releases, adjusting targeting, re-enabling an opt-out flag, and suppressing console output. Affected versions expose AWS keys, GitHub tokens, npm publish tokens, database credentials, and third-party API keys. Developers should check lock files for versions 2.0.4 through 2.0.7 and immediately rotate any credentials present at install time.
GitHub Discloses and Patches Critical RCE Vulnerability in git push Pipeline (CVE-2026-3854)
TAG: SECURITY
On March 4, 2026, Wiz researchers reported a critical remote code execution vulnerability affecting github.com and all GitHub Enterprise variants. Any user with push access to any repository — including one they created themselves — could execute arbitrary commands on GitHub's servers by passing a crafted push option containing an unsanitized delimiter character. GitHub validated the report in 40 minutes, deployed a fix to github.com within two hours, and confirmed via telemetry that only the Wiz researchers' own test activity triggered the anomalous code path — no customer data was accessed. Patches for GitHub Enterprise Server are available in releases 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4, and 3.20.0 or later. The fix also removes an unnecessary code path from environments where it should not have existed, improving defense in depth. The vulnerability is tracked as CVE-2026-3854.
Mini Shai-Hulud: Compromised SAP npm Packages Deliver Bun-Based Credential Stealer
TAG: SECURITY
Aikido Security discovered a supply-chain compromise targeting SAP's npm ecosystem, affecting @cap-js/sqlitev2.2.2, @cap-js/postgresv2.2.2, @cap-js/db-servicev2.10.1, and mbtv1.2.48. Each compromised package adds a preinstall hook that runs setup.mjs, which downloads Bun runtime 1.3.13 and executes an 11.7 MB obfuscated payload named execution.js. The payload harvests GitHub tokens, npm tokens, GitHub Actions secrets, AWS STS credentials, Azure Key Vault secrets, GCP Secret Manager values, and Kubernetes service account tokens, then exfiltrates encrypted results to attacker-controlled GitHub repositories using AES-256-GCM encryption. The likely entry point was an npm publish token exposed through a malicious CircleCI pull request build on the SAP/cloud-mta-build-tool repository. The malware propagates by modifying release tarballs and pushing backdoored files to repositories using stolen tokens under the commit message "chore: update dependencies" attributed to claude@users.noreply.github.com.
GitHub Copilot Moves to Usage-Based Billing with AI Credits Starting June 1, 2026
TAG: AI
GitHub announced that all Copilot plans will transition from premium request units (PRUs) to a token-based GitHub AI Credits system on June 1, 2026. Base plan pricing remains unchanged — Copilot Pro at $10/month, Pro+ at $39/month, Business at $19/user/month, and Enterprise at $39/user/month — with each plan's monthly dollar value converted directly into an equivalent AI Credits allotment. Code completions and Next Edit suggestions remain included in all plans without consuming credits. A preview bill experience launches in early May so users and admins can project costs before the transition. Business and Enterprise customers receive promotional bonus credits ($30 and $70 respectively) for June through August. Admins gain new budget controls at enterprise, cost center, and user levels, and included credits can now be pooled across an organization.
73 More Fake Extensions Linked to GlassWorm Found in Open VSX Marketplace
TAG: SECURITY
Threat intelligence firm Socket identified 73 additional malicious VS Code extensions uploaded to the Open VSX registry, following 72 similar extensions discovered the prior month. The extensions impersonate legitimate developer tools and initially ship benign code to bypass malware scanners; after connecting to newly-created GitHub or other public accounts, they download the GlassWorm loader as an update. GlassWorm's stage 3 payload includes a credential theft module that harvests GitHub and npm tokens, then force-pushes malware into the victim's repositories. The campaign includes host-gating logic that skips infection on Russian-locale machines, leading Socket's Philipp Burckhardt to suspect Russian threat actors. Of the 73 new extensions, 14 had been activated within a week of discovery. The Eclipse Foundation was notified and expects all 73 have now been removed. Security researchers emphasize that IDE extensions currently lack the integrity verification, lockfile equivalents, and organizational policy controls that exist for software packages.
GitHub CTO Addresses Two Major Availability Incidents and Outlines 30x Scaling Plan
TAG: INDUSTRY
GitHub CTO Vlad Fedorov published a transparency post following two significant incidents in April 2026. On April 23, a regression in merge queue operations caused squash-merge commits to be generated from incorrect base states, affecting 658 repositories and 2,092 pull requests — without any data loss, but leaving default branches in incorrect states. On April 27, a botnet attack overloaded GitHub's Elasticsearch cluster, disabling search-backed features across pull requests, issues, and projects. Fedorov revealed that GitHub had begun a 10x capacity expansion in October 2025 but by February 2026 recognized the need to design for 30x scale, driven by rapidly accelerating agentic development workflows. The engineering response includes migrating webhooks out of MySQL, redesigning session caching, isolating git and GitHub Actions from other workloads, migrating performance-sensitive Ruby code to Go, and pursuing a multi-cloud architecture.
Theo (t3.gg) delivers an extended critical analysis of GitHub's reliability collapse in late April 2026, covering the merge queue regression that silently reverted 2,092 merged pull requests, the Elasticsearch outage that took down search across issues and PRs for a full workday, and the CVE-2026-3854 remote code execution vulnerability. He cites a community-built alternative status page showing GitHub's actual uptime at roughly 86.75% rather than the official figure. Theo also addresses the fake tanstack npm package that stole .env credentials, arguing GitHub and npm bore responsibility for ignoring months of reports from TanStack creator Tanner Linsley. The video examines GitHub's organizational problems — no CEO since Thomas Dohmke's departure, a hard wall between product and engineering — and quotes Mitchell Hashimoto (creator of Vagrant, Terraform, and Ghosty) explaining why the Ghosty project is leaving GitHub after 18 years.
Fake "tanstack" npm Package Publishes Four Malicious Versions in 27 Minutes to Steal .env Files
On April 29, 2026, an attacker published four versions of the unscoped tanstack npm package — 2.0.4 through 2.0.7 — in just 27 minutes, each containing a postinstall hook that silently exfiltrates .env and .env.local files to a Svix webhook endpoint under the attacker's control. The real TanStack organization (publisher of @tanstack/query, @tanstack/router, and related packages with millions of weekly downloads) has no connection to the unscoped tanstack name, which the attacker registered separately. Version 2.0.6 escalated the attack by sweeping all .env.* variants in the working directory. The attacker visibly iterated on their payload across the four releases, adjusting targeting, re-enabling an opt-out flag, and suppressing console output. Affected versions expose AWS keys, GitHub tokens, npm publish tokens, database credentials, and third-party API keys. Developers should check lock files for versions 2.0.4 through 2.0.7 and immediately rotate any credentials present at install time.
Theo (t3.gg) delivers an extended critical analysis of GitHub's reliability collapse in late April 2026, covering the merge queue regression that silently reverted 2,092 merged pull requests, the Elasticsearch outage that took down search across issues and PRs for a full workday, and the CVE-2026-3854 remote code execution vulnerability. He cites a community-built alternative status page showing GitHub's actual uptime at roughly 86.75% rather than the official figure. Theo also addresses the fake tanstack npm package that stole .env credentials, arguing GitHub and npm bore responsibility for ignoring months of reports from TanStack creator Tanner Linsley. The video examines GitHub's organizational problems — no CEO since Thomas Dohmke's departure, a hard wall between product and engineering — and quotes Mitchell Hashimoto (creator of Vagrant, Terraform, and Ghosty) explaining why the Ghosty project is leaving GitHub after 18 years.
GitHub Discloses and Patches Critical RCE Vulnerability in git push Pipeline (CVE-2026-3854)
On March 4, 2026, Wiz researchers reported a critical remote code execution vulnerability affecting github.com and all GitHub Enterprise variants. Any user with push access to any repository — including one they created themselves — could execute arbitrary commands on GitHub's servers by passing a crafted push option containing an unsanitized delimiter character. GitHub validated the report in 40 minutes, deployed a fix to github.com within two hours, and confirmed via telemetry that only the Wiz researchers' own test activity triggered the anomalous code path — no customer data was accessed. Patches for GitHub Enterprise Server are available in releases 3.14.25, 3.15.20, 3.16.16, 3.17.13, 3.18.7, 3.19.4, and 3.20.0 or later. The fix also removes an unnecessary code path from environments where it should not have existed, improving defense in depth. The vulnerability is tracked as CVE-2026-3854.
Mini Shai-Hulud: Compromised SAP npm Packages Deliver Bun-Based Credential Stealer
Aikido Security discovered a supply-chain compromise targeting SAP's npm ecosystem, affecting @cap-js/sqlitev2.2.2, @cap-js/postgresv2.2.2, @cap-js/db-servicev2.10.1, and mbtv1.2.48. Each compromised package adds a preinstall hook that runs setup.mjs, which downloads Bun runtime 1.3.13 and executes an 11.7 MB obfuscated payload named execution.js. The payload harvests GitHub tokens, npm tokens, GitHub Actions secrets, AWS STS credentials, Azure Key Vault secrets, GCP Secret Manager values, and Kubernetes service account tokens, then exfiltrates encrypted results to attacker-controlled GitHub repositories using AES-256-GCM encryption. The likely entry point was an npm publish token exposed through a malicious CircleCI pull request build on the SAP/cloud-mta-build-tool repository. The malware propagates by modifying release tarballs and pushing backdoored files to repositories using stolen tokens under the commit message "chore: update dependencies" attributed to claude@users.noreply.github.com.
GitHub Copilot Moves to Usage-Based Billing with AI Credits Starting June 1, 2026
GitHub announced that all Copilot plans will transition from premium request units (PRUs) to a token-based GitHub AI Credits system on June 1, 2026. Base plan pricing remains unchanged — Copilot Pro at $10/month, Pro+ at $39/month, Business at $19/user/month, and Enterprise at $39/user/month — with each plan's monthly dollar value converted directly into an equivalent AI Credits allotment. Code completions and Next Edit suggestions remain included in all plans without consuming credits. A preview bill experience launches in early May so users and admins can project costs before the transition. Business and Enterprise customers receive promotional bonus credits ($30 and $70 respectively) for June through August. Admins gain new budget controls at enterprise, cost center, and user levels, and included credits can now be pooled across an organization.
73 More Fake Extensions Linked to GlassWorm Found in Open VSX Marketplace
Threat intelligence firm Socket identified 73 additional malicious VS Code extensions uploaded to the Open VSX registry, following 72 similar extensions discovered the prior month. The extensions impersonate legitimate developer tools and initially ship benign code to bypass malware scanners; after connecting to newly-created GitHub or other public accounts, they download the GlassWorm loader as an update. GlassWorm's stage 3 payload includes a credential theft module that harvests GitHub and npm tokens, then force-pushes malware into the victim's repositories. The campaign includes host-gating logic that skips infection on Russian-locale machines, leading Socket's Philipp Burckhardt to suspect Russian threat actors. Of the 73 new extensions, 14 had been activated within a week of discovery. The Eclipse Foundation was notified and expects all 73 have now been removed. Security researchers emphasize that IDE extensions currently lack the integrity verification, lockfile equivalents, and organizational policy controls that exist for software packages.
GitHub CTO Addresses Two Major Availability Incidents and Outlines 30x Scaling Plan
GitHub CTO Vlad Fedorov published a transparency post following two significant incidents in April 2026. On April 23, a regression in merge queue operations caused squash-merge commits to be generated from incorrect base states, affecting 658 repositories and 2,092 pull requests — without any data loss, but leaving default branches in incorrect states. On April 27, a botnet attack overloaded GitHub's Elasticsearch cluster, disabling search-backed features across pull requests, issues, and projects. Fedorov revealed that GitHub had begun a 10x capacity expansion in October 2025 but by February 2026 recognized the need to design for 30x scale, driven by rapidly accelerating agentic development workflows. The engineering response includes migrating webhooks out of MySQL, redesigning session caching, isolating git and GitHub Actions from other workloads, migrating performance-sensitive Ruby code to Go, and pursuing a multi-cloud architecture.
Supply-chain security dominated the week with three serious incidents. On April 29, an attacker published four malicious versions of the unscoped tanstack npm package (2.0.4–2.0.7) in 27 minutes; each used a postinstall hook to exfiltrate .env and .env.local files to an attacker-controlled Svix webhook endpoint. Separately, Socket identified 73 more fake VS Code extensions in the Open VSX registry linked to the GlassWorm campaign — which uses a deferred download pattern to bypass scanners and deploys a credential theft module that force-pushes malware into victims' repositories. And Aikido Security uncovered a compromise of SAP's npm packages (@cap-js/sqlitev2.2.2, @cap-js/postgresv2.2.2, @cap-js/db-servicev2.10.1, mbtv1.2.48), where a preinstall hook downloads Bun runtime 1.3.13 and executes an 11.7 MB obfuscated payload that harvests AWS, GitHub, Azure, GCP, and Kubernetes credentials encrypted with AES-256-GCM.
GitHub disclosed and patched CVE-2026-3854, a critical RCE vulnerability in its push pipeline: any user with push access could execute arbitrary commands by passing a crafted push option with an unsanitized delimiter. GitHub validated and patched within two hours of the Wiz report. Enterprise Server patches are available in releases 3.14.25 through 3.20.0. GitHub also announced Copilot is moving to usage-based AI Credits billing on June 1, 2026, while keeping base plan prices unchanged and pooling credits across organizations.
GitHub's CTO published a transparency post following two April availability incidents — a merge queue regression affecting 658 repositories and 2,092 pull requests, and an Elasticsearch botnet overload — and announced plans to scale to 30x capacity, migrate webhooks off MySQL, and shift performance-sensitive Ruby code to Go.
Key Takeaways
Three supply-chain attacks hit this week: fake tanstack npm packages (versions 2.0.4–2.0.7) stealing .env files, 73 GlassWorm VS Code extensions on Open VSX, and compromised SAP npm packages using Bun to run an AES-256-GCM credential stealer.
CVE-2026-3854 is a critical RCE in GitHub's git push pipeline — patched within two hours — with Enterprise Server fixes in releases 3.14.25 through 3.20.0.
GitHub Copilot switches to token-based AI Credits billing on June 1, 2026; GitHub's CTO simultaneously disclosed two major April incidents and a 30x capacity expansion plan driven by agentic development workflows.
