Jump to content

Search the Community

Showing results for tags 'Shellcode'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Talk
    • Everything Else
    • Gaming
    • Questions
    • Business and Enterprise IT
    • Security
    • Hacks & Mods
    • Applications & Coding
    • Trading Post
  • Hak5 Gear
    • Hak5 Cloud C²
    • WiFi Pineapple Mark VII
    • USB Rubber Ducky
    • Bash Bunny
    • Key Croc
    • Packet Squirrel
    • Shark Jack
    • Signal Owl
    • LAN Turtle
    • Screen Crab
    • Plunder Bug
  • O.MG (Mischief Gadgets)
    • O.MG Cable
    • O.MG DemonSeed EDU
  • WiFi Pineapple (previous generations)
    • WiFi Pineapple TETRA
    • WiFi Pineapple NANO
    • WiFi Pineapple Mark V
    • WiFi Pineapple Mark IV
    • Pineapple Modules
    • WiFi Pineapples Mark I, II, III
  • Hak5 Shows
  • Community
    • Forums and Wiki
    • #Hak5
  • Projects
    • SDR - Software Defined Radio
    • Community Projects
    • Interceptor
    • USB Hacks
    • USB Multipass
    • Pandora Timeshifting

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests


Enter a five letter word.

Found 1 result

  1. So I was writing a PERL script to automate Ghostwriting ASM shellcode and sort of hit a block in terms of designing the obfuscation engine. But, what I do have now is a fairly functional ASM parser. THere are definitely issues, and certainly things that can be added to improve, but it does things well for the most part. I had an idea to make it more useful/fun. What about giving the user a register+stack state and having him code the ASM for it using the inline parser I have in the script and give him points for doing clever things and solving difficult problems with fewer lines of code. The point of all this being to help people understand ASM and shellcode, and possibly draw more interest into the shellcoding world, which I happen to greatly enjoy. Sample outputs of my program look something like this: Phant0m>mov eax,0x41414141 <> {!} -- Instruction: >MOV< FirstOp: >eax< Value: >0x41414141< <> {!} -- CMD: MOV EAX, 0x41414141 <> {!} -- Registering a change in EAX. <> {!} -- Change Registered. <> {!} -- EAX has changed. Taking that into account. <> {!} -- Changing the child registers of EAX now. <> {!} -- Child registers of EAX now changed. <> {!} -- EAX is now: 1094795585. <> {!} -- Updating flags... <> {!} -- Bit length of EAX is: 32 <> {!} -- Flags are now changed. ZF: 0 SF: 0 OF: 0 Current status: All purpose Registers ---------------------------- EAX: 0x41414141 AX: 0x4141 AH: 0x41 AL: 0x41 EBX: 0x071DBDF8 BX: 0xBDF8 BH: 0xBD BL: 0xF8 ECX: 0x38ECCEBF CX: 0xCEBF CH: 0xCE CL: 0xBF EDX: 0x0EF4DFF1 DX: 0xDFF1 DH: 0xDF DL: 0xF1 ZF: 0 SF: 0 OF: 0 ESP: 0x0A3C9827 EBP: 0x0A3C9817 Stack ----------------------------- ----Hex-----------Decimal---------String---- Phant0m>push eax <> {!} -- Instruction: >PUSH< FirstOp: >eax< Value: >< <> {!} -- CMD: PUSH eax <> {!} -- Registering a change in ESP. <> {!} -- Change Registered. <> {!} -- 1094795585 has been pushed to stack. Current status: All purpose Registers ---------------------------- EAX: 0x41414141 AX: 0x4141 AH: 0x41 AL: 0x41 EBX: 0x071DBDF8 BX: 0xBDF8 BH: 0xBD BL: 0xF8 ECX: 0x38ECCEBF CX: 0xCEBF CH: 0xCE CL: 0xBF EDX: 0x0EF4DFF1 DX: 0xDFF1 DH: 0xDF DL: 0xF1 ZF: 0 SF: 0 OF: 0 ESP: 0x0A3C9828 EBP: 0x0A3C9817 Stack ----------------------------- ----Hex-----------Decimal---------String---- 0x41414141 1094795585 AAAA Phant0m> So its fairly easy to read in its most verbose state, and definitely would help people learn ASM with greater fluency. Also, if people were to read my (terrible) source and improve on it, or give suggestions, the hacking community as a whle would benefit. Anyway, if anyone has feedback on this, let me know.
×
×
  • Create New...