An unknown number of users experienced inconsistencies with the ToE lines within progress reports and the scheduled cloning. The issue started on UTC-5 24-01-18 11:20 and was proactively discovered 3.8 days (TTD) later by analysts who reported through our help desk [1] that there was an inconsistency in the reported number of lines of code. The problem was resolved in 2.1 days (TTF), resulting in a total window of exposure of 5.9 days (WOE) [2].
We were implementing a migration to reset inconsistencies in the Attacked lines. During this migration period, the data had some disparities and inconsistencies [3].
When the migration was completed, all inconsistencies were resolved [4].
The incident originated from intentional and necessary modifications to the production database during a migration. To prevent similar occurrences, I would like to point out that a call to enhance communication protocols, especially for significant migrations, is given. This underscores the relevance of notifying group chats before executing impactful migrations. FAILED_MIGRATION