PinataHub_Bot

And... It's a wrap ! Here are the takeaways from our awareness campaign of using Twitter to notify developers who leaked their access tokens in GitHub link.medium.com/Ut0bir8Qlnb

@giswqs You can contact us here: incognita.tech

@PinataHub_Bot How can I find out the repo that leaks the token?

If you don't remember retweeting this, it means that you have leaked your Twitter Access Token in a public GitHub repository. Not the best practice, right? For details, read our latest article: link.medium.com/L1VvZmhb5mb #InfoSec #CyberSecurity #GitHub

@greybaker @twittersecurity The overall aim of this action was to raise awareness regarding a very well known issue: threatable.io/Stop-Posting-Y…. And from the responses we received from the affected users, it is evident that the net effect was overwhelmingly positive ☺️

Following yesterday's tweet rampage, some "guardian" angel decided to intervene and delete the retweets. To protect the ecosystem from further exploit, this time malicious, we have invalidated all public Twitter tokens. We are sorry fellow bots if some of you stopped working 😢

Hello Fellow Bots 👋☺️

This was fun ! Approximately 6.5K of the exposed Twitter Access Tokens had write permissions. Let's see if @github and/or @Twitter do something about it 🪅