Hello!
I am administering the server named Destiny-Server - Hallway Forts. I created this topic to share the IP Address / name of confirmed hackers playing on my server. Yesterday I managed to catch someone who has been making my server crash numerous times in the past month. He used other hacks as well, like aimbot etc...and he stated himself that if someone kicks him, the server will crash. Therefore I recommend adding him to global banlist.
Server admins can use this list to make their servers a bit more hacker-free. If you are a player and see your name and IP listed here, there is no going back. My server warns you every 5 minutes that hackers are not welcome. If you are caught, bear the consequences. People listed here are 100% confirmed hackers, or deserve banning for behavior (see reasons).
Most common location of banned people: South America, Russian Federation
Name: Padre Marcelo
Caught IP: 177.141.159.225
Reason: server crash hack, aimbot, wallhack
Severity: Threat (returned many times to crash the server)
Date: 2015/Jun/27
Name: Sykes
Caught IP: 179.217.26.11
Reason: aimbot
Severity: Normal
Date: 2015/Jun/29
Name: [faZe]TORC
Caught IP: 114.76.80.132
Reason: multihack
Severity: Severe
Date: 2015/Jun/30
Name: {Modz}Itz_Tony
Caught IP: 87.151.54.37
Reason: clan based on hacking, aimbot
Severity: Severe
Date: 2015/Jul/1
Name: {Modz}Itz_NooB
Caught IP: 87.151.59.213
Reason: clan based on hacking, aimbot
Severity: Severe
Date: 2015/Jul/1
Name: [xTr3m]and07
Caught IP: 78.242.12.197
Reason: multihack, server crash hack
Severity: Threat
Date: 2015/Jul/2
Name: Deuce0
Caught IP: 2.82.75.113
Reason: idiot, abusing votekick system
Severity: Normal
Date: 2015/Jul/06
Name: Deuce1
Caught IP: 85.243.65.82
Reason: idiot, abusing votekick system
Severity: Normal
Date: 2015/Jul/06
Name: HRomeu
Caught IP: 177.205.244.29 | 189.102.194.154
Reason: aimbot, ban evasion
Severity: Severe
Date: 2015/Jul/07
Name: 100 HAX
Caught IP: 91.156.151.170
Reason: multihack
Severity: Normal
Date: 2015/Jul/14
Name: RiukBR
Caught IP: 177.124.97.250
Reason: aimbot, wallhack
Severity: Normal
Date: 2015/Jul/15
Name: brbr zuera
Caught IP: 177.107.93.7
Reason: aimbot, wallhack
Severity: Normal
Date: 2015/Jul/15
Name: Gorlami
Caught IP: 177.99.145.24 | 179.186.52.239
Reason: server crash hack, ban evasion
Severity: Threat
Date: 2015/Jul/16
Name: (-_-)GhOsT(-_-)
Caught IP: 37.219.114.203
Reason: aimbot
Severity: Normal
Date: 2015/Jul/16
Name: AssER
Caught IP: 83.220.236.169 | 83.220.236.135 | 83.220.238.231
Reason: aimbot, ban evasion
Severity: Severe
Date: 2015/Jul/18
Name: TADJIK
Caught IP: 92.100.181.5
Reason: aimbot
Severity: Normal
Date: 2015/Jul/18
Name: kirill
Caught IP: 78.85.222.175
Reason: wallhack
Severity: Normal
Date: 2015/Jul/18
Name: Asassin'-'
Caught IP: 190.204.35.188
Reason: aimbot
Severity: Normal
Date: 2015/Jul/18
Name: Player
Caught IP: 79.136.188.223
Reason: aimbot
Severity: Normal
Date: 2015/Jul/18
Name: Th_Loren
Caught IP: 179.49.122.242
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: rtuci1020
Caught IP: 46.120.106.25
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: france
Caught IP: 79.25.59.201
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: Charley
Caught IP: 95.23.231.191
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: C 4
Caught IP: 198.8.80.68
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: lce
Caught IP: 104.156.228.198
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: Iava
Caught IP: 104.200.154.29
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: Awhnold
Caught IP: 104.200.151.57
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: Konher
Caught IP: 104.156.228.106
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: {M.T.M}nsgamess
Caught IP: 179.219.41.113
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: toriitti
Caught IP: 89.174.232.9
Reason: aimbot
Severity: Normal
Date: 2015/Jul/20
Name: Jazzy
Caught IP: 198.8.80.15
Reason: aimbot
Severity: Normal
Date: 2015/Jul/23
Name: Noone
Caught IP: 89.152.190.95
Reason: aimbot
Severity: Normal
Date: 2015/Jul/23
Name: versutus
Caught IP: 188.142.166.93
Reason: aimbot
Severity: Normal
Date: 2015/Jul/23
Name: Armageddon
Caught IP: 180.249.152.76
Reason: aimbot
Severity: Normal
Date: 2015/Jul/23
Name: pmichaelq30
Caught IP: 91.21.10.171
Reason: aimbot
Severity: Normal
Date: 2015/Jul/23
Name: 19hbK1YpuffX
Caught IP: 46.139.239.219
Reason: aimbot
Severity: Normal
Date: 2015/Jul/25
Confirmed hackers list
-
Deuce - Posts: 7
- Joined: Sun Jun 28, 2015 8:04 am
Last edited by MidnightWolf on Sat Jul 25, 2015 3:26 pm, edited 17 times in total.
-
Zekamalikyd
Modder
- Posts: 4219
- Joined: Mon Apr 01, 2013 3:40 pm
there is no global banlist
-
Deuce - Posts: 7
- Joined: Sun Jun 28, 2015 8:04 am
weird, what is this then?
http://blacklist.spadille.net/
my server keeps subscribing to this list. Doesn't really matter, the info is there for other server admins to ban vicious hackers listed here.
http://blacklist.spadille.net/
my server keeps subscribing to this list. Doesn't really matter, the info is there for other server admins to ban vicious hackers listed here.
-
Zekamalikyd
Modder
- Posts: 4219
- Joined: Mon Apr 01, 2013 3:40 pm
ha, minit
also as you can see it was last updated in 2013
also as you can see it was last updated in 2013
What Zeka means to say (in his not-so-straightforward attitude) is that the GBL is only used for very rare cases where a player is continuously harassing people, hacking on servers, and cheating in tournaments and there is "no choice" but to just disallow the player from ever connecting to a PySnip server.
-
Deuce - Posts: 7
- Joined: Sun Jun 28, 2015 8:04 am
Sure. I created this topic because I am really tired of people constantly hacking on my server, despite that every 5 minutes a Zero tolerance message warns them about the consequences. From now on everyone I catch hacking will get listed here for greater good.
-
Zekamalikyd
Modder
- Posts: 4219
- Joined: Mon Apr 01, 2013 3:40 pm
longbyte you ruined it they have to learn the hard way :(
Hey MidnightWolf, you still there m8?
Can you share the error that led server to crash? I might get someone to fix it.
Also, you should look into adding anti-cheat scripts, like aimbot2.py and banhammer.py.
Yours is a good server but sadly the only protection it has is (probably) just you and nowadays thats not enough.
Even if the GBL was still active, that'd not help much against the cheaters we have now.
Can you share the error that led server to crash? I might get someone to fix it.
Also, you should look into adding anti-cheat scripts, like aimbot2.py and banhammer.py.
Yours is a good server but sadly the only protection it has is (probably) just you and nowadays thats not enough.
Even if the GBL was still active, that'd not help much against the cheaters we have now.
Last edited by SnIpEr on Sat Aug 15, 2015 3:13 am, edited 2 times in total.
you forgot Universe_Gamer.
also haven't you realized how many people you HAVE caught aimbotting... that's a lot of people aimbotting on one server. think about how many MORE aimbotters there are that you haven't caught
also haven't you realized how many people you HAVE caught aimbotting... that's a lot of people aimbotting on one server. think about how many MORE aimbotters there are that you haven't caught
You should add the country of each hacker to the list aswell.
IGN: [BTK]LastKiller or DEV_CLIENT
Hey guys, here. I thought about this a lot longer to pyspades server, you are able to ask the clients to the MAC address. And let's say if the admin discovers *vandalism*, then kicks it only with a command on the server and stores it in a (.txt) extension to the mac-address that you just got fired as well as the (bans.txt).
=> Then, of course, to need to write a script, if possible.
Yes, this is a weak idea because anyone can change this address, but I think it would be a real reduction in headcount.
edit: Oh yes, and while I played today, I found this(have a look at chat):
=> Then, of course, to need to write a script, if possible.
Yes, this is a weak idea because anyone can change this address, but I think it would be a real reduction in headcount.
edit: Oh yes, and while I played today, I found this(have a look at chat):
-
Zekamalikyd
Modder
- Posts: 4219
- Joined: Mon Apr 01, 2013 3:40 pm
ByteBit wrote:You should add the country of each hacker to the list aswell.why is that necessary
LeFizzy wrote:Hey guys, here. I thought about this a lot longer to pyspades server, you are able to ask the clients to the MAC address. And let's say if the admin discovers *vandalism*, then kicks it only with a command on the server and stores it in a (.txt) extension to the mac-address that you just got fired as well as the (bans.txt).Hmm, that got me thinking about unique identifiers again..
=> Then, of course, to need to write a script, if possible.
Yes, this is a weak idea because anyone can change this address, but I think it would be a real reduction in headcount.
edit: Oh yes, and while I played today, I found this(have a look at chat):
There was some research a while ago on determining the model of a camera based on the noise pattern generated by the sensor. There are some more practical things than that, of course...
For example, you could make a hash out of a motherboard ID + disk drive ID and bind it to your username on server join and add a /lock feature to auto-login on a recognized hash and ask for a password on an unknown hash. When you get banned both your username and hash(es) are banned from the server.
Zekamalikyd wrote:umm, would just be interesting to know, huh?ByteBit wrote:You should add the country of each hacker to the list aswell.why is that necessary
IGN: [BTK]LastKiller or DEV_CLIENT
-
Zekamalikyd
Modder
- Posts: 4219
- Joined: Mon Apr 01, 2013 3:40 pm
why every hacker is either br, polish or any country in the world where idiots live and can afford computers and internet.
Who is online
Users browsing this forum: No registered users and 11 guests