I2C Address 0x00 not supposed to be showing up
Address 0 is a special address named the &quot;general call address.&quot; The basic idea is that any slave device on the bus can respond to this address. Not all devices actually implement this behavior, though. I've never tried to use it myself. I'm not sure how common it is for slaves to respond to it.
See section 3.1.13 of the I2C specification from NXP:
https://www.nxp.com/docs/en/user-guide/UM10204.pdf

3.1.13 General call address
The general call address is for addressing every device connected to the I2C-bus at the same time. However, if a
device does not need any of the data supplied within the general call
structure, it can ignore this address by not issuing an
acknowledgment. If a device does require data from a general call
address, it acknowledges this address and behave as a slave-receiver.
The master does not actually know how many devices acknowledged if one
or more devices respond. The second and following bytes are
acknowledged by every slave-receiver capable of handling this data. A
slave who cannot process one of these bytes must ignore it by
not-acknowledging. Again, if one or more slaves acknowledge, the
not-acknowledge will not be seen by the master. The meaning of the
general call address is always specified in the second byte (see
Figure 16).

I don't know why dropping the scanner would cause this to show up now if it didn't before. Perhaps the scanner has some settings that went back to factory defaults? Is it working as expected otherwise?