Loki - The Dependency Confusion vulnerability scanner and

项目说明

<di="center">
<p> <img src=" alt="Loki" width="100"/> </p>

</div>

<di="center">
<a href=" src=" alt="npm "/></a>
<a href=" src=" alt="downloads"/></a>
<a href=" src=" alt="Known "/></a>
<a href="./SECURITY.md"><img src=" alt="Responsible Disclosure Policy" /></a>
<a href="./LICENSE"><img src=" alt="License" /></a>
</div>

About

Loki helps to identify NodeJS projects that are to Dependency Confusion supply chain attacks.

Loki has been created with the goal of helping de to scan their projects and identifying possible attack that could take ad of in the dependency supply chain.

Loki is a god in Norse mithology. Among other powers, he is an adept shapeshifter and people impersonator.

Disclaimer

Loki is a defensive tool. The attack mode simply inserts a payload opening a listener service to allow the de to connect to the compromised dependency with the sole purpose of showing the impact of a misconfigured module.

When may a Dependency Confusion supply chain attack happen?

Dependency Confusion attacks may occur if:
* A company uses a hybrid approach to download their dependencies from both their internal repositories and public repositories.
* A de has not properly configured a project's npm registry. A lightweight private npm proxy registry such as can be configured.
* A typo in the name of a dependency may lead to an untrusted dependency being downloaded from the wrong repository. Better known as typosquatting.
* The specified of the wanted dependency in the package.json file allows downloading newer . Having such "loki-this-dependency-does-not-exist": "^1.1.0" dependency allows downloading the latest of the dependency from 1.1.0 up to, but not including, 2.0.0. Similar interaction happens with tilde ~. If a project has a hybrid setup, if the public repository such as npmjs.org contains a higher compared with the private repository, the public one will be downloaded.
* A package name has a different import name. If a junior de, by reading the code, expects the installation name of a package used in the repository is the same as the import. As an example, we can have a look at the Python image processing library OpenCV whose import name is cv2 but the correct pip install command to install it is pip install openc.

Mitigation

* Strict internal dependency management by configuring the private repository to never go beyond (access the public realm) when it does not contain the wanted dependency. As pre said, is a nice tool to achieve this.
* Using dependency scopes or namespaces to avoid typosquatting.
* Using pinning. This technique does not index whether your current dependencies have been compromised, but it will prevent from downloading newer untrusted .
* Integrity checking.

Features

* Dependency scanning
* npmjs package publishing
* Configurable reverse shell generation
* Payload injection in projects
* Attack mode (PoC after successful payload injection)
* Inspector mode (display hash of the commit that introduced the package if the directory to scan is a git repository)

Usage

Prerequisite

To use this tool, it is expected that you have the following a in your en:

Node.js and npm in stable and recent

The Git binary a in your path

If downloaded from the repository:

Using npx:

Options

Contributing

Contributing Guide

License

MIT

Credits

Big thanks to the Snyk team for their work on snync as Loki uses a modified of their tool.

项目信息

开发语言：JavaScript

Star 数：37

技术要点

该项目属于安全软件方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕The Dependency Confusion vulnerability scanner and autoexploitation tool to help identifying and mitigating supply chain attacks展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

从技术实现角度看，此类项目的核心在于对底层原理的深入理解与工程化落地。开发者在研究过程中可以结合官方文档与社区讨论，梳理项目的初始化流程、核心模块职责与数据流转，逐步掌握其中的技术细节与设计思路。

使用与学习建议

1. 下载源码压缩包，解压到本地环境。

2. 根据项目类型准备对应的运行环境与依赖。

3. 按照 README 中的步骤完成配置与部署。

4. 在隔离的测试环境中运行验证，避免影响生产系统。

免责声明

本资源来源于开源社区，仅供安全研究、技术学习与合法授权范围内的攻防演练使用，请勿用于任何非法或侵害他人权益的用途。使用本项目产生的一切后果由使用者自行承担。