fix: detect TikTok SlardarWAF to prevent false positives#2958
Open
guhyun9454 wants to merge 1 commit into
Open
fix: detect TikTok SlardarWAF to prevent false positives#2958guhyun9454 wants to merge 1 commit into
guhyun9454 wants to merge 1 commit into
Conversation
TikTok responds to Python requests (HTTP/1.1) with a SlardarWAF challenge page for all requests regardless of account existence. Without this fingerprint, Sherlock incorrectly marks all TikTok queries as CLAIMED. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
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.
Summary
requests(HTTP/1.1) with a SlardarWAF bot-challenge page for all profile requests, regardless of whether the account actually existsstatusCode:10221, so Sherlock incorrectly marks every TikTok query as CLAIMED (false positive)SlardarWAFtoWAFHitMsgscorrectly classifies these responses asQueryStatus.WAFinsteadRoot cause
TikTok performs TLS/HTTP fingerprinting and serves a ByteDance SlardarWAF challenge to non-browser clients.
curl(HTTP/2) bypasses it and returns the correctstatusCodein the JSON payload; Pythonrequests(HTTP/1.1) does not.Verified with:
Test plan
sherlock <nonexistent_tiktok_username> --site TikTok→ should showWAF(notCLAIMED)sherlock <existing_tiktok_username> --site TikTok→ should showWAF(bot detection active for all requests)