Hiddenden/beef
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix typos

Browse Source
This commit is contained in:
zinduolis
2025-11-10 20:39:51 +10:00
parent 582c4d67e3
commit cc862ae82f
20 changed files with 30 additions and 30 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
modules/ipec/inter_protocol_posix_bindshell/module.rb
View File

@@ -48,7 +48,7 @@ class Inter_protocol_posix_bindshell < BeEF::Core::Command
{ 'name' => 'ip', 'ui_label' => 'Target Address', 'value' => 'localhost' },
{ 'name' => 'port', 'ui_label' => 'Target Port', 'value' => '4444' },
{ 'name' => 'command_timeout', 'ui_label' => 'Timeout (s)', 'value' => '30' },
{ 'name' => 'cmd', 'ui_label' => 'Shell Commands', 'description' => 'Enter shell commands to execute. Note: the semicolons are required to seperate commands', 'type' => 'textarea',
{ 'name' => 'cmd', 'ui_label' => 'Shell Commands', 'description' => 'Enter shell commands to execute. Note: the semicolons are required to separate commands', 'type' => 'textarea',
'value' => 'echo ID: ; id', 'width' => '200px' },
{ 'name' => 'result_size', 'ui_label' => 'Result Size', 'description' => 'Expected maximum size of the result in bytes', 'value' => '1024' }
]

2
modules/ipec/inter_protocol_redis/config.yaml
View File

@@ -9,7 +9,7 @@ beef:
enable: true
category: "IPEC"
name: "Redis"
description: "Using Inter-Protocol Exploitation/Communication (IPEC) the hooked browser will send commands to a listening Redis daemon on the target specified in the 'Target Address' input field.<br/><br/>The target address can be on the hooked browser's subnet which is potentially not directly accessible from the Internet.<br/><br/>The results of the Redis commands are not returned to BeEF.<br/><br/>Note: Use '\\n' to seperate Redis commands and '\\\\n' for new lines."
description: "Using Inter-Protocol Exploitation/Communication (IPEC) the hooked browser will send commands to a listening Redis daemon on the target specified in the 'Target Address' input field.<br/><br/>The target address can be on the hooked browser's subnet which is potentially not directly accessible from the Internet.<br/><br/>The results of the Redis commands are not returned to BeEF.<br/><br/>Note: Use '\\n' to separate Redis commands and '\\\\n' for new lines."
authors: ["bcoles"]
target:
working: ["FF", "C"]

2
modules/ipec/inter_protocol_redis/module.rb
View File

@@ -10,7 +10,7 @@ class Inter_protocol_redis < BeEF::Core::Command
{ 'name' => 'rhost', 'ui_label' => 'Target Address', 'value' => '127.0.0.1' },
{ 'name' => 'rport', 'ui_label' => 'Target Port', 'value' => '6379' },
{ 'name' => 'timeout', 'ui_label' => 'Timeout (s)', 'value' => '15' },
{ 'name' => 'commands', 'ui_label' => 'Redis commands', 'description' => "Enter Redis commands to execute. Note: Use '\\n' to seperate Redis commands and '\\\\n' for new lines.",
{ 'name' => 'commands', 'ui_label' => 'Redis commands', 'description' => "Enter Redis commands to execute. Note: Use '\\n' to separate Redis commands and '\\\\n' for new lines.",
'type' => 'textarea', 'value' => cmd, 'width' => '200px' }
]
end

2
modules/ipec/inter_protocol_win_bindshell/config.yaml
View File

@@ -9,7 +9,7 @@ beef:
enable: true
category: "IPEC"
name: "Bindshell (Windows)"
description: "Using Inter-Protocol Exploitation/Communication (IPEC) the hooked browser will send commands to a listening Windows shell bound on the target specified in the 'Target Address' input field.<br/><br/>The target address can be on the hooked browser's subnet which is potentially not directly accessible from the Internet.<br/><br/>The results of the commands are not returned to BeEF.<br/><br/>Note: ampersands are required to seperate commands."
description: "Using Inter-Protocol Exploitation/Communication (IPEC) the hooked browser will send commands to a listening Windows shell bound on the target specified in the 'Target Address' input field.<br/><br/>The target address can be on the hooked browser's subnet which is potentially not directly accessible from the Internet.<br/><br/>The results of the commands are not returned to BeEF.<br/><br/>Note: ampersands are required to separate commands."
authors: ["bcoles", "wade"]
target:
working: ["FF", "C"]

2
modules/ipec/inter_protocol_win_bindshell/module.rb
View File

@@ -15,7 +15,7 @@ class Inter_protocol_win_bindshell < BeEF::Core::Command
{ 'name' => 'rhost', 'ui_label' => 'Target Address', 'value' => '127.0.0.1' },
{ 'name' => 'rport', 'ui_label' => 'Target Port', 'value' => '4444' },
{ 'name' => 'timeout', 'ui_label' => 'Timeout (s)', 'value' => '30' },
{ 'name' => 'commands', 'ui_label' => 'Shell Commands', 'description' => 'Enter shell commands to execute. Note: ampersands are required to seperate commands', 'type' => 'textarea',
{ 'name' => 'commands', 'ui_label' => 'Shell Commands', 'description' => 'Enter shell commands to execute. Note: ampersands are required to separate commands', 'type' => 'textarea',
'value' => 'echo User: & whoami & echo Directory Path: & pwd & echo Directory Contents: & dir & echo HostName: & hostname & ipconfig & netstat -an', 'width' => '200px' }
]
end

12
modules/ipec/s2c_dns_tunnel/command.js
View File

@@ -5,14 +5,14 @@
//
/*
This JavaScript retreives data from a server via DNS covert channel.
This JavaScript retrieves data from a server via DNS covert channel.
A remote controlled domain with a custom DNS server implementing covert channel logic is required.
BeEF supports this feature via Server-to-Client DNS Tunnel extension.
The initial concept of the DNS covert channell and its implementation are described in the following literature:
The initial concept of the DNS covert channel and its implementation are described in the following literature:
- K.Born. Browser-Based Covert Data Exfiltration. http://arxiv.org/ftp/arxiv/papers/1004/1004.4357.pdf
- W. Alkorn,C. Frichot, M.Orru. The Browser Hacker's Handbook. ISBN-13: 978-1118662090, ISBN-10: 1118662091
- W. Alcorn,C. Frichot, M.Orru. The Browser Hacker's Handbook. ISBN-13: 978-1118662090, ISBN-10: 1118662091
*/
beef.execute(function() {
@@ -29,7 +29,7 @@ beef.execute(function() {
var bit_transfered = new Array();
var timing = new Array();
// Do the DNS query by reqeusting an image
// Do the DNS query by requesting an image
send_query = function(fqdn, msg, byte, bit) {
var img = new Image;
var fport = "";
@@ -51,7 +51,7 @@ beef.execute(function() {
}
};
// Construct DNS names based on Active Directory SRV resource records pattern and resolv them via send_query function
// Construct DNS names based on Active Directory SRV resource records pattern and resolve them via send_query function
// See http://technet.microsoft.com/en-us/library/cc961719.aspx
function get_byte(msg, byte) {
bit_transfered[msg][byte] = 0;
@@ -71,7 +71,7 @@ beef.execute(function() {
}
}
// Construct random sring
// Construct random string
function getRandomStr(n){
return Math.random().toString(36).slice(2, 2 + Math.max(1, Math.min(n, 12)));
}

2
modules/ipec/s2c_dns_tunnel/config.yaml
View File

@@ -9,7 +9,7 @@ beef:
enable: true
category: "IPEC"
name: "DNS Tunnel: Server-to-Client"
description: "This module retreives data sending by server over DNS covert channel (DNS tunnel).<br/><br/> A payload name and message are taken as input. The message is sent as a bitstream, decoded, and then can be accessed via Window object property specified in payload name parameter.<br/><br/>Note: To use this feature you should enable S2C DNS Tunnel extension."
description: "This module retrieves data sent by the server over DNS covert channel (DNS tunnel).<br/><br/> A payload name and message are taken as input. The message is sent as a bitstream, decoded, and then can be accessed via Window object property specified in payload name parameter.<br/><br/>Note: To use this feature you should enable S2C DNS Tunnel extension."
authors: ["dnkolegov"]
target:
working: "All"