Deobfuscation

This page documents the deobfuscation command.

LD can deobfuscate Lua files by using the /deobfuscatecommand in the DMs of the bot.

Once you have used the command, upload a file to the bot and press the Deobfuscatebutton and wait for the bot to respond. The bot will automatically determine the obfuscator.

Deobfuscation Options

Deobfuscation options specify the output style of the deobfuscation. Please not that full source code is NOT available through LD. LD will output bytecode or a listing of the instructions. The bytecode can usually be decompiled with a decompiler, but the decompiled result will be messy and not have local variable names or comments.

Bytecode Dump

The output will be dumped as a Lua 5.1 bytecode (.luac) file. This file can be executed or it can be ran through a decompiler such as unluac or luadec.

Formatted Listing

The output will be formatted as a list of instructions, functions, and constants.

Supported Obfuscators

LD's deobfuscator is a generic deobfuscator that uses code samples from open-source projects to attempt to identify and reverse obfuscation. LD does not specifically target any obfuscators, but it uses algorithms designed to reverse obfuscation that utilizes code from the following projects:

Rerubi: https://github.com/Rerumu/Rerubi FiOne: https://github.com/Rerumu/FiOne The following obfuscators have been tested by community members and stated to be supported:

  • IronBrew 2.7.0

  • IronBrew 2.7.1

  • IronBrew 2.7.2

  • AztupBrew 2.7.2

  • PSU 4.0.A

  • PSU 4.5.A

  • MoonSec V2

  • MoonSec V3

  • Boronide 0.4

  • Boronide 0.5

  • Boronide 0.6

Deobfuscation Support

If your deobfuscation fails, you will not be charged a token. If your deobfuscation gives incorrect results, open a ticket and developers will fix the issue and refund your token.

Last updated