Zeus
NOT MY CODE! Zeus trojan horse - leaked in 2011, I am not the author. This repository is for study purposes only, do not message me about your lame hacking attempts.
Top Related Projects
An API wrapper for Discord written in Python.
Official Discord API Documentation
A multi-function Discord bot
An unofficial .Net wrapper for the Discord API (https://discord.com/)
Java wrapper for the popular chat & VOIP service: Discord https://discord.com
A powerful JavaScript library for interacting with the Discord API
Quick Overview
Zeus is a Python library for interacting with the OpenAI API, specifically designed for generating and managing conversations with AI models like GPT-3.5 and GPT-4. It provides a simple interface for creating chat-based applications and managing conversation history.
Pros
- Easy-to-use interface for interacting with OpenAI's chat models
- Supports conversation history management
- Allows for custom system messages and user prompts
- Integrates well with other Python libraries and frameworks
Cons
- Limited documentation and examples
- Depends on the OpenAI API, which requires an API key and may incur costs
- May not support all features of the OpenAI API
- Relatively new project with potential for bugs or breaking changes
Code Examples
- Creating a simple conversation:
from zeus import Conversation
conversation = Conversation()
response = conversation.chat("Hello, how are you?")
print(response)
- Using a custom system message:
from zeus import Conversation
system_message = "You are a helpful assistant that speaks like Shakespeare."
conversation = Conversation(system_message=system_message)
response = conversation.chat("Tell me about the weather.")
print(response)
- Managing conversation history:
from zeus import Conversation
conversation = Conversation()
conversation.chat("What's the capital of France?")
conversation.chat("And what about Germany?")
print(conversation.history)
Getting Started
To get started with Zeus, follow these steps:
-
Install the library using pip:
pip install zeus-ai -
Set up your OpenAI API key as an environment variable:
export OPENAI_API_KEY=your_api_key_here -
Create a simple script to test the library:
from zeus import Conversation conversation = Conversation() response = conversation.chat("Tell me a joke.") print(response) -
Run the script and enjoy your conversation with the AI!
Competitor Comparisons
An API wrapper for Discord written in Python.
Pros of discord.py
- More active development and larger community support
- Comprehensive documentation and extensive examples
- Robust feature set for Discord bot development
Cons of discord.py
- Steeper learning curve for beginners
- Larger codebase, potentially more complex for simple bots
Code Comparison
Zeus:
@zeus.command()
async def hello(ctx):
await ctx.send("Hello, World!")
discord.py:
@bot.command()
async def hello(ctx):
await ctx.send("Hello, World!")
The code comparison shows that both libraries use similar syntax for defining commands, making it relatively easy to switch between them if needed. However, discord.py offers more advanced features and customization options for complex bot development.
Zeus is a lightweight alternative to discord.py, focusing on simplicity and ease of use. It may be more suitable for small projects or beginners looking to create basic Discord bots quickly. On the other hand, discord.py provides a more comprehensive set of tools and features for building advanced Discord bots, making it the preferred choice for larger projects and experienced developers.
While Zeus offers a simpler approach, discord.py's extensive documentation, active community, and broader feature set make it a more versatile option for long-term bot development and maintenance.
Official Discord API Documentation
Pros of discord-api-docs
- Comprehensive documentation for Discord's API, including endpoints, rate limits, and best practices
- Regularly updated to reflect the latest changes and features in Discord's API
- Collaborative effort with contributions from Discord staff and community members
Cons of discord-api-docs
- Focused solely on Discord API documentation, lacking implementation examples or tools
- May require additional resources for practical application and development
Code comparison
While a direct code comparison is not relevant in this case, here's an example of how the two repositories differ in content:
discord-api-docs:
## Get Channel
GET /channels/{channel.id}
Returns a channel object.
Zeus:
class Channel(models.Model):
name = models.CharField(max_length=100)
description = models.TextField(blank=True)
Summary
discord-api-docs is a comprehensive documentation repository for Discord's API, providing detailed information for developers working with Discord's platform. Zeus, on the other hand, appears to be a Django-based project with models and functionality unrelated to Discord's API documentation. The repositories serve different purposes and are not directly comparable in terms of functionality or content.
A multi-function Discord bot
Pros of Red-DiscordBot
- More active development and larger community support
- Extensive documentation and user guides
- Modular design with a wide range of available cogs (plugins)
Cons of Red-DiscordBot
- Steeper learning curve for beginners
- Requires more system resources due to its comprehensive feature set
Code Comparison
Red-DiscordBot:
@commands.command()
async def ping(self, ctx):
"""Pong."""
start = time.perf_counter()
message = await ctx.send("Ping...")
end = time.perf_counter()
await message.edit(content=f"Pong! {(end - start) * 1000:.2f}ms")
Zeus:
@bot.command()
async def ping(ctx):
await ctx.send('Pong!')
Red-DiscordBot offers a more sophisticated ping command with latency measurement, while Zeus provides a simpler implementation. This reflects the overall difference in complexity and feature richness between the two projects.
Red-DiscordBot is a more comprehensive and feature-rich Discord bot framework, suitable for advanced users and complex bot implementations. Zeus, on the other hand, appears to be a simpler, more lightweight alternative that may be easier for beginners to get started with but offers fewer built-in features and less community support.
An unofficial .Net wrapper for the Discord API (https://discord.com/)
Pros of Discord.Net
- More comprehensive and feature-rich Discord API wrapper
- Larger community and better documentation
- Actively maintained with frequent updates
Cons of Discord.Net
- Steeper learning curve for beginners
- Larger codebase and potentially more complex implementation
- May include unnecessary features for simple bot projects
Code Comparison
Zeus (Python):
@client.event
async def on_message(message):
if message.content.startswith('!hello'):
await message.channel.send('Hello!')
Discord.Net (C#):
[Command("hello")]
public async Task HelloCommand()
{
await ReplyAsync("Hello!");
}
Zeus is a simpler Python-based Discord bot framework, while Discord.Net is a more comprehensive C# library for Discord bot development. Zeus offers a more straightforward approach for basic bot functionality, making it easier for beginners to get started. However, Discord.Net provides a more robust set of features and better scalability for larger projects. The code comparison shows that Zeus uses event-based programming, while Discord.Net utilizes a command-based structure, reflecting the different design philosophies of the two libraries.
Java wrapper for the popular chat & VOIP service: Discord https://discord.com
Pros of JDA
- More active development with frequent updates and bug fixes
- Extensive documentation and examples for easier implementation
- Larger community support and wider adoption among Discord bot developers
Cons of JDA
- Steeper learning curve due to more complex API
- Requires more setup and configuration compared to Zeus
- Higher memory usage, especially for larger bot implementations
Code Comparison
Zeus (Python):
@bot.command()
async def hello(ctx):
await ctx.send('Hello, World!')
JDA (Java):
public class HelloCommand extends ListenerAdapter {
@Override
public void onMessageReceived(MessageReceivedEvent event) {
if (event.getMessage().getContentRaw().equals("!hello")) {
event.getChannel().sendMessage("Hello, World!").queue();
}
}
}
Zeus offers a more concise syntax for simple commands, while JDA provides more granular control over event handling and message processing. JDA's approach allows for more complex bot behaviors but requires more boilerplate code.
Both libraries serve their purpose well, with Zeus being more suitable for quick prototyping and simpler bots, while JDA is better suited for larger, more complex Discord bot projects that require fine-grained control and scalability.
A powerful JavaScript library for interacting with the Discord API
Pros of discord.js
- Larger community and more active development
- Extensive documentation and examples
- Broader feature set for Discord bot development
Cons of discord.js
- Steeper learning curve for beginners
- Potentially more complex setup for simple bots
- Larger package size and dependencies
Code Comparison
Zeus (Python):
@bot.command()
async def hello(ctx):
await ctx.send('Hello!')
discord.js (JavaScript):
client.on('message', message => {
if (message.content === '!hello') {
message.channel.send('Hello!');
}
});
Key Differences
- Zeus is written in Python, while discord.js is a JavaScript library
- Zeus uses a command decorator approach, discord.js uses event listeners
- Zeus is more lightweight and focused on simplicity
- discord.js offers more advanced features and customization options
Use Cases
- Zeus: Ideal for small, simple Discord bots or for Python developers
- discord.js: Better suited for complex bots, large-scale projects, or JavaScript developers
Community and Support
- Zeus: Smaller community, less frequent updates
- discord.js: Large, active community with regular updates and extensive third-party resources
Learning Curve
- Zeus: Easier to get started for Python developers or beginners
- discord.js: Requires more JavaScript knowledge but offers more advanced capabilities
Convert 
designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual CopilotREADME
This is version 2.0.8.9 downloaded from http://www.mdl4.com/2011/05/download-zeus-source-code/
This repository doesn´t contain my code I have uploaded it to GitHub to simplify the process of getting/analysing the code.
Third paragraph:
Setting up the bot Step by step installation:
- From your existing package assembly, run 'local \ cp.exe', is a builder and bot file konifguratsii
- Open the 'Builder'. Click 'Browse' and select the configuration file there, the name of MDM 'local \ config.txt'.
- Click 'Edit config', as a result should start a text editor. Migrate the file like this:
First: The source configuration file is a text file encoding in Windows, and is needed to create the final configuration file (which is a binary file to download bot) and the bot. In your package assembly sample configuration file must be located in the folder 'local' and be named config.txt. You can open the file in a text editor such as 'Notepad' (Notepad).
The file consists of records, one record per line. Recording is composed of parameters, the first parameter is the name commonly write (but not always, such as in cases when there is any data transfer, no name). The parameters are separated by spaces, if the parameter is found in the space, or a tab, this option must be enclosed in double quotes ("), the same rule applies to the name. Unlimited number of parameters, and if the record has a name, it read insensitive Examples: username Kot Matroskin recording name - username, option 1 - Kot, option 2 - Matroskin.
username "James" Bond " recording name - username, option 1 - James, option 2 - Bond.
username "Volodia Putin" recording name - username, option 1 - Volodia Putin.
"Url" "http://example.com/" index.php recording name - url, option 1 - http://example.com/, option 2 - index.php
Also there are special names of entries that allow you to share the configuration file you want as far as sub-sections, which can contain within itself any number of sub-sections and records. They are called sections and consist of a name and a parameter determining the entry section name (case is also not taken into account in this parameter), the end of the same section, indicated by entering end. The documentation, nesting record in relation to sub-sections will be designated by ->. That is, Entries named username owned section userdata, will be designated as the userdata-> username, etc.
Examples: entry "userdata" fname "petia" lname "lolkin" end
entry compdata name "pcvasya" entry devices - the contents of this section, an example of when the record does not have a name, there is a listing of devices. cdrom "Hdd" fdd end end
Also, you can insert comments, comments must be in a separate line, and start with a ';'. If it turns out that the first parameter in the record, too, begins with a ';', this parameter must be enclosed in quotation marks.
Examples: ; Hello.I think that I'm hero! ; How are you /-it does not record "; I love you" - and here it is already recording.
Second: Configuration File Entries The file consists of two sections StaticConfig and DynamicConfig.
StaticConfig, the values ââprescribed in this section directly to the bot file, ie in exe, and define the basic behavior of the bot on a victim's computer. Depending on your build, some details may not have value for you, all the significant parameters prescribed in the example that came with the package assembly. botnet [string] - specifies the name of a botnet, which owns the boat. string - the name of a botnet to 4 characters, or 0 - for the default value.
Recommended value: botnet 0
timer_config [number1] [number2] - determines the intervals through which to receive updatings configuration file. number1 - Specifies the time in minutes through which to update the configuration file, if successful boot last time. number2 - Specifies the time in minutes through which to update the configuration file, in case of an error when loading the previous time.
Recommended value: timer_config 60 5
timer_logs [number1] [number1] - determines the intervals through which to send the accumulated logs to the server. number1 - Specifies the time in minutes through which to send the logs, in cases successfully sent last time. number2 - Specifies the time in minutes through which to send the logs, in case of an error in sending previous time.
Recommended value: timer_logs February 2
timer_stats [number1] [number2] - determines the intervals through which to send statistics to the server. (Includes inastally, finding in the online, open ports, services, socks, screenshots, etc.) number1 - Specifies the time in minutes through which to send the statistics, in cases successfully sent last time. number2 - Specifies the time in minutes through which to send the statistics, in the case of an error in sending previous times.
Recommended value: timer_logs 20 10
url_config [url] - URL that is located on the main configuration file, this is the most important parametor if the infection kompyuetra victim on a URL will not be available this configuration, the infection does not make sense.
url_compip [url] [number] - specifies the site where you can check your IP, is used to determine the NAT. url - specifies the URL of the web number - Specifies the kolichetsvo bytes that enough to swing from the site to see in the downloaded your IP.
blacklist_languages ââ[number1] [number2] ... [chisloX] - specifies a list of language codes Windows, for which the bot will always spyashem is in Safe Mode, ie it will not send the logs and statistics, but will appeal to the configuration file. chisloX - language code, for example RU - 1049, EN - 1033.
DynamicConfig, the values ââprescribed in this section, the final configuration file. Depending on your build, some details may not have value for you, all the significant parameters prescribed in the example that came with the package assembly. url_loader [url] - specifies the URL, which you can download the update bot. This option is relevant only if you are running the botnet new version of the bot and prescribed configuration of him for the same URL, as the old configuration, in which case the old version of the bot will start to upgrade by downloading the file specified in this record.
url_server [url] - specifies the URL, which will be sent to statistics, files, logs, etc. from the computers of victims.
file_webinjects - defines a local file, which is a list of web izhektov. Description of the format of this file can be found here
Subsection AdvancedConfigs - enumerates a list of the URL, which you can download a backup configuration file, in the cases of the inaccessibility of the main file. It is recommended to fill this subsection 1-3 URL, which will save the botnet from death in cases of unavailability of the main configuration file, and the result is easy to transfer it to another server. Required files exist on this URL is not required, then the main thing to be able to place the files on this URL. Files should be mixed there only after the discovery of the main configuration file is not available, but if you ever want to have the files on this URL, you should update them all in sync with the main configuration file. The backup files can not not be distinguished from the core, and are created in the same way.
Example: entry "AdvancedConfigs" "Http://url1/cdffd.ccc" "Http://url2/cdf34.dc" end
Subsection WebFilters - has two purposes: enumerates a list of masks URL, which should be written down or removed from the log, regardless of the type of request (GET, POST). If the first character of the mask is a '!', Then the coincidence of the URL with this mask, the entry in the log will not be produced (eg mask! "*" Will ban entry of URL, except those listed before it). The mask URL, at the beginning of treatment which will sozdavatsya screenshots of pressing the left mouse button (useful for bypassing the virtual keyboard). This mask URL should begin with the character '@'. Note: URL listed in this section, the value is ignored StaticConfig.ignore_http
Example: entry "WebFilters" , The log will be written by all the URL matching with this mask. "Http://www.google.com/ *" , The log will be written all the URL matching with this mask. "! Http:// * yahoo.com / *" And after the opening of this page will be created in the screenshots click the left mouse button. "@ Http://www.rambler.ru/" end
Subsection WebFakes - enumerates a list of transparent URL-redirects (fake) sites, a detailed description of this topic can be found here
Subsection TanGrabber - determine the rules for TAN-grabber, a detailed description of this topic can be found here
Subsection DnsMap - DNS list of changes to be made in the file% system32% \ drivers \ etc \ hosts. Recording format: [IP] [domain]. IP - the new IP domain. domain - the domain name for which changes IP. If the domain name begins with a '!', This domain will have Dalen from the file, of course if it is found there. The value of IP and can be ignored by anyone.
Example: entry "dnsmap" 127.0.0.1 microsoft.com 192.168.0.1 google.com 0.0.0.0! Yahoo.com end Third:) Then save the file.
== END of original Readme ====
This bot source only includes the bot generator and not the installer or the web server "Control Center". For more Information look for Ice IX
Top Related Projects
An API wrapper for Discord written in Python.
Official Discord API Documentation
A multi-function Discord bot
An unofficial .Net wrapper for the Discord API (https://discord.com/)
Java wrapper for the popular chat & VOIP service: Discord https://discord.com
A powerful JavaScript library for interacting with the Discord API
Convert designs to code with AI
Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.
Try Visual Copilot