In reply to Peter Corless.

The infected image is the one in the RAM, not EEPROM. The check you are suggesting is for the image in the EEPROM. Is there a way to check the MD5 of the image in the RAM, what could be infected with this "sinful-knock" code?