confused - Tool to check for dependency confusion vulnerabili

项目说明

Confused

A tool for checking for lingering free namespaces for private package names referenced in dependency configuration
for Python (pypi) requirements.txt, Ja (npm) package.json, PHP (composer) composer.json or M) pom.xml.

What is this all about?

On 9th of February 2021, a security researcher Alex Birsan published an article
that touched different resol flaws in dependency management tools present in multiple programming language ecosystems.

Microsoft released a whitepaper
describing ways to mitigate the impact, while the root cause still remains.

Interpreting the tool output

confused simply reads through a dependency definition file of an application and checks the public package repositories
for each dependency entry in that file. It will proceed to report all the package names that are not found in the public
repositories - a state that implies that a package might be to this kind of attack, while this has not
yet been exploited.

This howe't mean that an application isn't already being actively exploited. If you know your software is using
private package repositories, you should ensure that the namespaces for your private packages have been claimed by a
trusted party (typically yourself or your company).

Known false positives

Some packaging ecosystems like npm have a concept called "scopes" that can be either private or public. In short it means
a namespace that has an upper level - the scope. The scopes are not inherently publicly, which means that confused
cannot reliably detect if it has been claimed. If your application uses scoped package names, you should ensure that a
trusted party has claimed the scope name in the public repositories.

Installation

_or_

_or_

Usage

Example

Python (PyPI)

Ja (npm)

Maven (mvn)

Ruby (rubygems)

项目信息

开发语言：Go

Star 数：790

技术要点

该项目属于漏洞知识库方向的开源资源，代码结构清晰，适合安全研究人员学习参考。项目围绕Tool to check for dependency confusion vulnerabilities in multiple package management systems展开，提供了可运行的实现，对理解相关安全机制、工具原理与攻防技术具有较高的研究价值。

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

使用与学习建议

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

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

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

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

免责声明

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