fix: remove npm due to Cloudflare WAF blocking all requests#2841
Open
juliosuas wants to merge 1 commit intosherlock-project:masterfrom
Open
fix: remove npm due to Cloudflare WAF blocking all requests#2841juliosuas wants to merge 1 commit intosherlock-project:masterfrom
juliosuas wants to merge 1 commit intosherlock-project:masterfrom
Conversation
npm (npmjs.com) now returns HTTP 403 for all profile requests due to Cloudflare WAF challenge protection. This causes consistent false negatives since sherlock's status_code detection treats non-2xx responses as 'not found'. Both existing and non-existing usernames receive identical 403 responses, making reliable detection impossible without browser-level challenge solving. Fixes sherlock-project#2628
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
npm (npmjs.com) now uses Cloudflare WAF challenge protection that returns HTTP 403 for all profile page requests, regardless of whether the username exists. This causes consistent false negatives — Sherlock can never detect an npm profile.
Both existing (
~kennethsweezy) and non-existing usernames receive identical 403 responses withcf-mitigated: challengeheaders.Fix
Remove the
npmentry fromdata.json. The Cloudflare challenge requires browser-level JavaScript execution that can't be solved with simple HTTP requests.This is the same pattern as 1337x and Giphy (see #2835).
Fixes #2628