This post is by a banned member (MASTER6Y9) - Unhide
07 April, 2024 - 12:12 PM
Reply
This post is by a banned member (Vaporahere) - Unhide
07 April, 2024 - 05:22 PM
Reply
This post is by a banned member (andrix343434) - Unhide
07 April, 2024 - 07:30 PM
Reply
(23 March, 2024 - 07:29 PM)VolCoder Wrote: Show MoreNLBrute
![[Image: FqETTeo.png]](https://i.imgur.com/FqETTeo.png)
Description
Show ContentSpoiler:
NLBrute Manager allows launching and managing multiple instances of NLBrute from a single interface. The main feature is the ability to divide tasks into parts for instances. NLBrute Manager automatically divides the file and monitors all NLBrute instances. It can queue parts of tasks and provide a new portion of NLBrute upon completion of each instance. There is also clear real-time statistics (speed, results, failures, etc.) displayed.
NLBrute Manager allows launching and managing multiple instances of NLBrute from a single interface. The main feature is the ability to divide tasks into parts for instances. NLBrute Manager automatically divides the file and monitors all NLBrute instances. It can queue parts of tasks and provide a new portion of NLBrute upon completion of each instance. There is also clear real-time statistics (speed, results, failures, etc.) displayed.
It is well known that NLBrute is glitchy, so we have tried to bypass the errors it has, namely: - Crashes (both instant crashes and hanging at the WerFault dumping window).
- Crashes related to OS resource shortage and invalid memory access (csrss message).
- Complete hanging during operation.
- Damage to the settings.ini configuration file.
The instance's work is restored from the saved position. There is customizable removal of IP lines after a crash to bypass glitchy IPs.
This has resulted in achieving stable brute force operations with NLBrute.
Possible additions in future updates include: - Centralized management of multiple servers with NLBrute Manager for distributed brute-forcing.
- Adding an NLBrute auto-activator.
- Notifications via Telegram bot.
Usage
Show ContentSpoiler:
- Navigate to the tools\NL_sample folder and activate NLBrute.exe (activator not included). Do not touch anything else in this folder!!!
- Run NLBrute_Manager.exe
Allowed data formats in input files: - Encoding: ANSI (without Unicode, BOM, UTF8, etc.).
- Line break style: Windows (CR LF) or Linux (LF).
Settings
Show ContentSpoiler:
"Source" Block:
~ IP - path to the file with ip:port (1 per line). Alternatively, you can specify a file in z668 format (1.2.3.4:3389>>>>user1;user2;). ~ Username - path to the file with usernames. ~ Password - path to the file with passwords. PS. Next to each, there will be a designation with the number of lines in the corresponding file.
"Result" Block:
~ Save Path - path to save the results of work (from all copies of NLBrute). ~ Format - format of recording work results. Switches: ~ Append - append the results file when starting a new brute. ~ Remove on start - delete the results file at the start of a new brute.
"Split" Block:
~ Split parts - divide the selected file into how many parts. Each part of the task will go to a separate NLBrute instance. Purpose of switches: - IP (default) - the file with IP will be split into parts. You can choose the order in which login:password pairs are substituted: if the "Order by password" checkbox is selected, passwords will be substituted first, and then all usernames will be tried with each of them. Otherwise, usernames will be taken first, and then all passwords will be tried with each of them.
- Username - split into parts from the user file.
- Password - split into parts from the password file.
~ Parallel instances - how many copies of NLBrute to run simultaneously (recommended not more than 10000 threads, i.e., if 1500 threads are configured per instance, then no more than 7 instances - depends on available PC resources).
PS. Below is automatically calculated approximate number of authorizations (1 pair login:password per 1 instance).
"Network" Block:
~ Threads count (NLBrute option) - number of parallel threads per 1 instance. ~ Timeout (NLBrute option) - maximum time to wait for a response from a thread. ~ Max Attempts (NLBrute option) - maximum number of connection attempts. ~ Default Port (NLBrute option) - brute port. ~ Del. lines on crash - delete the specified number of IP lines from the servers.txt file when NLBrute crashes. Lines are counted from the last autosave. NLBrute itself makes autosaves once a minute. Set to 0 to not delete anything on crash. ~ Del. lines on hang - delete the specified number of IP lines from the servers.txt file when NLBrute hangs. Lines are counted from the last autosave. NLBrute itself makes autosaves once a minute. Set to 0 to not delete anything on hang. ~ Log Crashed IP - write all IPs excluded from checking due to NLBrute crashes/hangs to a separate file next to the program (log_ip_crashed.log) (see 2 settings above). ~ Server checking (NLBrute option) - check PC availability before starting brute.
"Launch" Block:
~ Minimized - launch NLBrute minimized to the taskbar. ~ Hidden - launch NLBrute hidden. ~ Log debug - write debug info to a file (log_debug.log) next to the program. Helps the developer to understand errors. ~ Stop - stop the brute force process and kill all NLBrute copies. ~ Pause - pause the brute force process. Works instantly. Not recommended to use frequently. ~ Results - open the file with work results (if there is anything). ~ Run - start the brute force process. PS. Also, at the bottom, there is a label with the status: - Initializing... - manager form loading.
- Starting... - starting instances.
- Working... - all instances are started, waiting for their completion and/or starting new instances from the queue.
- Paused - instances are paused (frozen).
- Stopped - work prematurely stopped by the Stop button.
- Finished - work of all task instances is completed (or stopped).
"Status" Block:
~ Started at - time when brute force started. ~ Elapsed - time passed. ~ Time left - estimated time remaining until the end of brute force (estimated by the time of full completion of the last instance(s)). ~ Speed - average work speed (authorizations (login-password pair) / per second). ~ Processed - number of successfully completed instances, as well as their total number in the task and the overall completion percentage. ~ Skipped IP - number of IPs excluded from checking due to NLBrute crashes/hangs (number taken from settings in the "Network" block). ~ Success - number of successfully cracked authorizations (shown in real-time, transferred to the overall results file). ~ Crashes - number of crashes in the format: "x1 / i", where: *x1: total number of crashes; *i: number of unique instances where crashes occurred. ~ Hangs - number of hangs in the format: "x1 @ x2 @ x3 / i", where: *x1: hang due to memory access error ("Application Error"); *x2: hang when NLBrute stops auto-saving; *x3: hang due to a broken setting.ini or activation check failure; *i: number of unique instances where hangs occurred (restarted instance is not counted).
Miscellaneous
Show ContentSpoiler:
What is NLBrute_Watch.exe process for? Watcher - this is a copy of the manager, serving one purpose - to monitor the manager. If it is suddenly decided to terminate it from the outside (for any reason), Watcher will ensure the closure of all NLBrute instances and terminate itself.
The numbers "# X" in the NLBrute window titles - denote the instance number, corresponding to the folder number in tools\work\NL_X from which this instance is launched.
Complete hang is detected by the sign: if the results of work have
Download
VT Links
Show ContentSpoiler:
Code: NLBrute_Manager.exe: https://www.virustotal.com/gui/file/6badcd1498647bd5fc54d31b9ff03995daaae055ae7079c4c0387c61fda2806c NLBrute_watch.exe: https://www.virustotal.com/gui/file/6badcd1498647bd5fc54d31b9ff03995daaae055ae7079c4c0387c61fda2806c NLBrute.exe: https://www.virustotal.com/gui/file/a332f863da1709b27b62f3a3f2a06dca48c7dabe6b8db76ec7bb81ce3786e527
ty
This post is by a banned member (AmineAfia) - Unhide
07 April, 2024 - 07:43 PM
Reply
(23 March, 2024 - 07:29 PM)VolCoder Wrote: Show MoreNLBrute
Description
Show ContentSpoiler:
NLBrute Manager allows launching and managing multiple instances of NLBrute from a single interface. The main feature is the ability to divide tasks into parts for instances. NLBrute Manager automatically divides the file and monitors all NLBrute instances. It can queue parts of tasks and provide a new portion of NLBrute upon completion of each instance. There is also clear real-time statistics (speed, results, failures, etc.) displayed.
NLBrute Manager allows launching and managing multiple instances of NLBrute from a single interface. The main feature is the ability to divide tasks into parts for instances. NLBrute Manager automatically divides the file and monitors all NLBrute instances. It can queue parts of tasks and provide a new portion of NLBrute upon completion of each instance. There is also clear real-time statistics (speed, results, failures, etc.) displayed.
It is well known that NLBrute is glitchy, so we have tried to bypass the errors it has, namely: - Crashes (both instant crashes and hanging at the WerFault dumping window).
- Crashes related to OS resource shortage and invalid memory access (csrss message).
- Complete hanging during operation.
- Damage to the settings.ini configuration file.
The instance's work is restored from the saved position. There is customizable removal of IP lines after a crash to bypass glitchy IPs.
This has resulted in achieving stable brute force operations with NLBrute.
Possible additions in future updates include: - Centralized management of multiple servers with NLBrute Manager for distributed brute-forcing.
- Adding an NLBrute auto-activator.
- Notifications via Telegram bot.
Usage
Show ContentSpoiler:
- Navigate to the tools\NL_sample folder and activate NLBrute.exe (activator not included). Do not touch anything else in this folder!!!
- Run NLBrute_Manager.exe
Allowed data formats in input files: - Encoding: ANSI (without Unicode, BOM, UTF8, etc.).
- Line break style: Windows (CR LF) or Linux (LF).
Settings
Show ContentSpoiler:
"Source" Block:
~ IP - path to the file with ip:port (1 per line). Alternatively, you can specify a file in z668 format (1.2.3.4:3389>>>>user1;user2;). ~ Username - path to the file with usernames. ~ Password - path to the file with passwords. PS. Next to each, there will be a designation with the number of lines in the corresponding file.
"Result" Block:
~ Save Path - path to save the results of work (from all copies of NLBrute). ~ Format - format of recording work results. Switches: ~ Append - append the results file when starting a new brute. ~ Remove on start - delete the results file at the start of a new brute.
"Split" Block:
~ Split parts - divide the selected file into how many parts. Each part of the task will go to a separate NLBrute instance. Purpose of switches: - IP (default) - the file with IP will be split into parts. You can choose the order in which login:password pairs are substituted: if the "Order by password" checkbox is selected, passwords will be substituted first, and then all usernames will be tried with each of them. Otherwise, usernames will be taken first, and then all passwords will be tried with each of them.
- Username - split into parts from the user file.
- Password - split into parts from the password file.
~ Parallel instances - how many copies of NLBrute to run simultaneously (recommended not more than 10000 threads, i.e., if 1500 threads are configured per instance, then no more than 7 instances - depends on available PC resources).
PS. Below is automatically calculated approximate number of authorizations (1 pair login:password per 1 instance).
"Network" Block:
~ Threads count (NLBrute option) - number of parallel threads per 1 instance. ~ Timeout (NLBrute option) - maximum time to wait for a response from a thread. ~ Max Attempts (NLBrute option) - maximum number of connection attempts. ~ Default Port (NLBrute option) - brute port. ~ Del. lines on crash - delete the specified number of IP lines from the servers.txt file when NLBrute crashes. Lines are counted from the last autosave. NLBrute itself makes autosaves once a minute. Set to 0 to not delete anything on crash. ~ Del. lines on hang - delete the specified number of IP lines from the servers.txt file when NLBrute hangs. Lines are counted from the last autosave. NLBrute itself makes autosaves once a minute. Set to 0 to not delete anything on hang. ~ Log Crashed IP - write all IPs excluded from checking due to NLBrute crashes/hangs to a separate file next to the program (log_ip_crashed.log) (see 2 settings above). ~ Server checking (NLBrute option) - check PC availability before starting brute.
"Launch" Block:
~ Minimized - launch NLBrute minimized to the taskbar. ~ Hidden - launch NLBrute hidden. ~ Log debug - write debug info to a file (log_debug.log) next to the program. Helps the developer to understand errors. ~ Stop - stop the brute force process and kill all NLBrute copies. ~ Pause - pause the brute force process. Works instantly. Not recommended to use frequently. ~ Results - open the file with work results (if there is anything). ~ Run - start the brute force process. PS. Also, at the bottom, there is a label with the status: - Initializing... - manager form loading.
- Starting... - starting instances.
- Working... - all instances are started, waiting for their completion and/or starting new instances from the queue.
- Paused - instances are paused (frozen).
- Stopped - work prematurely stopped by the Stop button.
- Finished - work of all task instances is completed (or stopped).
"Status" Block:
~ Started at - time when brute force started. ~ Elapsed - time passed. ~ Time left - estimated time remaining until the end of brute force (estimated by the time of full completion of the last instance(s)). ~ Speed - average work speed (authorizations (login-password pair) / per second). ~ Processed - number of successfully completed instances, as well as their total number in the task and the overall completion percentage. ~ Skipped IP - number of IPs excluded from checking due to NLBrute crashes/hangs (number taken from settings in the "Network" block). ~ Success - number of successfully cracked authorizations (shown in real-time, transferred to the overall results file). ~ Crashes - number of crashes in the format: "x1 / i", where: *x1: total number of crashes; *i: number of unique instances where crashes occurred. ~ Hangs - number of hangs in the format: "x1 @ x2 @ x3 / i", where: *x1: hang due to memory access error ("Application Error"); *x2: hang when NLBrute stops auto-saving; *x3: hang due to a broken setting.ini or activation check failure; *i: number of unique instances where hangs occurred (restarted instance is not counted).
Miscellaneous
Show ContentSpoiler:
What is NLBrute_Watch.exe process for? Watcher - this is a copy of the manager, serving one purpose - to monitor the manager. If it is suddenly decided to terminate it from the outside (for any reason), Watcher will ensure the closure of all NLBrute instances and terminate itself.
The numbers "# X" in the NLBrute window titles - denote the instance number, corresponding to the folder number in tools\work\NL_X from which this instance is launched.
Complete hang is detected by the sign: if the results of work have
Download
VT Links
Show ContentSpoiler:
Code: NLBrute_Manager.exe: https://www.virustotal.com/gui/file/6badcd1498647bd5fc54d31b9ff03995daaae055ae7079c4c0387c61fda2806c NLBrute_watch.exe: https://www.virustotal.com/gui/file/6badcd1498647bd5fc54d31b9ff03995daaae055ae7079c4c0387c61fda2806c NLBrute.exe: https://www.virustotal.com/gui/file/a332f863da1709b27b62f3a3f2a06dca48c7dabe6b8db76ec7bb81ce3786e527
"zr"r"zr
This post is by a banned member (salhiefwew) - Unhide
08 April, 2024 - 05:34 PM
Reply
(23 March, 2024 - 07:29 PM)VolCoder Wrote: Show MoreNLBrute
Description
Show ContentSpoiler:
NLBrute Manager allows launching and managing multiple instances of NLBrute from a single interface. The main feature is the ability to divide tasks into parts for instances. NLBrute Manager automatically divides the file and monitors all NLBrute instances. It can queue parts of tasks and provide a new portion of NLBrute upon completion of each instance. There is also clear real-time statistics (speed, results, failures, etc.) displayed.
NLBrute Manager allows launching and managing multiple instances of NLBrute from a single interface. The main feature is the ability to divide tasks into parts for instances. NLBrute Manager automatically divides the file and monitors all NLBrute instances. It can queue parts of tasks and provide a new portion of NLBrute upon completion of each instance. There is also clear real-time statistics (speed, results, failures, etc.) displayed.
It is well known that NLBrute is glitchy, so we have tried to bypass the errors it has, namely: - Crashes (both instant crashes and hanging at the WerFault dumping window).
- Crashes related to OS resource shortage and invalid memory access (csrss message).
- Complete hanging during operation.
- Damage to the settings.ini configuration file.
The instance's work is restored from the saved position. There is customizable removal of IP lines after a crash to bypass glitchy IPs.
This has resulted in achieving stable brute force operations with NLBrute.
Possible additions in future updates include: - Centralized management of multiple servers with NLBrute Manager for distributed brute-forcing.
- Adding an NLBrute auto-activator.
- Notifications via Telegram bot.
Usage
Show ContentSpoiler:
- Navigate to the tools\NL_sample folder and activate NLBrute.exe (activator not included). Do not touch anything else in this folder!!!
- Run NLBrute_Manager.exe
Allowed data formats in input files: - Encoding: ANSI (without Unicode, BOM, UTF8, etc.).
- Line break style: Windows (CR LF) or Linux (LF).
Settings
Show ContentSpoiler:
"Source" Block:
~ IP - path to the file with ip:port (1 per line). Alternatively, you can specify a file in z668 format (1.2.3.4:3389>>>>user1;user2;). ~ Username - path to the file with usernames. ~ Password - path to the file with passwords. PS. Next to each, there will be a designation with the number of lines in the corresponding file.
"Result" Block:
~ Save Path - path to save the results of work (from all copies of NLBrute). ~ Format - format of recording work results. Switches: ~ Append - append the results file when starting a new brute. ~ Remove on start - delete the results file at the start of a new brute.
"Split" Block:
~ Split parts - divide the selected file into how many parts. Each part of the task will go to a separate NLBrute instance. Purpose of switches: - IP (default) - the file with IP will be split into parts. You can choose the order in which login:password pairs are substituted: if the "Order by password" checkbox is selected, passwords will be substituted first, and then all usernames will be tried with each of them. Otherwise, usernames will be taken first, and then all passwords will be tried with each of them.
- Username - split into parts from the user file.
- Password - split into parts from the password file.
~ Parallel instances - how many copies of NLBrute to run simultaneously (recommended not more than 10000 threads, i.e., if 1500 threads are configured per instance, then no more than 7 instances - depends on available PC resources).
PS. Below is automatically calculated approximate number of authorizations (1 pair login:password per 1 instance).
"Network" Block:
~ Threads count (NLBrute option) - number of parallel threads per 1 instance. ~ Timeout (NLBrute option) - maximum time to wait for a response from a thread. ~ Max Attempts (NLBrute option) - maximum number of connection attempts. ~ Default Port (NLBrute option) - brute port. ~ Del. lines on crash - delete the specified number of IP lines from the servers.txt file when NLBrute crashes. Lines are counted from the last autosave. NLBrute itself makes autosaves once a minute. Set to 0 to not delete anything on crash. ~ Del. lines on hang - delete the specified number of IP lines from the servers.txt file when NLBrute hangs. Lines are counted from the last autosave. NLBrute itself makes autosaves once a minute. Set to 0 to not delete anything on hang. ~ Log Crashed IP - write all IPs excluded from checking due to NLBrute crashes/hangs to a separate file next to the program (log_ip_crashed.log) (see 2 settings above). ~ Server checking (NLBrute option) - check PC availability before starting brute.
"Launch" Block:
~ Minimized - launch NLBrute minimized to the taskbar. ~ Hidden - launch NLBrute hidden. ~ Log debug - write debug info to a file (log_debug.log) next to the program. Helps the developer to understand errors. ~ Stop - stop the brute force process and kill all NLBrute copies. ~ Pause - pause the brute force process. Works instantly. Not recommended to use frequently. ~ Results - open the file with work results (if there is anything). ~ Run - start the brute force process. PS. Also, at the bottom, there is a label with the status: - Initializing... - manager form loading.
- Starting... - starting instances.
- Working... - all instances are started, waiting for their completion and/or starting new instances from the queue.
- Paused - instances are paused (frozen).
- Stopped - work prematurely stopped by the Stop button.
- Finished - work of all task instances is completed (or stopped).
"Status" Block:
~ Started at - time when brute force started. ~ Elapsed - time passed. ~ Time left - estimated time remaining until the end of brute force (estimated by the time of full completion of the last instance(s)). ~ Speed - average work speed (authorizations (login-password pair) / per second). ~ Processed - number of successfully completed instances, as well as their total number in the task and the overall completion percentage. ~ Skipped IP - number of IPs excluded from checking due to NLBrute crashes/hangs (number taken from settings in the "Network" block). ~ Success - number of successfully cracked authorizations (shown in real-time, transferred to the overall results file). ~ Crashes - number of crashes in the format: "x1 / i", where: *x1: total number of crashes; *i: number of unique instances where crashes occurred. ~ Hangs - number of hangs in the format: "x1 @ x2 @ x3 / i", where: *x1: hang due to memory access error ("Application Error"); *x2: hang when NLBrute stops auto-saving; *x3: hang due to a broken setting.ini or activation check failure; *i: number of unique instances where hangs occurred (restarted instance is not counted).
Miscellaneous
Show ContentSpoiler:
What is NLBrute_Watch.exe process for? Watcher - this is a copy of the manager, serving one purpose - to monitor the manager. If it is suddenly decided to terminate it from the outside (for any reason), Watcher will ensure the closure of all NLBrute instances and terminate itself.
The numbers "# X" in the NLBrute window titles - denote the instance number, corresponding to the folder number in tools\work\NL_X from which this instance is launched.
Complete hang is detected by the sign: if the results of work have
Download
VT Links
Show ContentSpoiler:
Code: NLBrute_Manager.exe: https://www.virustotal.com/gui/file/6badcd1498647bd5fc54d31b9ff03995daaae055ae7079c4c0387c61fda2806c NLBrute_watch.exe: https://www.virustotal.com/gui/file/6badcd1498647bd5fc54d31b9ff03995daaae055ae7079c4c0387c61fda2806c NLBrute.exe: https://www.virustotal.com/gui/file/a332f863da1709b27b62f3a3f2a06dca48c7dabe6b8db76ec7bb81ce3786e527
fefg
This post is by a banned member (aezakmiii) - Unhide
08 April, 2024 - 07:40 PM
Reply
This post is by a banned member (lamsomi98) - Unhide
09 April, 2024 - 05:00 AM
Reply
This post is by a banned member (VolCoder) - Unhide
OP 09 April, 2024 - 08:35 AM
Reply
|
![[Image: hackerman_xmas.gif]](https://external-content.duckduckgo.com/iu/?u=https%3A%2F%2Fstatic.cracked.io%2Fimages%2Fsmilies%2Fhackerman_xmas.gif)