Exclusive Interview with Tweepsect creator Andrey Petrov
Context: This post is a follow-up to my previous post: Twitter Phishing Scam: FIND OUT WHO STALKS YOUR TWITTER! THIS NEW APP ROCKS!
The following is an interview I conducted with Andrey Petrov, the creator of the Twitter application called Tweepsect. According to Petrov, his application was abused by scammers in the “StalkTrak” phishing scam on Twitter. The recent version of the “StalkTrak” application has copied the results page from Tweepsect to give it enough authenticity to fool unsuspecting Twitter users.
Satnam: You mentioned you encountered this scam a few weeks ago. How were you alerted to it?
I received a bunch of @mentions telling me that my app is sending people DMs. This wasn’t true, my app doesn’t do this, but it prompted me to investigate further.
I received an alert on SocialGrapple (another service I created after Tweepsect) that Tweepsect is being mentioned *a lot* more than usual on Twitter.
I received an alert on Google Analytics that I had unusually high amount of incoming traffic. The traffic increase began on the night of June 25th (it was in full throttle on the 26th).
Satnam: You mentioned that you alerted your users after they were proxying through TweepSect. Did you alert Twitter’s Trust and Safety team?
Andrey: Yes. First I made sure that he wasn’t exploiting something in Tweepsect. At first I didn’t know there was a fake OAuth page somewhere redirecting traffic, so I thought there might be an exploit in Tweepsect to spam DMs. As soon as I was sure it wasn’t my fault and I couldn’t do something about it, I contacted @twitter and @twitterapi.
https://twitter.com/shazow/status/85382389525774336
While waiting for a response, I noticed that the phishing scam was using Tweepsect as an endpoint exit to increase credibility (instead of showing a static results page like it does now), so I put up a big fat warning telling people that if they came in through StalkTrak that their login information was compromised and they should immediately change their password and revoke access to suspicious applications. The warning was up until yesterday.
I never heard back from Twitter, so later that night I emailed [redacted] personally. He replied to me within 7 minutes saying he forwarded my email to the appropriate team.
Satnam: How long did this last before the scammers got the hint?
Andrey: I noticed the first change in the attack after about 3 days since the beginning, that’s when he put up a static snapshot instead of redirecting to Tweepsect to circumvent my warning (which I put up on day 2 of the attack, as soon as I noticed it).
Satnam: Did you know about the newest version of the scam that’s using a static HTML page instead?
Andrey: Yes, this version has been active since Day 3 of the attack.
Satnam: Do you have any advice to Twitter application developers on how to detect scammers trying to proxy through their applications?
Andrey: Monitor your analytics (I use intelligence alerts for Google Analytics).
Satnam: Any additional thoughts you’d like to add?
Andrey: I wish Twitter would get back to me about their efforts on this. I’m still seeing spikes in traffic based on these attacks and I don’t know if they’re doing anything about it or not.
Here are some things I think Twitter should do:
Block all outgoing links to [redacted phishing url], especially in DMs
Check all accounts who sent DMs with links to that site, force password resets on those accounts (they’re probably compromised)
Revoke access to any suspicious apps that may have been granted in compromised accounts (no idea if this is the case)
It should be noted that the StalkTrak phishing scam is still spreading. While Andrey wasn’t able to provide me with any figures on just how many users might have fallen for this scam, considering the timeline he gave, I believe it’s safe to assume thousands of Twitter users were phished by this fake application.