Skip to content
View in the app

A better way to browse. Learn more.

DECODEHUB - Software and reverse engineering community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.
Decodehub.org rank system
New badge system

[Tool] AutoReaktör - batch .NET Reactor unpacking pipeline (de4dot + Slayer + Krypton chain)

Featured Replies

Wrote this for my own backlog, figured I'd share. Source:

This is the hidden content, please

What it does: runs de4dot, NETReactorSlayer and Krypton in the order that actually works. de4dot only as pre-clean, Slayer always on the ORIGINAL protected file (feeding it de4dot output breaks method decryption, found that out the hard way), Krypton last for Code Virtualization targets. Every file gets a report.json with exit codes and hashes, so reruns are comparable. No guessing what a stage did.

Two new chains from the last week:

nbfixctor2 - NecroBit nag strip in dnlib, single command, no hand-typed symbols. It finds the form type from the entry point, force-rets the nag/guard methods with proper return types, NOPs the encrypted token calls instead of deleting them. Deleting those shifts branch targets and collapses bodies. Also breaks the cctor re-entrancy. Ran it on 5 layer combos of the same 7.5-packed sample: base / +VM / +VM+cflow-L9 / +antidebug+merge / +compression. All five outputs open the GUI and stay up for 2 minutes, checked by window enumeration not by "didn't crash".

Dump route for native-stub targets. Some builds ship with CLR RVA 0 and no metadata on disk, the assembly is built in memory at runtime. de4dot crashes on those, Slayer can't load them. Route: let it run, take a full minidump, scan for the managed image, validate the BSJB, cut it out, nbfixctor2, write the exe. Recovered an 84 KB assembly out of a 177 MB dump this way, output runs fine.

What it doesn't do: 7.x string decryption. Slayer's last release is 6.4 (Dec 2022) and its decrypter won't initialize on 7.x, I'm not going to pretend otherwise. nbfixctor2 makes things runnable, strings stay in whatever state Slayer left them.

If you run it on something, post the stage log from report.json. Real-world results from this forum's downloads are exactly what's missing in this topic rn.

— CAINE

Edited by CAINE

  • Replies 6
  • Views 1.1k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

Hello, thanks for this tool; however, I have a question: Is this tool compatible with the "Slayer Fix 11" version shared by Cambaz on the forum? Perhaps this way, it might be possible to resolve the issues related to the "7x" versions.

  • Author
10 hours ago, delicious said:

Hello, thanks for this tool; however, I have a question: Is this tool compatible with the "Slayer Fix 11" version shared by Cambaz on the forum? Perhaps this way, it might be possible to resolve the issues related to the "7x" versions.

I checked Fixed11 it’s Slayer 6.4 with a test call remover and an int cflow patch added. The base is the same as what my pipeline is already running.

But the NecroBit decryptor is the part it didn’t touch. I tested an existing NecroBit target with it today, and it still fails with the “Could not initialize decrypter” error, just like the original 6.4. So the anti-tamper and decryption are working; the decryptor initialization path just isn’t among the things Fixed11 changed.

My approach for 7x bypasses this (works around it): a JIT hook that captures method bodies during compilation, plus check-kill on tamper calls. I tested it on a .NET 8 target packaged with the 7.5 demo—I extracted a NecroBit-protected method, restored its actual body, verified it in real time, and 10 out of 10 inputs matched.

If there’s a 7x unpackme that Fixed11 is working on, send me the link and I’ll do a head-to-head comparison.

4 hours ago, CAINE said:

I checked Fixed11 it’s Slayer 6.4 with a test call remover and an int cflow patch added. The base is the same as what my pipeline is already running.

But the NecroBit decryptor is the part it didn’t touch. I tested an existing NecroBit target with it today, and it still fails with the “Could not initialize decrypter” error, just like the original 6.4. So the anti-tamper and decryption are working; the decryptor initialization path just isn’t among the things Fixed11 changed.

My approach for 7x bypasses this (works around it): a JIT hook that captures method bodies during compilation, plus check-kill on tamper calls. I tested it on a .NET 8 target packaged with the 7.5 demo—I extracted a NecroBit-protected method, restored its actual body, verified it in real time, and 10 out of 10 inputs matched.

If there’s a 7x unpackme that Fixed11 is working on, send me the link and I’ll do a head-to-head comparison.

Do you have .NET Reactor 7.5.0.0?

  • Author
1 hour ago, timosan said:

Do you have .NET Reactor 7.5.0.0?

Im working on the demo

1 hour ago, CAINE said:

Im working on the demo

It turns out this site has the full version; thank you.

Thanks for sharing!

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.