Jump to content
Setting up an AI agent? ReverseEngineering.wiki skill (works from the command line, no configuration): https://reverseengineering.wiki/skill/rewiki/SKILL.md · setup for every client, including MCP: https://reverseengineering.wiki/llms.txt · REWiki:Connect

Tool:Enigma Protector

From ReverseEngineering.wiki
Tool
Vendor The Enigma Protector Developers Team
Platforms Windows
Website https://enigmaprotector.com
On this wiki Facts · Code · Notes · Topics

Commercial PE protector and licensing system (The Enigma Protector). This page covers recognition only: a build-stamp record 'ENIGMA' in the last section and fixed entry-point stubs.

Recognition only

How to tell that a PE is protected by The Enigma Protector; nothing about removing it.

From the Detect It Easy rule (Tool:Detect It Easy):

  • The last section (or the one before it, if the last has no raw data) contains 00 00 00 'ENIGMA' followed by a record: major byte, minor byte, then 16-bit year, month, day, hour, minute, second of the build (DIE prints these as the version, e.g. 3.x build date). Newer builds show the text Enigma Protector in that region (DIE reports 5.X).
  • 1.x: 'ENIGMA' 07 ' PROT' in the last section (v1.14), and the text Enigma protector v in .data for old builds.
  • x86 entry points include 60 E8 00 00 00 00 5D 81 ED .. .. .. .. (pushad, call $+5, pop ebp, sub ebp, imm) often followed by a jmp, plus several other variants; .NET files are tagged by the ENIGMA record in the first section.

See Technique:Identifying the toolchain of a binary, Tool:Themida, Tool:ASPack.