NASM - The Netwide Assembler

NASM Forum => Programming with NASM => Topic started by: SHITTY23 on September 04, 2022, 09:21:34 PM

Title: Optimizing NASM Assembler codes in Windows x86
Post by: SHITTY23 on September 04, 2022, 09:21:34 PM
I am a novice in assembler programing, I will will appreciate if someone could review these NASM assembler code for me. Is about encoder decoder.
The encoder performs the following:

For those good at NASM assembler for Microsoft Windows, please could you optimize this code? the Code is working but takes lot of time. The shellcode is a windows/meterpreter/reverse_tcp   x86 from msfvenom.

Code: [Select]
global main

; gone
; Frank

Title: Re: Optimizing NASM Assembler codes in Windows x86
Post by: Frank Kotler on September 05, 2022, 10:11:37 AM
Shellcode has rather a bad reputation. Why are you using it?

Best,
Frank

Title: Re: Optimizing NASM Assembler codes in Windows x86
Post by: fredericopissarra on September 05, 2022, 01:02:42 PM
Very funny how you tried to inffect somebody computers with Trojan:Script/Wacatac.Html...

To the moderator I recommend deleting this and ban the user.

PS: Decode (do not run!) the byte stream and let the antivirus do its trick...
Title: Re: Optimizing NASM Assembler codes in Windows x86
Post by: Frank Kotler on September 05, 2022, 02:18:58 PM
Thank you, Fred!

I hadn't decoded decoded his shellcode, but would have before I ran it.
He's gone in just a second.

Best,
Frank

Title: Re: Optimizing NASM Assembler codes in Windows x86
Post by: tysonprogrammer on September 06, 2022, 09:56:50 PM
I chuckled at the username and it was a bit suspicious because of it :)
Title: Re: Optimizing NASM Assembler codes in Windows x86
Post by: Elawig57 on January 24, 2023, 06:06:43 AM
Hello,
It looks like the code you've provided

Redacted by moderator!
Title: Re: Optimizing NASM Assembler codes in Windows x86
Post by: Frank Kotler on January 24, 2023, 09:17:03 AM
The person with the questionable name has been banned from the forum.

If you do not want to join him, do not discus malware here!

Seriously,
Frank