Tabletop script: an npm worm steals developer credentials
A 60 minute tabletop script for a self replicating npm package compromise: injects, roles, and the questions that expose gaps in your response.
Deep dives, practical guides, and incident analyses from engineers who build Safeguard. No fluff, no vendor FUD — just what you need to ship secure software.
A 60 minute tabletop script for a self replicating npm package compromise: injects, roles, and the questions that expose gaps in your response.
A 45 minute tabletop script for a popular IDE extension that updates to a malicious version: find installs, contain laptops, rotate secrets and set policy.
A 45 minute tabletop script for dependency confusion: an internal package name appears on a public registry. Scope, containment and registry controls.
A 60 minute tabletop script for a compromised third-party GitHub Action: setup, four injects, discussion questions and what good answers look like.
Generated Java models use Swagger v2 annotations, and v3 annotations do not work as a swap. What that means for your dependency tree and your scanner.
Six supply chain quick wins a small SaaS team can finish in one week: lockfiles, scanning, branch rules, CI permissions and a vendor list.
A supply chain risk program office advises, hosts tools and templates, assesses suppliers, keeps the risk register and reports upward. Here is the scope.
Add dependency path, exposure window, artifact recall, credential rotation and external source sections to a postmortem template for supply chain events.
Maintainers whose package was compromised should publish what happened, which versions are bad, how to check, how to clean up and what changed in access.
Weekly insights on software supply chain security, delivered to your inbox.
Your first fix PR is minutes away.
No sales call required, even your agent can complete the purchase over MCP.