⚠️ Nemo has now been discontinued, as I simply lack the resources to continue development on this project. Apologies!

Forks are always welcome, however :)

A Remote Access Tool & Post-Exploitation Framework

Introduction

Nemo is yet another post-exploitation framework, focused around collaboration. Collaboration among multiple operators is managed by a "swarm", which can be remotely managed from the command and control. Payloads are not dynamically generated; nemo is not intended to be used in production. Do keep in mind that I'm fairly new to malware dev, and this is just one of those shower thought projects that magically came to life.

Installation & Usage

Nemo consists of a number of components, namely:

• client - A CLI shell utility to manage payloads and communicate with operators. The main interface you will be interacting with.
• server - The remote command and control server (a websocket API server) which will be the main access point into the payloads. The daemon usually manages the server.
• daemon - The primary access point for the CLI to communicate with the server; acts as an API client.
• payload - Payload generation scripts and templates. These are the payloads that are slightly modified during generation.

Built With

Heavily inspired by Havoc, you should check it out :)