Main / Executor detections
Code injected into a script
exec.script_injectionserverDefault: logCode was injected into one of your own scripts.
How ByteAC finds it
When the server starts, ByteAC reads the code of every script. Scripts with the ByteAC include report which game functions they call on their own player. A call to a function that appears nowhere in that script's files can only come from injected code.
Measured by the server. The player cannot fake or block it.
What the numbers mean
These are the values shown under the detection in the Threat feed and on the player page.
- resource
- The script the code was injected into.
- native
- The game function it called. A suffix :on or :off is the value it was set to.
Can also be caused by
Scripts that build function names at runtime (very rare).
What to do
Log first, then ban once you have checked it on your server.
The action (Off, Log, Kick, Ban) is set per detection on the Protection page. It only applies when Enforcement is on Custom. See Actions, modes & numbers.