“…To keep dormant in functional verification, hardware Trojan is usually triggered by some rare conditions, which is the so-called trigger condition. In the existing Trojan benchmarks, the trigger part and payload part are designed separately and the rare-triggered condition is implemented by a combination of several low-activity or low testability signals, which may be detected by logic analysis techniques [17,18,19,20]. The traditional digital Trojan design methodology can be divided into two categories, the first exploits the rare transition signals in the original design [6,7,9,15], and the second attempts to partition the Trojan circuit into smaller parts and stages [12,14].…”