Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Detect potential dependency confusion and typo squatting #630

Open
arewm opened this issue Nov 15, 2024 · 0 comments
Open

Detect potential dependency confusion and typo squatting #630

arewm opened this issue Nov 15, 2024 · 0 comments

Comments

@arewm
Copy link

arewm commented Nov 15, 2024

Malicious packages which are uploaded with a similar name to other known-good packages (i.e. typosquatting) is a challenge for supply chain without a good solution that I am aware of. It would be interesting to see if malcontent could catch potential typosquatting attacks as these are often named similarly not not exactly the same. There are two potential modes of operation where I see these potentially malicious packages being introduced:

  • A dependency disappears from the reference sources and a similar one appears in the new sources (dependency replacement)
  • A new dependency is added which is named similar to an already used dependency (i.e. a change in a recursive dependency)

These packages may be versioned similarly but might not be.

@arewm arewm changed the title Detect potential dependency typo squatting Detect potential dependency confusion and typo squatting Nov 19, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant