🍣Sushi Train Overview

Welcome to the documentation for Sushi Train. This documentation will tell you how to setup Sushi Train and get started with using it.

What is Sushi Train?

Sushi Train is essentially a fancy web server that sits behind redirectors and serves some kind of content to incoming requests. The redirectors define specific paths that should be forward to Sushi Train, then Sushi Train looks at the incoming request and decides what kind of response to send. Sushi Train itself is never directly target facing.

What can I use Sushi Train for?

Serving any type of content or payload you want in a controlled and managed way. Typically Sushi Train is used for things like hosting phishlng payloads or implant stagers. However, it is really up to your imagination what you want to use it for.

Why use Sushi Train?

Sushi Train provides granular policies that you can use to control access to content you want to serve. Sushi Train also has a modular payload system you can use to create highly dynamic payloads.

The management interface of Sushi Train is designed from the ground up to be "multiplayer friendly" and is intended to allow multiple operators to work together to manage redirectors and payloads.

Additionally, Sushi Train makes it significantly easier to manage large numbers of redirectors and payloads in one place. Even if you only want to serve simple static payloads you have generated elsewhere, Sushi Train can ease the pain of doing this on a larger scale.