STEAM GROUP
TF2 Outpost by Fanbyte
Membership by invitation only
STEAM GROUP
TF2 Outpost by Fanbyte
3,660
IN-GAME
30,454
ONLINE
Founded
7 August, 2011
Language
English
zemnmez 4 Aug, 2014 @ 11:57am
Regarding Anti-phishing measures
Sneeza posted recently that we had implemented some measures to mitigate phishing attacks launched on our users via TF2 Outpost, and many of you have seen reduced phishing attempts since it was implemented.

The mode of operation for these phishing bots is pretty simple:

  1. Load front page of tf2outpost.com et al
  2. Scan for 64 bit steamIDs (just 17 digit numbers -- /\d{17}/g)
  3. Add these people -- some bots do this by loading steam://addfriend[...] URLs, others (I hope) are more sophisticated than this.
  4. Bot periodically, or someone manually copies and pastes (yes really) some kind of link that looks like steamhost.cn/steamcommunity_com but isn't.
  5. The not-really-steamcommunity website records your login details when you type them in.
  6. They do what they want with your account.

After some discussion we isolated that phishing on Steam is difficult to solve because we don't have data on the activities on users like Valve do.

Solving this problem, then means we need to measure how many people someone is attempting to add.

Our solution works like this:

  • Where we would normally have SteamIDs, we have URLs that pass through to the steamID, for example my steamcommunity link now goes to: http://www.tf2outpost.com/user/4/resolve/community which uses my Outpost user ID and not my 64 bit SteamID. The actual redirect is done through a Location header, which shouldn't confuse any good HTTP client and shouldn't impact our SEO.
  • We record hits on a per-IP basis on these pass-through links.
  • If someone makes too many requests for SteamIDs, we lock them out.

If any other website want to pick up the baton and implement these measures, I'm sure we'd see a reduction in phishing activity.
Last edited by Sneeza™; 4 Aug, 2014 @ 12:09pm
< >
Showing 1-15 of 15 comments
tomato juice 4 Aug, 2014 @ 12:09pm 
1rd
Thanks.
HusKy 5 Aug, 2014 @ 2:25am 
I have posted this elsewhere but you should protect trade offer URLs as well.
NiceTraderJoe 5 Aug, 2014 @ 7:57am 
AWESOME!! I really like the automated "monitor and react" method of dealing with scanning bots.

To help harden the countermeasure effectiveness, could these be implemented:

  • Have seller option "require user Steam login before showing 'resolve' link" (further prevent fresh bots from ever viewing my Steam ID while maintaining SEO for my post contents)
  • Expand 'resolve' link monitoring to "logged in by Steam" users and block specific users, not just IP addresses

These two measures should help harden the phishing bot countermeasures by:

  • Not exposing 'resolves' to fresh collector bots
  • Prevent proxy server hopping by collector bots even if they are logged in by Steam to beat IP bans
  • Further increases the complexity of successful collector bot code (disincentive to create smarter bots)
  • Give sellers more active options to combat phishing

Thanks again for the excellently effective efforts!! ^_^

Joe.
Sunny! 5 Aug, 2014 @ 8:08am 
Originally posted by NiceTraderJoe:
AWESOME!! I really like the automated "monitor and react" method of dealing with scanning bots.

To help harden the countermeasure effectiveness, could these be implemented:

  • Have seller option "require user Steam login before showing 'resolve' link" (further prevent fresh bots from ever viewing my Steam ID while maintaining SEO for my post contents)
  • Expand 'resolve' link monitoring to "logged in by Steam" users and block specific users, not just IP addresses

These two measures should help harden the phishing bot countermeasures by:

  • Not exposing 'resolves' to fresh collector bots
  • Prevent proxy server hopping by collector bots even if they are logged in by Steam to beat IP bans
  • Further increases the complexity of successful collector bot code (disincentive to create smarter bots)
  • Give sellers more active options to combat phishing

Thanks again for the excellently effective efforts!! ^_^

Joe.
Unlike the others you suggested, these actually may work! But this is up to the admins.
Sunny! 5 Aug, 2014 @ 8:10am 
Originally posted by HusKy:
I have posted this elsewhere but you should protect trade offer URLs as well.
People use offer URLs for Backpack.tf price suggestions as proof. I would think that the admins won't do that.
Originally posted by NiceTraderJoe:
AWESOME!! I really like the automated "monitor and react" method of dealing with scanning bots.

To help harden the countermeasure effectiveness, could these be implemented:

  • Have seller option "require user Steam login before showing 'resolve' link" (further prevent fresh bots from ever viewing my Steam ID while maintaining SEO for my post contents)
  • Expand 'resolve' link monitoring to "logged in by Steam" users and block specific users, not just IP addresses

These two measures should help harden the phishing bot countermeasures by:

  • Not exposing 'resolves' to fresh collector bots
  • Prevent proxy server hopping by collector bots even if they are logged in by Steam to beat IP bans
  • Further increases the complexity of successful collector bot code (disincentive to create smarter bots)
  • Give sellers more active options to combat phishing

Thanks again for the excellently effective efforts!! ^_^

Joe.

IDs are hidden from all users, it doesn't matter whether they are logged in or not (and it should not matter, phishers do it both ways). Restricting it to logged in users will diminish its effectiveness...

Proxy detection is a totally different beast.

Originally posted by •L•R• MrOmNomNom3:
Originally posted by HusKy:
I have posted this elsewhere but you should protect trade offer URLs as well.
People use offer URLs for Backpack.tf price suggestions as proof. I would think that the admins won't do that.

Trade Offer links have nothing to do with bp.tf
HusKy 5 Aug, 2014 @ 11:34am 
Originally posted by wat:
Proxy detection is a totally different beast.

Yep. I have hinted this on bazaar and the admin told me they already bypassed the resolver by switching proxies.
zemnmez 5 Aug, 2014 @ 11:35am 
Originally posted by HusKy:
I have posted this elsewhere but you should protect trade offer URLs as well.

Hm. That's a good idea.

Originally posted by HusKy:
Originally posted by wat:
Proxy detection is a totally different beast.

Yep. I have hinted this on bazaar and the admin told me they already bypassed the resolver by switching proxies.

This was discussed, but it was thought that it would be uneconomical to do this at any real scale.
Last edited by zemnmez; 5 Aug, 2014 @ 12:19pm
HusKy 5 Aug, 2014 @ 11:37am 
Originally posted by Zemnmez:
Originally posted by HusKy:
I have posted this elsewhere but you should protect trade offer URLs as well.

Hm. That's a good idea.

Related: https://steamhost.cn/steamcommunity_com/groups/tf2outpost/discussions/0/38596747823331166/#c38596747828890194
zemnmez 5 Aug, 2014 @ 11:47am 
Yeah, I know how to convert 32 bit IDs to 64 bit.
Last edited by zemnmez; 5 Aug, 2014 @ 12:19pm
Sunny! 5 Aug, 2014 @ 12:40pm 
Originally posted by wat:
Originally posted by NiceTraderJoe:
AWESOME!! I really like the automated "monitor and react" method of dealing with scanning bots.

To help harden the countermeasure effectiveness, could these be implemented:

  • Have seller option "require user Steam login before showing 'resolve' link" (further prevent fresh bots from ever viewing my Steam ID while maintaining SEO for my post contents)
  • Expand 'resolve' link monitoring to "logged in by Steam" users and block specific users, not just IP addresses

These two measures should help harden the phishing bot countermeasures by:

  • Not exposing 'resolves' to fresh collector bots
  • Prevent proxy server hopping by collector bots even if they are logged in by Steam to beat IP bans
  • Further increases the complexity of successful collector bot code (disincentive to create smarter bots)
  • Give sellers more active options to combat phishing

Thanks again for the excellently effective efforts!! ^_^

Joe.

IDs are hidden from all users, it doesn't matter whether they are logged in or not (and it should not matter, phishers do it both ways). Restricting it to logged in users will diminish its effectiveness...

Proxy detection is a totally different beast.

Originally posted by •L•R• MrOmNomNom3:
People use offer URLs for Backpack.tf price suggestions as proof. I would think that the admins won't do that.

Trade Offer links have nothing to do with bp.tf
Ah, sorry. I didn't get much sleep last night. Also, the bots can still view the Profile ID using the User Outpost ID. So I would presume if we lifted the Private Profile rule or have our Outpost ID URL different to our Steam ID URL, the asshole who made these can program the bots to search for us on SteamRep.

So that could work in my opinion. But for a temp solution.
I don't give a shit anyway. They give me a way to let out my frustrations. I pretty much do this:
Bot: hey mate
Bot: blah blah blah
Bot: blah blah blah spam.fakesteampage.banana
Me: (Imagine the most insulting remark you can think of here.)
Me: (Insert sarcastic remark.)
Me: (Allan Please Add Sarcastic Remark.)
Me: I used to be a adventurer like you, but then I took a arrow to the knee. Allan Please Add Funnier Overused.
Me: Allan Please Add Insult.


I could just fuck about with the bots for days. The best part? They don't respond back!
How should I end this? I know! With a list of my current Steam emoticons! :csgob: :longhaul: :apteka: :crystal: Yes, I know that is a pathetic list.
HusKy 5 Aug, 2014 @ 12:53pm 
Originally posted by Zemnmez:
Yeah, I know how to convert 32 bit IDs to 64 bit.

These are "partner IDs". I haven't really found and explanation for them anywhere or why is Valve using them. (Probably because Javascript can't handle the "7656..." type properly.)
« Kreecher » 6 Aug, 2014 @ 6:18pm 
thank you for this. i was really getting upset wit hthe amount of phshing attempts i was getting on a daily basis ... i would say that i get almost no phishing bot adds anymore (at least not from outpost) .... so thank you.
< >
Showing 1-15 of 15 comments
Per page: 1530 50

Date Posted: 4 Aug, 2014 @ 11:57am
Posts: 15