> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/dependency-chains/appsec-cicd-160.md).

# Internal NPM package is not scoped

## Rule Details

|                       |                   |
| --------------------- | ----------------- |
| Cortex AppSec Rule ID | APPSEC\_CICD\_160 |
| Category              | Dependency Chains |
| Severity              | MEDIUM            |

## Impact

Any third party can publish unscoped packages to the public NPM registry. If the organization does not own the names of the internal packages on the public registry, attackers could potentially upload malicious packages to the registry with identical or similar names, hoping that clients who have not configured their '.npmrc' files to fetch packages from the internal registry will mistakenly download them. Scoping packages in NPM can help protect against "Dependency Confusion" and Typosquatting attacks. This is because each NPM user/organization has their own scope, and only the user/organization's owner can add packages to that scope. As a result, third parties cannot take the package name.

## Recommended Solution - Buildtime

Reduce the risk of **Dependency Confusion** and **Typosquatting** attacks on your internal NPM packages by using organization-controlled scopes on the public NPM registry. This will ensure that any packages fetched by your internal clients are legitimate versions under your organization’s control. To upload a scoped package to **npmjs.com** you need to own an NPM organization with the same name as the scope. Then, edit the name field in the `package.json` file to `@scopename/packagename` and publish the package. Reinstall the package on all repositories that depend on it.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://cortex-docs.paloaltonetworks.com/appsec-rules/ci-cd-security/dependency-chains/appsec-cicd-160.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.