Adversaries may use junk code / dead code to obfuscate a malware’s functionality. Junk code is code that either does not execute, or if it does execute, does not change the functionality of the code. Junk code makes analysis more difficult and time-consuming, as the analyst steps through non-functional code instead of analyzing the main code. It also may hinder detections that rely on static code analysis due to the use of benign functionality, especially when combined with Compression or Software Packing.12 No-Operation (NOP) instructions are an example of dead code commonly used in x86 assembly language. They are commonly used as the 0x90 opcode. When NOPs are added to malware, the disassembler may show the NOP instructions, leading to the analyst needing to step through them.3 The use of junk / dead code insertion is distinct from Binary Padding because the purpose is to obfuscate the functionality of the code, rather than simply to change the malware’s signature.
- ReasonLabs
- ReasonLabs Cyberpedia Junk Code
- ReasonLabs
Groups using this technique
| Group | Name | Country |
|---|---|---|
| grp_g0129 | Mustang Panda | China |
| grp_g0082 | APT38 | DPRK |
| grp_g0046 | FIN7 | — |
| grp_g0099 | APT-C-36 | — |
| grp_g0047 | Gamaredon Group | Russia |
| grp_g0094 | Kimsuky | DPRK |
| grp_g0050 | APT32 | Vietnam |
Claims
No public claim points at this technique yet.
Auto-ingested and not human-reviewed; confidence and validity read by citation.