I've reproduced that problem.
It would seems it's an error in wireshark mysql packet decoding.
0xfdc40000 => byte 0xfd indicate that length is 3 bytes little endian encoded 0xc40000 = 196
problem is that wireshark use 4 bytes:
0xc400000c => 201326788

wireshark PR submitted (https://gitlab.com/wireshark/wireshark/-/merge_requests/6239)

Hi Diego, I think it is also something not expected that using 3 bytes to encode an integer when 1 byte is enough? Quoting the MySQL's document here (link: https://dev.mysql.com/doc/internals/en/integer.html):

"An integer that consumes 1, 3, 4, or 9 bytes, depending on its numeric value
To convert a number value into a length-encoded integer:
If the value is < 251, it is stored as a 1-byte integer."

This may break some system that adheres strictly to the above rules. It is possible to fix this on the connector side, too? seems only the new releases suffer from this issue...

I asked myself this question during the implementation and this trick permit some optimization, but allright, predictability/ensure compatibility is a better argument.
It will be part of 3.0.4 release

Thanks Diego!