Player UUID does not match our cache Server hack

Discussion in 'Spigot Help' started by Kainzo, Feb 18, 2018.

Thread Status:
Not open for further replies.
  1. So basically,
    We had some users spoofing admin logins and giving them permissions etc.

    I'm unsure how to prevent it or stop it but I'm certain its happening. We're running latest BungeeCord and Spigot 1.12, has anyone seen this happen before?

    Code (Text):

        Line 42018: [20:36:41] [Server thread/INFO]: [Prism]: Player UUID for TimForReal does not match our cache! 442331b8-e085-337e-91c3-a91b0a0ff565 versus cache of 4fde0036-3c21-43c8-9b1f-6792e2aa099f
        Line 42240: [20:37:29] [Server thread/INFO]: [Prism]: Player UUID for Kainzo does not match our cache! f1af5742-e1f1-3311-9e50-bcec4613f64a versus cache of 004204f2-3c19-4446-9794-d09d1f015d59
        Line 42634: [20:38:44] [Server thread/INFO]: [Prism]: Player UUID for 8uo does not match our cache! f952e54f-08bd-3d12-a855-4d37becfe943 versus cache of 176f7e38-aa3e-4912-86f2-d61dec579cf1
      C:\Users\kainzo\Desktop\logs\2018-01-22-2.log (1 hit)
        Line 3392: [12:47:00] [Server thread/INFO]: [Prism]: Player UUID for Kainzo does not match our cache! 004204f2-3c19-4446-9794-d09d1f015d59 versus cache of f1af5742-e1f1-3311-9e50-bcec4613f64a
      C:\Users\kainzo\Desktop\logs\2018-02-02-3.log (1 hit)
        Line 21141: [20:20:20] [Server thread/INFO]: [Prism]: Player UUID for 8uo does not match our cache! 176f7e38-aa3e-4912-86f2-d61dec579cf1 versus cache of f952e54f-08bd-3d12-a855-4d37becfe943
     
  2. Installat a 2fa for admins
     
  3. The issue was resolved, it was a port forward issue.
     
    • Like Like x 1
    • Funny Funny x 1
Thread Status:
Not open for further replies.