> For the complete documentation index, see [llms.txt](https://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/tutorial-52-npm-dependency-confusion-and-unclaimed-packages.md).

# Tutorial 52: NPM Dependency Confusion and Unclaimed Packages

{% hint style="info" %}
[**Book an audit with Zokyo**](https://www.zokyo.io/)
{% endhint %}

In modern software development, managing dependencies through package managers like **NPM** (Node Package Manager) has become a crucial part of building applications. These dependencies are external libraries or modules that developers use to avoid reinventing the wheel, speeding up the development process. However, relying on third-party packages also introduces new attack vectors, one of which is known as **Dependency Confusion**.

Dependency confusion occurs when an attacker exploits the difference between public and private package repositories by publishing a malicious package with the same name as a legitimate one, often with a higher version number. This can trick package managers into downloading and executing the malicious package instead of the intended one.

One specific variant of this issue involves **unclaimed NPM package names and scopes**. If a package or organizational scope is not claimed on the public NPM registry, a malicious actor can claim it and upload a package under the unclaimed name. Developers who use that package in their projects unknowingly run the risk of executing malicious code.

In this section, we'll dive deeper into how dependency confusion works and how unclaimed NPM packages or organizational scopes can be exploited to introduce malicious code into a developer’s environment.


---

# 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://zokyo-auditing-tutorials.gitbook.io/zokyo-tutorials/tutorial-52-npm-dependency-confusion-and-unclaimed-packages.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.