Nefariously Pushing Master


    0.6.5 • Public • Published


    Forward P2P E2E encrypted


    npm i -g hyperforward


    Public connection

    Already having a server (TCP, HTTP, SOCKS, VNC, etc) running in your computer o remotely:

    hyperforward remote
    # Use this temporal public key to connect:
    # 6e7c244099bf7c14314b0e...0fed9c5e22d52a0c0e927c

    Other peers can connect to you using the public key:

    hyperforward local --connect 6e7c244099bf7c14314b0e...0fed9c5e22d52a0c0e927c
    # Ready to use, listening on:

    Now you can use the local as it will be forwarded to remote


    Create named key pair:

    hyperforward keygen lukks
    # Ask a friend to create their key pair:
    hyperforward keygen cristian

    Private connection

    Same as the first example but with specific authorization.

    1. lukks shares the remote server allowing only cristian
    hyperforward remote --key lukks --firewall cristian
    1. cristian creates a local server to receive from lukks
    hyperforward local --key cristian --connect lukks


    hyperforward remote [ip:port] --key [name] --firewall [names or public keys comma separated]
    hyperforward local [ip:port] --key [name] --connect [name or public key]
    hyperforward keygen [name]
    hyperforward add [name] [public_key]
    hyperforward print [name]
    hyperforward ls
    hyperforward rm [name]

    Sharing multiple services

    There is a security limitation: you can only use one key per forward.
    You still reuse a single key (ie. lukks, cristian, etc) to easily set firewalls.

    Let's say you have multiple things going on:

    • HTTP server on:
    • VNC/NoMachine on:
    • SOCKS5 proxy on:
    1. Each service should have their own key pair:
    hyperforward keygen http1
    hyperforward keygen vnc1
    hyperforward keygen proxy1
    1. Normal remote forward each one:

    In this case, only certain people should be able to use the private VNC service.

    hyperforward remote --key http1
    hyperforward remote --key vnc1 --firewall cristian,lukks
    hyperforward remote --key proxy1
    1. Other peers can connect to your services:

    Let's say "lukks" would like to use your VNC (as he's authorized):

    hyperforward local --key lukks --connect vnc1

    Later, anyone would like to use your proxy:

    hyperforward local --connect proxy1


    Code released under the MIT License.


    npm i hyperforward

    DownloadsWeekly Downloads






    Unpacked Size

    20.7 kB

    Total Files


    Last publish


    • lukks