Jump to content
Welcome, Guest
Existing user? Sign In

Sign In



Sign Up
The MatriX
  • Welcome To Ghbsys
  • CS GO Streaming Version is released. Have fun streaming while cheating!
  • Have a Payment Issue? Send us a Support ticket.
  • Make a thread if you need support or join our discord for live support.
  • Have Suggestions? Make a thread and you'll earn Ghbsys Points for implemented suggestions.
  • Join our discord to stay well connected! Don't forget to integrate your discord to the site
  • Welcome to [GHB] - GAmEhAcKbAsTaRdS Forum

    Welcome to [GHB] - GAmEhAcKbAsTaRdS Forum, like most online communities you must register to view or post in our community, but don't worry this is a simple free process that requires minimal information for you to signup. Be apart of [GHB] - GAmEhAcKbAsTaRdS Forum by signing in or creating an account.
    • Start new topics and reply to others
    • Subscribe to topics and forums to get email updates
    • Get your own profile page and make new friends
    • Send personal messages to other members.

    .NET Injection [v1.0.0.0]


    LithiumToast
     Share

    Recommended Posts

    How 'bout abit of an introduction first? My name is LithiumToast. I am hobbyist Visual Basic.NET and C#.NET programmer with a alittlebit of knowledge of C# and C++. I was a respected member under the name Toast on ghb but that place is long gone now. I know this kinda looks shady as this is my first post but I ensure you this not a scam/virus/waste of time or any of that crap.

     

    Okay now the good stuff.

     

    This is an 32-Bit/64-Bit injector that injects a .NET library, yes that means C#.NET or VB.NET code, into a native remote process such as WarRock.

     

    All the code is 100% made by me except for the command prompt injector, which is nothing but a normal unmanaged injector that works on all Windows operating systems. Expect an update in a couple days for timed injection O.o. Found any bugs? Please report them in this thread. I will try to fix them asap.

     

    Download:

    [hide_me]MULI - Managed & Unmanaged Library Injector v1.0.0.0[/hide_me]

     

    Download:

    [hide_me]Demo Library Injection v1.0.0.0[/hide_me]

     

    *Intructions*

     

    - Create a library with Visual Studio that you will be injecting. (Demo Library Injection source available to download above)

    - Build your library with Visual Studio.

    - Open MULI.exe

    - Select managed injection. (default)

    - Browse for your .NET library file.

    - Enter the namespace.class for your .NET library. If your using the Demo Library Injection this is "Demo_Injection_Library.Launcher" without quotations.

    - Enter the method name that will be executed from your .NET library. If your using the Demo Library Injection this is "Launch" without quotations.

    - Enter a parameter that will be passed with your method. If your using the Demo Library Injection whatever you enter here will popup in the messagebox.

    - Hit the "Save" button to save your .NET library information. (MULI will remember your .NET library information.)

    - Select your process either from a list of processes or from a window.

    - Unless you created a 64-Bit library and your target process is 64-Bit press the Inject 32-Bit button. (WarRock is 32-Bit) The time you inject your library doesn't really matter so far lol, but try to inject it before any anti-hacking software loads such as HackShield for stable results and to keep this undetected!.

     

    *Screenshots*

     

    screenshotgm.png

    Edited by LithiumToast
    Link to comment
    Share on other sites

    This Method was a long time non-public, well now it's public and many Biene Maja hacks are coming back O.o

    Link to comment
    Share on other sites

    Oh, I remember hearing somewhere Hans had figured this out before I even started to be interested in hacking. I heard this like over a year ago lol. But, this is still quite useful for people who started out like me, with no pre-experience in programming.

     

    Site note: Runtime.Marshal class, in the .NET framework, offers memory functions for the current process. Which if injected would be the remote process lol. I have tested most of the functions and they seem to be working correctly, however write functions sometimes get a insufficient rights error while the WriteProcessMemory API doesn't.

    Edited by LithiumToast
    Link to comment
    Share on other sites

    • 4 weeks later...
    How 'bout abit of an introduction first? My name is LithiumToast. I am hobbyist Visual Basic.NET and C#.NET programmer with a alittlebit of knowledge of C# and C++. I was a respected member under the name Toast on ghb but that place is long gone now. I know this kinda looks shady as this is my first post but I ensure you this not a scam/virus/waste of time or any of that crap.

     

    Okay now the good stuff.

     

    This is an 32-Bit/64-Bit injector that injects a .NET library, yes that means C#.NET or VB.NET code, into a native remote process such as WarRock.

     

    All the code is 100% made by me except for the command prompt injector, which is nothing but a normal unmanaged injector that works on all Windows operating systems. Expect an update in a couple days for timed injection O.o. Found any bugs? Please report them in this thread. I will try to fix them asap.

     

    Download:

    [ Hidden part. View original post. ]

     

    Download:

    [ Hidden part. View original post. ]

     

    *Intructions*

     

    - Create a library with Visual Studio that you will be injecting. (Demo Library Injection source available to download above)

    - Build your library with Visual Studio.

    - Open MULI.exe

    - Select managed injection. (default)

    - Browse for your .NET library file.

    - Enter the namespace.class for your .NET library. If your using the Demo Library Injection this is "Demo_Injection_Library.Launcher" without quotations.

    - Enter the method name that will be executed from your .NET library. If your using the Demo Library Injection this is "Launch" without quotations.

    - Enter a parameter that will be passed with your method. If your using the Demo Library Injection whatever you enter here will popup in the messagebox.

    - Hit the "Save" button to save your .NET library information. (MULI will remember your .NET library information.)

    - Select your process either from a list of processes or from a window.

    - Unless you created a 64-Bit library and your target process is 64-Bit press the Inject 32-Bit button. (WarRock is 32-Bit) The time you inject your library doesn't really matter so far lol, but try to inject it before any anti-hacking software loads such as HackShield for stable results and to keep this undetected!.

     

    *Screenshots*

     

    screenshotgm.png

    rep

    Link to comment
    Share on other sites

    • 2 weeks later...
    • 2 weeks later...
    • 3 weeks later...
    How 'bout abit of an introduction first? My name is LithiumToast. I am hobbyist Visual Basic.NET and C#.NET programmer with a alittlebit of knowledge of C# and C++. I was a respected member under the name Toast on ghb but that place is long gone now. I know this kinda looks shady as this is my first post but I ensure you this not a scam/virus/waste of time or any of that crap.

     

    Okay now the good stuff.

     

    This is an 32-Bit/64-Bit injector that injects a .NET library, yes that means C#.NET or VB.NET code, into a native remote process such as WarRock.

     

    All the code is 100% made by me except for the command prompt injector, which is nothing but a normal unmanaged injector that works on all Windows operating systems. Expect an update in a couple days for timed injection O.o. Found any bugs? Please report them in this thread. I will try to fix them asap.

     

    Download:

    [ Hidden part. View original post. ]

     

    Download:

    [ Hidden part. View original post. ]

     

    *Intructions*

     

    - Create a library with Visual Studio that you will be injecting. (Demo Library Injection source available to download above)

    - Build your library with Visual Studio.

    - Open MULI.exe

    - Select managed injection. (default)

    - Browse for your .NET library file.

    - Enter the namespace.class for your .NET library. If your using the Demo Library Injection this is "Demo_Injection_Library.Launcher" without quotations.

    - Enter the method name that will be executed from your .NET library. If your using the Demo Library Injection this is "Launch" without quotations.

    - Enter a parameter that will be passed with your method. If your using the Demo Library Injection whatever you enter here will popup in the messagebox.

    - Hit the "Save" button to save your .NET library information. (MULI will remember your .NET library information.)

    - Select your process either from a list of processes or from a window.

    - Unless you created a 64-Bit library and your target process is 64-Bit press the Inject 32-Bit button. (WarRock is 32-Bit) The time you inject your library doesn't really matter so far lol, but try to inject it before any anti-hacking software loads such as HackShield for stable results and to keep this undetected!.

     

    *Screenshots*

     

    screenshotgm.png

    Link to comment
    Share on other sites

    • 3 weeks later...
    How 'bout abit of an introduction first? My name is LithiumToast. I am hobbyist Visual Basic.NET and C#.NET programmer with a alittlebit of knowledge of C# and C++. I was a respected member under the name Toast on ghb but that place is long gone now. I know this kinda looks shady as this is my first post but I ensure you this not a scam/virus/waste of time or any of that crap.

     

    Okay now the good stuff.

     

    This is an 32-Bit/64-Bit injector that injects a .NET library, yes that means C#.NET or VB.NET code, into a native remote process such as WarRock.

     

    All the code is 100% made by me except for the command prompt injector, which is nothing but a normal unmanaged injector that works on all Windows operating systems. Expect an update in a couple days for timed injection O.o. Found any bugs? Please report them in this thread. I will try to fix them asap.

     

    Download:

    [hide_me]MULI - Managed & Unmanaged Library Injector v1.0.0.0[/hide_me]

     

    Download:

    [hide_me]Demo Library Injection v1.0.0.0[/hide_me]

     

    *Intructions*

     

    - Create a library with Visual Studio that you will be injecting. (Demo Library Injection source available to download above)

    - Build your library with Visual Studio.

    - Open MULI.exe

    - Select managed injection. (default)

    - Browse for your .NET library file.

    - Enter the namespace.class for your .NET library. If your using the Demo Library Injection this is "Demo_Injection_Library.Launcher" without quotations.

    - Enter the method name that will be executed from your .NET library. If your using the Demo Library Injection this is "Launch" without quotations.

    - Enter a parameter that will be passed with your method. If your using the Demo Library Injection whatever you enter here will popup in the messagebox.

    - Hit the "Save" button to save your .NET library information. (MULI will remember your .NET library information.)

    - Select your process either from a list of processes or from a window.

    - Unless you created a 64-Bit library and your target process is 64-Bit press the Inject 32-Bit button. (WarRock is 32-Bit) The time you inject your library doesn't really matter so far lol, but try to inject it before any anti-hacking software loads such as HackShield for stable results and to keep this undetected!.

     

    *Screenshots*

     

    screenshotgm.png

    Link to comment
    Share on other sites

    • 1 month later...

    I'm still wondering why there aren't some new 1337Biene Majahacks out, this method is so usefull xD

    Link to comment
    Share on other sites

    Guest
    This topic is now closed to further replies.
     Share

    • Recently Browsing   0 members

      • No registered users viewing this page.
    ×
    ×
    • Create New...