Skip to content

Socks

The Socks module attempts to connect to a static target via a Socks (v4/v5) proxy, extract the termination node address and check whether the node belongs to the TOR network.

Socks Request Example

curl -v -L https://api.binaryedge.io/v1/tasks -d '{"type":"scan", "options":[{"targets":["X.X.X.X"], "ports":[{"port":8080, "protocol":"tcp", "modules":["socks"]}]}]}' -H "X-Token:<Token>"

Socks Request Options

These are optional parameters that can alter the behaviour of the module. These options can be inserted into the "config" object on the request.

  • ipv6 - Whether to use IPv6 instead of IPv4
    • "config":{"ipv6":true}

Schema

Socks Event Schema

{
  ...
  "result": {
    "data": {
      "socks4": {
        "state": "string",
        "exit_ip": "string",
        "tor": "boolean",
        "error": {
          "message": "string",
          "code": "string"
        }
      },
      "socks5": {
        "state": "string",
        "exit_ip": "string",
        "tor": "boolean",
        "error": {
          "message": "string",
          "code": "string"
        }
      }
    }
  ...
}

Contents of the fields

  • state - State of the connection to the remote server
  • exit_ip - Exit IP address of the SOCKS server
  • tor - Whether the exit IP address belongs to the list of known TOR nodes or not
  • error - Description of error conditions when connecting to the remote server
    • message - Error message
    • code - Error code

Socks Event Example

{
  ...
  "result": {
    "data": {
      "socks5": {
        "state": "closed",
        "error": {
          "message": "[Errno 104] Connection reset by peer"
        }
      },
      "socks4": {
        "state": "closed",
        "error": {
          "message": "[Errno 104] Connection reset by peer"
        }
      }
    }
  ...
}