Bypass Duplicate Tweet Protection using negative tweet id

Twitter doesn’t allow making tweets of same content in relatively near time frame.

But same content can be there in tweet which is made as reply to another tweet.

Attached below is the request made, when replying to a specific tweet.

POST /i/api/graphql/SECRET/CreateTweet HTTP/2
Cookie: SECRET
Content-Length: 981
X-Twitter-Client-Language: en
X-Csrf-Token: SECRET
X-Twitter-Auth-Type: OAuth2Session
X-Twitter-Active-User: yes
Authorization: Bearer SECRET
User-Agent: SECRET
Accept: */*
Sec-Gpc: 1
Accept-Language: en-US,en;q=0.7
Sec-Fetch-Site: same-origin
Sec-Fetch-Mode: cors
Sec-Fetch-Dest: empty
Accept-Encoding: gzip, deflate


The tweet to which we want to tweet as reply is decided based on param in_reply_to_tweet_id.

Here, comes my hacker mind voice telling me to try non-existent tweet id, negative tweet id, zero tweet id for the in_reply_to_tweet_id param.

To my surprise when the value of in_reply_to_tweet_id is zero or negative integer, It’s tweeted as a original tweet & not as a reply to tweet also bypassing the twitter duplicate content protection !

Duplicate tweets with same content made in reply to zero or negative tweet id’s

Made a nice report to twitter through H1 platform explaining the issue, unfortunately it was closed as informative as this doesn’t cause any considerable security impact to it’s users or the infrastructure, but is only a bypass to a security control placed on a feature.

Liked my article ? Follow me on twitter (@jayateerthaG) and medium for more content about bugbounty, Infosec, cybersecurity and hacking.



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store