HomeAI · summaries
Storia in 3 fonti
TanStack weighs invitation-only pull requests after supply chain attack
Shai-Hulud worm exploited GitHub Actions misconfiguration to poison shared cache, now project weighing nuclear option on unsolicited contributions
Confronto fonti
3 prospettive sulla stessa storiaTimeline cronologica
- ·
theregister.com
TanStack weighs invitation-only pull requests after supply chain attack
Shai-Hulud worm exploited GitHub Actions misconfiguration to poison shared cache, now project weighing nuclear option on unsolicited contributions
- ·
heise.de
TanStack verschärft Sicherheitsvorkehrungen nach Supply-Chain-Attacken
TanStack verschärft nach Supply-Chain-Attacken seine Sicherheitsmaßnahmen. Pull Requests könnte es künftig nur noch auf Einladung geben.
- ·
bleepingcomputer.com
Grafana breach caused by missed token rotation after TanStack attack
The Grafana data breach was caused by a single GitHub workflow token that slipped through the rotation process following the TanStack npm supply-chain attack last week.
- ·
GitHub links repo breach to TanStack npm supply-chain attack
GitHub says the hackers who breached 3,800 internal repositories gained access via a malicious version of the Nx Console VS Code extension, compromised in last week's TanStack npm…