I was on a similar project. OTOH it was sad to see so much code devoid of any art or even dignity. OTOH the original overseas coders were just trying to live their life, pay their bills, and giving the middle finger to capitalism. And I got to pay some bills, too.
I spent most of the early 2010s rewriting systems that had been outsourced to budget offshore coding shops in the 2000s. The software looked a lot like this: no code reuse, no system architecture, just copy pasta over and over.
The client didn't care about this of course, they weren't reading the code. What made them eventually fire the outsourcing shop and hire a guy like me was the bugs that wouldn't get fixed, and the request to fix a bug that caused three more bugs to get introduced.
I'd rewrite the software and it'd be functionally complete with 1/5th the code, and it'd be faster and have fewer bugs, as well as being maintainable.
I actually developed a sick enjoyment about reading through their code and understanding what they were doing. From what I can tell the guys were being put under pressure to produce code and close tickets. I would find big chunks of dead code that I think was to fool their SLOC counters.
Changing schema on one project required a change order and migrations submitted to DB folks so these guys discovered that mysql booleans were actually integers and they could stick whatever number they wanted in there, and ended up using existing boolean fields to store unrelated data! Of course this broke the original functionality in difficult to track down ways!