Common attacks

Supply chain attack

An attack that reaches you through something you already trust and install, such as a code package, a tool or a provider.

In plain words

Instead of breaking into your kitchen, the attacker poisons an ingredient at the supplier. You cook with it without suspecting anything.

When it affects you

Anyone who builds with libraries, packages, command-line tools or AI tools. A single compromised dependency can end up inside your product or on your laptop.

What to do today

  1. Keep a short list of the packages and tools your product depends on, so you can check it when a warning appears.
  2. Update from official sources and be wary of unexpected new versions of tools you already use.
  3. Keep your keys out of the places where a compromised tool could read them.

← All termsNo. 29 / 32

Related on this site

News

Last reviewed: 2026-10-27. Written for non-experts. Check an advisory or your vendor for the details of a specific flaw.

Get the free runbooks

One-page security checklists for founders who build with AI. You get a confirmation email first, then the runbooks.

Send me the runbooks