Declined 76561198054186815 (Db3aStFr0mD3aSt)

Scammer

|steamID: Db3aStFr0mD3aSt #69JefeSwag
|steamID32: STEAM_0:1:46960543
|steamID64: http://steamcommunity.com/profiles/76561198054186815
|customURL: http://steamcommunity.com/id/Db3
|steamrepURL: http://steamrep.com/profiles/76561198054186815







Recently this user made his backpack private. There were rumors he had sold his Burning Jefe to a marked scammer for a duped Scorching KE + ~30 buds in items/unusuals/rares. I never had seen the KE, but according to admins of the GHS server, they had seen him wearing it multiple times, for a few seconds before killing himself. The user made his backpack private BECAUSE of his dealings with scammers.

Here is the proof that I have discovered, finally.

He now has a 13th hour Killer exclusive as seen in these screenshots, below

http://steamcommunity.com/sharedfiles/filedetails/?id=121983578 (offering it to someone else)
http://steamcommunity.com/sharedfiles/filedetails/?id=121982781 (equipped)

BUT where did he get this unusual 13th hour KE, you might ask??? from this user http://steamcommunity.com/profiles/76561198053014083 (.SQ) who had a 13th hour KE on outpost. You can see in this screenshot, the two are friends. http://puu.sh/1QIYk/62d8906ae9... http://www.tf2outpost.com/trade/8038915 is the outpost trading PROVING that .SQ had the 13th KE. If you check his backpack now, it's gone and there is no one else on the history, this is because it has gone into Db3asts backpack.

The next question, WHY IS DB3AST HAVING THIS KE RELEVANT???? Well in .SQs backpack now lies a Scorching Killer Exclusive. http://www.tf2outpost.com/trade/8052204 obtained immediately after he traded the 13th hour away http://puu.sh/1QIXk/06ff222f9d

SR also has information from this user http://steamrep.com/profiles/76561198034860020 regarding a screenshot he gave me of his trade history. It shows Db3ast trading ellie (before he was marked) the scorching KE. If SR doesn't have this information I can provide it again.

Thread is locked, admins/mods will respond to it only from now on.

Moving.

This was dealt with previously, marking as rejected for the record.