lupo

module

v1.0.8 Latest Latest Go to latest Published: Sep 5, 2023 License: MIT

Details

Valid go.mod file

The Go module system was introduced in Go 1.11 and is the official dependency management solution for Go.
Redistributable license

Redistributable licenses place minimal restrictions on how software can be used, modified, and redistributed.
Tagged version

Modules with tagged versions give importers more predictable builds.
Stable version

When a project reaches major version v1 it is considered stable.
Learn more about best practices

Repository

github.com/InjectionSoftwareandSecurityLLC/lupo

Links

Open Source Insights

README ¶

lupo

Modular C2 server to tame your pack of wolves.

Current Release

v1.0.8 - Version 1.0.8 Release!

Documentation

v1.0.8 Features:

Support for process injection commands that deliver shellcode payload data and process identifiers for implants to implement (BYOA - Bring your own allocation)
Better multi function hook sample provided in the sample implant directory
Added updateinterval subcommand to Sessions CLI to allow for dynamic updates to implant check-in delays
Added persistence handler updates to all listening modules
Implement data response and check in status intervals
Implement registering custom functions
Consider creating a "color" library in core to handle custom colors across the entire application
Port finished HTTP server to HTTPs
Enhance custom functions
Implement TCP listener
Implement "wolfpack" teamserver with client binary generation
Implement extended functions like upload/download and any other seemingly "universal" switches
Implement a web shell handler for bind web shells
Consider random PSK generation rather than a default base key
Add Exec command to allow local shell interaction while in the Lupo CLI
Reformat the ASCII art so it is printed a bit more cleanly
Document API
Document core features
Create demo implants to show off all the feature/functionality
Repo art update and open source!
Implement config file for lupo server to auto supply configs (done via metasploit-style resource file for simpler automation)
Implement optional encryption flag for TCP
wolfpack chat

v1.0.8 Bug Fixes:

Fixed MAJOR bug in concurrency with writing to maps. Squashed two race conditions that caused C2 server crashes.

Road Map:

Consider Implementing UDP listener (Would be cool to come back to this, it's not hard, just tricky for implants to integrate with cleanly. Needs a seamless standard/API)
Consider Implementing Proxying (Cool for v2 should be easy with a go revproxy lib)
Implement Stager support for things like multi staged implants and DLL injection
Implement Procdump API to support process dumping (can use the stager API)
Web interface for wolfpack server
Implement Github Actions to get automated builds for future releases

Directories ¶

Path	Synopsis
lupo-client main - the "main" package of the application.	main - the "main" package of the application.
cmd Package cmd - the "cmd" package is the core packaged used to reference and manage all grumble integrated commands/features of the application.	Package cmd - the "cmd" package is the core packaged used to reference and manage all grumble integrated commands/features of the application.
core core - the "core" package is used to organize all primary libraries and utilities that are made use of across several aspects of the application.	core - the "core" package is used to organize all primary libraries and utilities that are made use of across several aspects of the application.
lupo-server main - the "main" package of the application.	main - the "main" package of the application.
cmd Package cmd - the "cmd" package is the core packaged used to reference and manage all grumble integrated commands/features of the application.	Package cmd - the "cmd" package is the core packaged used to reference and manage all grumble integrated commands/features of the application.
core core - the "core" package is used to organize all primary libraries and utilities that are made use of across several aspects of the application.	core - the "core" package is used to organize all primary libraries and utilities that are made use of across several aspects of the application.
server server - the "server" package is used to organize all server handler functionality of the application.	server - the "server" package is used to organize all server handler functionality of the application.
sample

?	: This menu
/	: Search site
f or F	: Jump to
y or Y	: Canonical URL