[byte[]]

LuminosityLink is a highly advanced RAT that contains features such as a usermode ring3 rootkit, powerful persistence, silent startup, and amazing Anti-Malware/Bot Killer. However, crypting Luminosity while using all its great features can be a challenge. Therefore, I have created this tutorial to assist users.

What Crypters Work Best?
According to KFC Watermelon himself, any crypter which stub is coded in .NET and has self injection will work perfect with Luminosity and its features. He recommends AeonHack's RunPE, stating that the self injection on it works excellent with Luminosity and its rootkit.

If you are going to purchase a crypter, it is highly recommended that you PM the seller first to ensure it works with Luminosity. Send him or her a link to this thread - it will be helpful to the seller as well.

Crypter Settings:
If your crypter meets the above specifications (.NET Crypter with self injection), disable all settings within your crypter (such as startup, persistence, mutex, etc) and just enable self injection, "Inject into self." That is all you need. You may then enable the startup/persistence/rootkit within Luminosity.

If your crypter does not meet the above specifications, meaning it is coded in another language (AutoIT, C++, etc), then you must disable the startup/installation/rootkit within Luminosity. You must then enable the startup option within your crypter. You should also enable ".NET Support" within your crypter, if it's an option.

Contact your Crypter Seller!
KFC Watermelon provides support for LuminosityLink. He does not provide support for crypters, as he does not make or sell them. You should contact the coder of your crypter, and/or the support, in order to get the appropriate settings and information.

In addition, you may post a reply to this thread to ask for help. If you have appropriate crypter settings, it would be greatly appreciated if you posted them here for others to see. Thank you!


Credits:
-KFC Watermelon (thread design and software)
-AeonHack (RunPE which was tested with LuminosityLink extensively)
-Me (creating thread, helping KFC test crypters)

[Incendiary.]

Vouch,
byte is a very skilled person, knows his shit.
His crypter is very good, I would recommend checking that out.

[LegendaryFox]

Time to figure out how to use it with RazerCrypter :C

However VERY usefull guide thanks
EDIT: Well RazerCrypter is incompatible sadly. Also AeonHack's RunPE is source only, well I'm screw'd now ^^.

[BahNahNah]

Time to figure out how to use it with RazerCrypter :C

However VERY usefull guide thanks
EDIT: Well RazerCrypter is incompatible sadly. Also AeonHack's RunPE is source only, well I'm screw'd now ^^.

You can use my opensource crypter.
It uses aeonhacks runpe.
https://hackforums.net/showthread.php?tid=4801618

[h4tee]

Hello byte,
i would like to contribute to your thread by mentioning this -
Luminosity is a very size-dependent RAT. Now, im not 100% sure of this, so ignore this if im wrong, but what ive noticed is that if you make the crypted file too large, the Luminosity's stub will simply get corrupt and the RAT wont work. Now, sorry if thats already known or basic logic, just wanted to leave it there.
Also, reading from above if youre using a crypter that allows you to change icon/assembly (like cyberseal) you might notice that if your rat is not in the same size or close to that as the original, safe file, you will get alot of bary detections. Therefore, use a smaller file to copy assemlby from, some kb's to match the file size in a radius of 300kb and you should be fine!

Hope i helped someone.

[KFC Watermelon]

Hello byte,
i would like to contribute to your thread by mentioning this -
Luminosity is a very size-dependent RAT. Now, im not 100% sure of this, so ignore this if im wrong, but what ive noticed is that if you make the crypted file too large, the Luminosity's stub will simply get corrupt and the RAT wont work. Now, sorry if thats already known or basic logic, just wanted to leave it there.
Also, reading from above if youre using a crypter that allows you to change icon/assembly (like cyberseal) you might notice that if your rat is not in the same size or close to that as the original, safe file, you will get alot of bary detections. Therefore, use a smaller file to copy assemlby from, some kb's to match the file size in a radius of 300kb and you should be fine!

Hope i helped someone.

This is incorrect information. The size of the output has nothing to do with wherever it will work or not.

I can't provide support regarding crypting Luminosity 9/10 of the times. I don't code a crypter. I'm not the support of your crypter.

[DaPiranha]

Happy this works great with Abyss Protect! A lot of my customers are satisfied.

[chinchedder]

Does it work with cyberseal?

[KFC Watermelon]

Does it work with cyberseal?

Should work fine with CyberSeal, though I cannot personally recommend it as I have not used it.

[n0$f3ratu$]

Hello byte,
i would like to contribute to your thread by mentioning this -
Luminosity is a very size-dependent RAT. Now, im not 100% sure of this, so ignore this if im wrong, but what ive noticed is that if you make the crypted file too large, the Luminosity's stub will simply get corrupt and the RAT wont work. Now, sorry if thats already known or basic logic, just wanted to leave it there.
Also, reading from above if youre using a crypter that allows you to change icon/assembly (like cyberseal) you might notice that if your rat is not in the same size or close to that as the original, safe file, you will get alot of bary detections. Therefore, use a smaller file to copy assemlby from, some kb's to match the file size in a radius of 300kb and you should be fine!

Hope i helped someone.

That made me laugh so hard....

[chinchedder]

Should work fine with CyberSeal, though I cannot personally recommend it as I have not used it.

Ah thanks, im about to get fileguardian or cyberseal, what do you recommend or what would you get?

[Ponut]

Ah thanks, im about to get fileguardian or cyberseal, what do you recommend or what would you get?

You can also test my free crypter
https://hackforums.net/showthread.php?tid=4803353
It's currently fud.
🤝

[KFC Watermelon]

Ah thanks, im about to get fileguardian or cyberseal, what do you recommend or what would you get?

File Guardian won't work with Luminosity's Rootkit/Installation/Persistence.

[KFC Watermelon]

This thread needs to be updated. The Rootkit may now be used with native and AutoIT crypter. Only installation needs to be disabled.

[lavic2001]

Cryptex reborn works fine with your tool KFC. I will make tutorial how to make fud using LuminosityLink and Cryptex_Reborn