GigaTap articles tagged supply chain security.
- Mini Shai-Hulud: Where SLSA L2 Breaks - Valid SLSA attestations did not prevent a CI/CD compromise. Cache poisoning and token leakage exposed the limits of SLSA L2 isolation assumptions.
- Supply-Chain Warnings Hide in Ordinary Access Sales - Underground GitHub access, leaked repositories, OAuth tokens, and API keys can become supply-chain risk when they touch trusted delivery paths.
- Laravel Lang tag hijack turned old versions into malware - Attackers rewrote GitHub release tags for third-party Laravel Lang packages, causing Composer installs to pull credential-stealing malware from what looked
- npm worms are now a CI/CD trust problem - Unit 42’s updated report shows npm attacks shifting from typosquats to self-propagating campaigns that abuse tokens, package publishing, and CI/CD workflow
- Preinstall persistence shows where provenance breaks - Microsoft’s Red Hat npm Miasma report shows how trusted publishing can still deliver poisoned packages when the CI/CD path is compromised.
- TeamPCP shows why trusted packages are not safe by default - A reported TeamPCP wave hit VS Code, PyPI, and npm paths in the same week. The common failure was trust: verified publishers, official packages, and auto-u
- Mythos raises the cost of slow software supply chains - Chainguard’s Mythos guidance is best read as an operational warning: faster exploit development makes opaque dependencies, slow patching, and weak build pr
- zizmor hardening shows why CI parsers matter - Trail of Bits hardened zizmor against real GitHub Actions workflows, fixing YAML anchor, deserialization, and expression-evaluator issues found in a 41,253
- Miasma Turns npm Packages Into a Supply-Chain Worm - The Miasma campaign reportedly compromised Red Hat-related npm packages, targeting developer credentials, CI/CD systems, and cloud identities for further p
- Risky Business #837: GitHub Actions as a supply-chain fault line - Risky Business #837 points to the TanStack compromise and a familiar CI/CD risk: workflows with too much trust can turn package publishing into an incident
- GlassWorm C2 Takedown: What Teams Should Check - The GlassWorm takedown disrupts known C2 infrastructure, but security teams still need to check developer exposure, tokens, packages, and build paths.
- Glassworm’s takedown shows the new C2 problem - Glassworm was disrupted after researchers cut off four C2 channels at once. The real lesson is how supply-chain malware used developer tools, blockchain, D
- pnpm 11.4 makes locked installs harder to silently subvert - pnpm 11.4 turns tarball integrity mismatches into hard failures and tightens several install-time trust boundaries around credentials, git resolutions, pat
- Glassworm Shows Why Developers Are the New Supply Chain Target - CrowdStrike, Google, and Shadowserver disrupted Glassworm infrastructure, but the deeper lesson is about developer accounts, extensions, ads, and release t
- Grafana’s Missed Token Shows the Real CI/CD Risk - Grafana says one GitHub workflow token missed during post-TanStack incident response allowed attackers to access private repositories.
- Malicious npm package went after Claude workspace files - A reported npm package used install-time execution to upload files from Claude’s local user-data directory to GitHub, showing how AI workspaces are becomin
- OSV’s 157 Withdrawn Malware Reports Show a CI/CD Risk - Automated false positives hit npm and PyPI packages, then flowed into OSV-consuming tools. The issue is not just bad data, but enforcement built on fast-mo
- AI coding agents now need a governed supply chain - JFrog’s OpenCode integration points to a real shift: agents that install packages, publish artifacts, and add MCP servers need deterministic trust paths, n
- AntV npm compromise: why trusted packages still broke - A compromised npm maintainer account pushed malicious AntV-linked package versions that stole credentials through install hooks. The key lesson is not just
- Canvas Shows How SaaS Risk Becomes Classroom Risk - ReversingLabs’ Canvas report is a supply-chain warning for schools: a SaaS weakness can become an exam-week outage, data incident, and continuity problem a
- OpenSSF’s growth push meets CRA and AI security pressure - OpenSSF’s latest quarter is less a membership story than a sign of where open source security is moving: regulation, AI-assisted tooling, secure coding gui
- TrapDoor turns developer tools into credential traps - A cross-ecosystem campaign is abusing npm, PyPI, and Crates.io packages to steal developer secrets, with a newer twist: AI assistant instruction files as p
- Laravel-Lang compromise shows the risk inside release tags - A reported compromise of Laravel-Lang PHP packages used rewritten git tags and Composer autoload behavior to run a cross-platform credential stealer.
- TeamPCP shows how trusted developer updates fail - A reported TeamPCP wave hit VS Code, PyPI, and npm paths in one week. The lesson is release-level trust, not publisher badges.
- TrapDoor Shows How Package Malware Hunts Developer Secrets - Socket reports an active cross-registry campaign using npm, PyPI, and Crates.io packages to steal wallets, tokens, SSH keys, cloud credentials, and develop
- GitHub’s poisoned extension incident shows a quiet supply-chain gap - GitHub says a malicious third-party VS Code extension compromised an employee device and led to exfiltration of internal repositories. Customer repository
- Mini Shai-Hulud hits npm and CI trust paths - A fresh Mini Shai-Hulud campaign compromised npm packages, GitHub Actions, and PyPI entries, turning maintainer trust and CI secrets into the attack surfac
- Grafana breach shows how one CI token keeps access alive - Grafana says attackers downloaded code and internal GitHub data after the TanStack supply-chain attack. Production systems and Grafana Cloud were not affec
- Snyk’s AI Security Push Moves Closer to the Code - Snyk is betting that AI-generated code needs security controls inside developer workflows, backed by partners who can implement governance at enterprise sc
- TeamPCP Hits the Build Chain Again - SANS ISC reports a confirmed Checkmarx Jenkins plugin compromise and a new self-spreading Mini Shai-Hulud worm across npm and PyPI.
- Chainguard lowers RPM friction for regulated Linux teams - Chainguard’s RHEL 9/10 RPM support and FINOS membership point to a practical goal: make secure Linux modernization less disruptive for financial institutio
- OpenAI Breach Shows the Real Risk in Trusted Build Pipelines - OpenAI says two employee devices were breached in the TanStack-linked supply-chain campaign. The larger issue is how trusted CI/CD and package release path
- Supply-chain attacks become a leaderboard - TeamPCP and BreachForums are reportedly promoting a $1,000 contest for Shai-Hulud package compromises. The prize is small. The copycat incentive is the pro
- Composer token leak risk: update before CI logs bite - A GitHub token format change exposed a Composer error path that could print Actions tokens into CI logs. PHP teams should update Composer and review recent
- 100% package test coverage is the point, not the slogan - Chainguard says its OS tests every package automatically, with 100% package test coverage. The useful question is not whether that sounds good, but what it
- Supply Chain Attacks Expose the Real Test of Resiliency - Recent Trivy, axios, LiteLLM, and npm incidents show why cyber resiliency is an operating model: roles, rotation, pipeline trust, and exercises matter more
- TanStack package breach shows the limits of trusted publishing - Socket says 84 TanStack npm artifacts were published in compromised form. The bigger lesson is structural: if attackers can run inside CI, OIDC and provena
- PyPI Fixed High-Severity Access Control Bugs Found in a Warehouse Security Audit - A Trail of Bits audit of PyPI’s Warehouse reported two high-severity access-control issues and an OIDC Trusted Publishing replay edge case. PyPI says it fi