# Introduction

NPM supply chain attacks target the software dependencies your applications and CI/CD pipelines rely on. These attacks often use new or updated packages, compromised maintainer accounts, or malicious install scripts to steal secrets, execute arbitrary code, or pivot deeper into your infrastructure.

Examples of such attacks include:

{% embed url="<https://www.stepsecurity.io/blog/sha1-hulud-the-second-coming-zapier-ens-domains-and-other-prominent-npm-packages-compromised>" %}

{% embed url="<https://www.stepsecurity.io/blog/supply-chain-security-alert-popular-nx-build-system-package-compromised-with-data-stealing-malware>" %}

{% embed url="<https://www.stepsecurity.io/blog/20-popular-npm-packages-compromised-chalk-debug-strip-ansi-color-convert-wrap-ansi>" %}

{% embed url="<https://www.stepsecurity.io/blog/ghostaction-campaign-over-3-000-secrets-stolen-through-malicious-github-workflows>" %}

The NPM Supply Chain Security capabilities in StepSecurity help you reduce this risk with a layered model built around three pillars:

Prevent – stop high risk dependencies and behaviors before they are introduced

Detect – continuously identify compromised packages and suspicious changes across your codebase

Respond – investigate incidents quickly and assess organization wide impact


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.stepsecurity.io/npm-supply-chain-security/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.