Spectator Hack Ban - Confirmed Working

[ImportBot]

Originally Posted by BriDawg*:

 

Hello all, I edit plugins and make insane limits for CMW. This was 100% confirmed today that this is working as we had someone logged in as a spectator who was immediately banned for a kill. This is to be added as a limit in Insane Limits plugin....

 

LumPenPacks' version with modifications:

---

Limit Evaluation

On Kill

 

First check

Expression

Code:

killer.Role == 1

Second check

Code

Code:

plugin.EABanPlayerWithMessage(EABanType.EA_GUID, EABanDuration.Permanent, killer.Name, 0, "Using Hacks - Bye (" + killer.Name + ")");
plugin.Log("Logs/SpectatorHacks.log", kill.Time.ToString() + " - " + killer.Name + " with GUID: " + killer.EAGuid + " was banned.");
plugin.PRoConChat(killer.Name + " with GUID: " + killer.EAGuid + " was banned.");
return false;

---

 

OP's original version:

---

 

Limit Evaluation: On Kill

First check: code

Code:

if(player.Role == 1)

return true;

 

return false;

 

second check disabled

 

limit action: EABan

EA Ban Type: EA_GUID

EA Ban Duration: Permanent

Our ban message: Permanent Ban for Use of Spectator Hack

---

 

You're servers will not be protected from the new spectator hack. I only release this because who knows how long it will take EA/DICE to figure out how to make FairFight catch it. Good night!

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Well, this is new. I'll update our systems later today. Thanks.

[ImportBot]

Originally Posted by dyn*:

 

Have seen two individuals so far take advantage of this but this morning is the first time soemone was caught using the limit above. The first one was 'able to use admin say / yell commands and move people at will' and 'kill while not being visible in player list'. I wasn't in game to witness the 'admin say / yell' and the logs do NOT indicate this behavior. I'm guessing it was autobalance that was moving people and it was just a knife message on screen... can't confirm though. The spectator was most definitely able to kill individuals, however.

 

Sabz from DICE did reply to one of the threads so it would appear they know it exists. Without the limit above cheaters would be able to empty the server and they do not appear to be getting banned by fair fight either.

 

See the reports of users seeing this in game:

 

http://battlelog.battlefield.com/bf4...0494087957206/

 

http://battlelog.battlefield.com/bf4...87020073475/2/

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Have seen two individuals so far take advantage of this but this morning is the first time soemone was caught using the limit above. The first one was 'able to use admin say / yell commands and move people at will' and 'kill while not being visible in player list'. I wasn't in game to witness the 'admin say / yell' and the logs do NOT indicate this behavior. I'm guessing it was autobalance that was moving people and it was just a knife message on screen... can't confirm though. The spectator was most definitely able to kill individuals, however.

 

Sabz from DICE did reply to one of the threads so it would appear they know it exists. Without the limit above cheaters would be able to empty the server and they do not appear to be getting banned by fair fight either.

 

See the reports of users seeing this in game:

 

http://battlelog.battlefield.com/bf4...0494087957206/

 

http://battlelog.battlefield.com/bf4...87020073475/2/

The admin say messages are simply their hack changing what the message looks like in chat, it doesn't have any special properties or functions, its just a regular chat message that has color changes on it. I've never seen anyone able to issue yells.

 

Also: 'Okay, today i saw one of these Cheaters, problem is, that guy was banned by FairFight few hours ago but still could use that spectator cheat few minutes ago.'

Fairfight doesn't block spectator joins? What?

 

Players in spectator are just invisible players it seems, probably the reason many hacks can tell who is spectating them and where. If they were able to just get their player operating normally while in spectator that would be insane.

Also, who is your friendly in spectator? Wouldn't everyone be your enemy? So it just becomes a free turkey shoot? This is really interesting.

[ImportBot]

Originally Posted by LumPenPacK*:

 

Hello all, I edit plugins and make insane limits for CMW. This was 100% confirmed today that this is working as we had someone logged in as a spectator who was immediately banned for a kill. This is to be added as a limit in Insane Limits plugin....

Thanks for this limit.

 

Here's a version that will also log the bans with date time.

 

Limit Evaluation

On Kill

 

First check

Expression

Code:

player.Role == 1

Second check

Code

Code:

plugin.EABanPlayerWithMessage(EABanType.EA_GUID, EABanDuration.Permanent, player.Name, 0, "Using Hacks - Bye (" + player.Name + ")");
plugin.Log("Logs/SpectatorHacks.log", kill.Time.ToString() + " - " + player.Name + " with GUID: " + player.EAGuid + " was banned.");
plugin.PRoConChat(player.Name + " with GUID: " + player.EAGuid + " was banned.");
return false;

[ImportBot]

Originally Posted by dyn*:

 

Ah! Didn't know that they were able to change the color of their text. That makes more sense. The yells / moves are likely unrelated.

 

My understanding of the cheaters being able to know where a spectator is, is the result of their hack knowing where everyone is. And spectators, I believe, report their position similar to a 'normal' player. So.. if two players are at the exact same coordinates (imagine a wall hack drawing boxes and knowing the location of all players), and they're at the coordinates of the cheater, then a spectator MUST be following the cheater.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Ah! Didn't know that they were able to change the color of their text. That makes more sense. The yells / moves are likely unrelated.

 

My understanding of the cheaters being able to know where a spectator is, is the result of their hack knowing where everyone is. And spectators, I believe, report their position similar to a 'normal' player. So.. if two players are at the exact same coordinates (imagine a wall hack drawing boxes and knowing the location of all players), and they're at the coordinates of the cheater, then a spectator MUST be following the cheater.

It would be so simple to just not send any spectator related information to players...they only know what the server sends them.

[ImportBot]

Originally Posted by IAF-SDS*:

 

There's already a spectator exploit that allows a banned person to come back as a spectator and cause trouble. That should be reason enough to restrict the spectator slots for only admins, which would also deal with preventing access to this spectator killing hack.

[ImportBot]

Originally Posted by veryDead*:

 

We only allow admins as spectators as well. There was no reason to leave them publicly available before this hack and definitely no reason now.

[ImportBot]

Originally Posted by LjMjollnir*:

 

i only open up a private spectator slot when i believe someone is hacking on the server.. but yeah its funny you see this guy going 30/0 and people complaining so i jump on spectator.. all of a sudden he's getting killed

[ImportBot]

Originally Posted by PapaCharlie9*:

 

I edited the OP to make both versions easier to find.

 

Are legit spectators allowed to type chat? If so, it would be easy to detect them typing in-game admin commands, like @kick or !kill. If that's what they are doing to cheat.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Just an FYI, the latest test version of AdKats has this built in for all servers.

[ImportBot]

Originally Posted by dyn*:

 

Are legit spectators allowed to type chat? If so, it would be easy to detect them typing in-game admin commands, like @kick or !kill. If that's what they are doing to cheat.

Spectators are allowed to type.

 

For this cheat they somehow spawn in and are able to freely roam the map.... literally the only thing you see is a floating gun 'running' around. lol! There is a video of it out there but can't find it now.

[ImportBot]

Originally Posted by Hutchew*:

 

Just an FYI, the latest test version of AdKats has this built in for all servers.

I don't see it. Where?

 

 

Hutchew

[ImportBot]

Originally Posted by ColColonCleaner*:

 

I don't see it. Where?

 

 

Hutchew

Not an option, it's hardcoded automatic. Any kill from spectator results in an immediate permaban for "Spectator Hack".

[ImportBot]

Originally Posted by ColColonCleaner*:

 

There's already a spectator exploit that allows a banned person to come back as a spectator and cause trouble. That should be reason enough to restrict the spectator slots for only admins, which would also deal with preventing access to this spectator killing hack.

Have they finally fixed it so you can have more than 15 players in the spectator slot list?

[ImportBot]

Originally Posted by IAF-SDS*:

 

I don't think so because none of the release notes show them changing it beyond the 15 allowed in the spectator slot list (but I haven't tested it for a couple months now).

[ImportBot]

Originally Posted by dyn*:

 

Also just snagged another player using the spectator hack this morning. It doesn't look like the server / client update Monday prevents the spectator hack though hopefully now they're logging it with FF and will ban them.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Also just snagged another player using the spectator hack this morning. It doesn't look like the server / client update Monday prevents the spectator hack though hopefully now they're logging it with FF and will ban them.

Not a single spectator hack ban on our servers so far...

 

Also no reports from players in the server of it happening, so it looks like they are just avoiding our servers?

[ImportBot]

Originally Posted by Hutchew*:

 

2 on ours using the IL limit, prior to adkats inclusion. None since. There have been reports of guns running around by themselves a few times, but no kills or bans.

 

Thanks for the heads up, CMW.

 

 

Hutchew

[ImportBot]

Originally Posted by ColColonCleaner*:

 

2 on ours using the IL limit, prior to adkats inclusion. None since. There have been reports of guns running around by themselves a few times, but no kills or bans.

 

Thanks for the heads up, CMW.

 

 

Hutchew

Did you keep your version on IL running during this time? If not, please do, if it detects something that AdKats isn't, let me know.

[ImportBot]

Originally Posted by Hutchew*:

 

Yes, I did, and yes, I will.

 

 

Hutchew

[ImportBot]

Originally Posted by CEBEP78*:

 

Thanks for this limit.

 

Here's a version that will also log the bans with date time.

 

Limit Evaluation

On Kill

 

First check

Expression

Code:

player.Role == 1

Second check

Code

Code:

plugin.EABanPlayerWithMessage(EABanType.EA_GUID, EABanDuration.Permanent, player.Name, 0, "Using Hacks - Bye (" + player.Name + ")");
plugin.Log("Logs/SpectatorHacks.log", kill.Time.ToString() + " - " + player.Name + " with GUID: " + player.EAGuid + " was banned.");
plugin.PRoConChat(player.Name + " with GUID: " + player.EAGuid + " was banned.");
return false;

Hello, say please, I got it right or no, if I itself (administrator) banned on a server ( through admin tools Rconnet ), that I will not be able to call at spectator?

[ImportBot]

Originally Posted by ColColonCleaner*:

 

Hello, say please, I got it right or no, if I itself (administrator) banned on a server ( through admin tools Rconnet ), that I will not be able to call at spectator?

Assuming you are asking if spectators are still allowed in the server after they are added to the ban list. I think that bug was fixed, but i'm not certain.

[ImportBot]

Originally Posted by CEBEP78*:

 

Hello, I banned itself, and tried to call at spectator, and calmly called and looked and wrote, and me not banned no kick

[ImportBot]

Originally Posted by LumPenPacK*:

 

Hello, say please, I got it right or no, if I itself (administrator) banned on a server ( through admin tools Rconnet ), that I will not be able to call at spectator?

You don't need to use this limit any more. This exploit has been fixed with the last server patch.

[ImportBot]

Originally Posted by ColColonCleaner*:

 

You don't need to use this limit any more. This exploit has been fixed with the last server patch.

He's not asking about the spectator hack, he's asking whether spectators can still join the server when they are in the banlist. Is that bug still there? I don't know whether it was fixed.

[ImportBot]

Originally Posted by LumPenPacK*:

 

He's not asking about the spectator hack, he's asking whether spectators can still join the server when they are in the banlist. Is that bug still there? I don't know whether it was fixed.

Uhh, to be honest I didn't understand his request (while drinking beer in a bar). I have no idea if this join bug has been fixed.

[ImportBot]

Originally Posted by CEBEP78*:

 

Uhh, to be honest I didn't understand his request (while drinking beer in a bar). I have no idea if this join bug has been fixed.

Yes, what is important me the player of banned permanent (or temporally), could not call at spectator .

[ImportBot]

Originally Posted by ty_ger07*:

 

Yes, what is important me the player of banned permanent (or temporally), could not call at spectator .

The easiest way to find out is to ban yourself or a friend and then try to join as a spectator.