MCU reverse engineering

Feeling/Faradix MCU Hack

General Questions About Microcontroller Firmware Extraction

---

• Is it safe to send payment to MikaTech ?

  If MikaTech was a bad company, you could find tons of bad reputations about its service on the internet over the 28 years history

  So, the answer is YES! We are good people.

  Why choose Mikatech, please click here to find out
  

  
  
• Can Mikatech break ics not listed on this site ?

  Different chip manufacturers have different part numbers, but the inner core of the chip can be make with same technology, it would be quite impossible to list all the part numbers where our technology can apply such as MYSON, STK, FEELING, ANALOG, FUJITSU, NOVATEK, LG/HYNDAI.
  
  Also by the advancing of the technology, everyday we gain more and more experience and develope new methods for reverse engineering for different Intergated Circuit parts. Full list of Integrated Circuit part numbers which is within our scope of capability is always getting bigger, please contact us to find out.

• Will my privacy be protected ?

  Mikatech Innovative Limited understands the importance of its clients' privacy. At the moment you contact Mikatech, the personal information from you will be put under protection by our management regulations which was developed by our years of practice, Mikatech uses these information to customize its service to you, it will never disclose these information to third party out of any reason.
  Every project we did, we will delete all the data, materials, and codes 60days after deliverig the files, it iwll protect us and protect your privacy.

• Is it legal to get service from Mikatech ?

  Yes, it is totally legal.
  Mikatech deliver its reverse engineering services for educational purposes only, it can be illegal to use above mentioned services in some coutries or regions, please check your local laws. Mikatech does not take any responsibility in relation to the use of above mentioned services that may be considered illegal.

  
  
• Secure Firmware Update Mechanisms and the MCU Lockbit Lock

  Firmware updates are essential for patching vulnerabilities, but they also introduce a potential attack vector. The MCU lockbit lock must ensure that only authenticated updates are installed. If an attacker can install malicious firmware, they can disable the lock. The update process typically involves reading the new firmware from a source. The MCU verifies a digital signature. If the signature is valid, the MCU programs the new firmware into flash. During this process, the read-out of an EEPROM processor is not allowed. But the attacker might try to inject a fake update. They could use a glitch to skip the signature check. Then they can dump flash and eeprom after booting their malicious firmware. Decapsulation and code recovery are unnecessary. The update mechanism itself must be protected. Many MCUs have a dedicated bootloader for updates. The bootloader is in a protected region. The MCU lockbit lock controls write access to that region. The lock prevents the bootloader from being overwritten. The update is performed in a secure environment. The MCU also checks the version number. It prevents rollback attacks. The attacker cannot install an older, vulnerable version. The read-out of an EEPROM processor of the version number is possible, but that doesn't help. Dump flash and eeprom of the update image is useless because it is encrypted. The update image is often encrypted with a device-specific key. The key is inside the MCU. The lockbit lock protects the key. So even if the attacker intercepts the update, they cannot decrypt it. They also cannot copy contents of crypto memory to get the key. Microcontroller reverse engineering of the update protocol might reveal flaws. But the protocol is usually standard. The MCU lockbit lock also enforces a secure channel for the update. The channel uses mutual authentication. The MCU authenticates the update server. The server authenticates the MCU. This prevents man-in-the-middle attacks. The update process also includes a fail-safe mechanism. If the update is interrupted, the MCU reverts to the previous version. This prevents bricking. The MCU lockbit lock ensures that the revert is also authenticated. The attacker cannot force a revert to an unauthenticated version. In summary, secure firmware update mechanisms are critical for maintaining the MCU lockbit lock. They prevent unauthorized code from disabling the lock. They protect against read-out, dump, decapsulation, copy, reverse engineering, and extraction by ensuring that only signed and encrypted firmware is installed.