UnstucK 1470 Posted February 18, 2019 Report Share Posted February 18, 2019 Some network related data. Found nifty exploits, which I am not going to publish here for obvious legal reasons, but those are quite easy to guess & implement ... Just few used php pages with few parameters /party.php?qt=party-update&type=updateParty&hardware=PC&uid=UNSTUCK&pid=WHATEVER&searching=0&change=7&loadidx=1 /user.php?qt=user-getinfo&getinfo=1&hardware=PC&uid=UNSTUCK&language=english&timezoneOffset=1&ugc=1&rep=1 /emptyservers/?qt=emptyservers-client&dc=west+europe&it=0&searchT=0.0 (yay) /mp.php /nucleus-oauth.php /communities.php /prime.php (srsly ...) You will get gtfoed (really) if direct access without proper user agent, which is "Respawn" With said user agent, and more sniffing of network activity, you will find many other stuffs, some are used to track players, get player infos, get lobby infos... After few researches, you will be able to track lobbies, and force your player into a specific one (streamsnipping wtf), or even crash them. (I guess, at least it crashed for me ... maybe I was the only one affected but I doubt). "datacenters" { "a" { display "Salt Lake City" name "west us" host "107.182.233.168" port 37015 } "a" { display "Oregon - GCE 1" name "west us" host "104.198.102.93" port 37015 } "a" { display "Oregon - GCE 2" name "west us" host "104.198.101.253" port 37015 } "a" { display "Oregon 1" // AWS name "west us" host "52.40.240.176" port 37015 } "a" { display "Oregon 2" // AWS name "west us" host "52.42.44.79" port 37015 } "a" { display "St Louis" name "central us" host "209.239.121.82" port 37015 } "a" { display "Dallas" name "central us" host "63.251.239.123" port 37015 } "a" { display "Iowa - GCE 1" name "central us" host "130.211.193.234" port 37015 } "a" { display "Iowa - GCE 2" name "central us" host "104.197.17.180" port 37015 } "a" { display "Iowa - GCE 3" name "central us" host "104.197.136.10" port 37015 } "a" { display "Iowa - GCE 4" name "central us" host "104.197.42.178" port 37015 } "a" { display "New York" name "east us" host "107.150.147.67" port 37015 } "a" { display "South Carolina - GCE 1" name "east us" host "104.196.43.45" port 37015 } "a" { display "South Carolina - GCE 2" name "east us" host "35.196.104.104" port 37015 } "a" { display "South Carolina - GCE 3" name "east us" host "104.196.8.33" port 37015 } "a" { display "Virginia 1" // AWS name "east us" host "52.6.64.33" port 37015 } "a" { display "Virginia 2" // AWS name "east us" host "52.86.226.95" port 37015 } "a" { display "Sao Paulo" name "brazil south" host "177.54.152.31" port 37015 } "a" { display "Sao Paulo - GCE 1" name "brazil south" host "35.199.89.186" port 37015 } "a" { display "Sao Paulo - GCE 2" name "brazil south" host "35.199.73.98" port 37015 } "a" { display "Sao Paulo 1" // AWS name "brazil south" host "52.67.92.122" port 37015 } "a" { display "Sao Paulo 2" // AWS name "brazil south" host "52.67.31.204" port 37015 } "a" { display "London" name "west europe" host "217.147.89.101" port 37015 } "a" { display "Amsterdam" name "west europe" host "64.95.100.189" port 37015 } "a" { display "Belgium - GCE 1" name "west europe" host "146.148.120.92" port 37015 } "a" { display "Belgium - GCE 2" name "west europe" host "104.155.80.155" port 37015 } "a" { display "Belgium - GCE 3" name "west europe" host "130.211.51.110" port 37015 } "a" { display "Frankfurt 1" // AWS name "west europe" host "52.58.81.34" port 37015 } "a" { display "Frankfurt 2" // AWS name "west europe" host "52.59.121.244" port 37015 } "a" { display "Hong Kong" name "east asia" host "69.88.135.37" port 37015 } "a" { display "Taiwan - GCE 1" name "east asia" host "104.155.233.79" port 37015 } "a" { display "Taiwan - GCE 2" name "east asia" host "104.199.182.138" port 37015 } "a" { display "Singapore 1" name "southeast asia" host "72.5.161.228" port 37015 } "a" { display "Singapore - GCE 1" name "southeast asia" host "35.185.189.243" port 37015 } "a" { display "Singapore - GCE 2" name "southeast asia" host "35.185.189.104" port 37015 } "a" { display "Tokyo" name "japan west" host "161.202.72.179" port 37015 } "a" { display "Tokyo - GCE 1" name "japan west" host "104.198.82.36" port 37015 } "a" { display "Tokyo - GCE 2" name "japan west" host "104.198.82.65" port 37015 } "a" { display "Tokyo - GCE 3" name "japan west" host "104.198.88.214" port 37015 } "a" { display "Tokyo 1" // AWS name "japan west" host "52.69.157.152" port 37015 } "a" { display "Tokyo 2" // AWS name "japan west" host "52.197.77.217" port 37015 } "a" { display "Sydney" name "australia" host "27.50.72.162" port 37015 } "a" { display "Sydney - GCE 1" name "australia" host "35.197.166.13" port 37015 } "a" { display "Sydney - GCE 2" name "australia" host "35.201.19.135" port 37015 } "a" { display "Sydney 1" // AWS name "australia" host "52.63.136.88" port 37015 } "a" { display "Sydney 2" // AWS name "australia" host "52.62.160.212" port 37015 } } 1 Quote Link to comment https://royalhack.net/forums/topic/1629-apex-legends-network-data/ Share on other sites More sharing options...
UnstucK 1470 Posted February 18, 2019 Author Report Share Posted February 18, 2019 An UC member trolling shroud's lobby using those infos: Quote Link to comment https://royalhack.net/forums/topic/1629-apex-legends-network-data/#findComment-11043 Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.