Insights regarding the recent detection/ban wave

Discussion in 'Announcements and News' started by Homie, Aug 9, 2024.

  1. Join our Telegram group and stay connected with the community!
    JOIN
By Homie on Aug 9, 2024 at 12:45 AM
  1. Homie

    Homie Super Gorilla Staff Member Super Moderator Moderator

    Joined:
    Nov 9, 2020
    Messages:
    11,187
    Likes Received:
    12,178
    Dear Customers,

    on August 1st, a banwave on Call of Duty was applied. At first, we suspected the spoofer as the cause of the banwave. We analysed a lot of our collected data and found unusual patterns which made us dig deeper into Ricochet.
    Due to the seriousness of this topic, many false accusations and to improve our transparency, we wanted to show you some insights on what we have done the past week.

    This shows that quick and accurate analysis of available data and sophisticated reverse engineering have to go hand in hand. We aim to improve our procedures continuously and while we unfortunately could not prevent a detection in advance this time, our precise analysis allowed us to make the cheat undetected again quickly, while avoiding dangerous trial-and-error methods. Our internal tools and algorithms have been improved in the process.

    We have an automated system in place to actively monitor game bans, which we can use to correlate game bans and cheat usage. We are using this info to gather insight on for example cheat usage and also to identify issues on ban-waves.
    Even though we are constantly monitoring the cheat and spoofer, it sometimes takes some days until we have all needed information for our analytics.

    Right after the banwave we illustrated the bans which looked like the following:
    [​IMG]
    Our assumption therefore was that the spoofer was detected. But due to the nature of this statistics it is not reliable and not up to date.

    After some days the statistics looked a bit different.
    [​IMG]

    Therefore, we were first focused on the spoofer but switched over to the cheat after initial analysis. We found that there was a detection that triggered rather infrequently, thus meaning it was not logged by us during routine tests and did not affect all users.

    To counter these kinds of detections, we restructured our internal tools to cover those scenarios in the future.

    EngineOwning for Call of Duty: Modern Warfare III and Warzone should be back up shortly and stronger than ever. We thank you for your continued loyalty and trust.

    We would not be here without you,
    Your Team EngineOwning
     

Comments

Discussion in 'Announcements and News' started by Homie, Aug 9, 2024.

Share This Page