Why Choose Plugin Encryptor?

AES-256 Encryption

Military-grade security that keeps your plugins safe from decompilation and theft

Zero Performance Impact

Optimized encryption that doesn't slow down your server or affect gameplay

FTP-SSL Support

Secure file transfer with automated deployment to your Rust server

Beta · Untested

Carbon Framework

Experimental loader for the Carbon modding framework — not yet tested in production.

Stable

Oxide / uMod

Fully tested and compatible with the classic Oxide and uMod frameworks.

LZMA Compression

Advanced compression to reduce file sizes without compromising security

Choose Your Plan

Start free, upgrade when you need more

Free

For testing and small projects

Download & Get Started

5 plugin encryptions

LZMA & custom support

AES-256 encryption

Carbon & Oxide support

⭐ Recommended

Premium

For professional server owners

$50 /year

Unlimited plugin encryptions

LZMA & custom support

AES-256 encryption

FTP-SSL support

Priority updates

Carbon & Oxide support

24/7 Support

Supports both desktop and CLI via REST API

All plans include support for Carbon and Oxide frameworks

Secure payments via

Protect Your Investment

Stop worrying about plugin theft and unauthorized distribution. Plugin Encryptor gives you complete control over your custom Rust server plugins.

→

Prevent Decompilation Keep your source code protected from reverse engineering

→

Control Distribution Only authorized servers can run your plugins

→

Both Frameworks Supported Works seamlessly with Carbon and Oxide/uMod

How to Install

Get your encrypted plugins running in minutes

For Plugin Vendors

Step 1

Download & Register

Download PluginEncryptor.exe from this page. Launch it and create your account. Your encryption keys are generated automatically.

Step 2

Encrypt Your Plugins

Select your .cs plugin files, choose an output folder and click Encrypt. You'll get .csenc files.

Step 3

Distribute

Send the .csenc files to your customers. They can't read the source — only servers with the loader can run them.

For Server Owners

Carbon Server

1. Download CarbonEncryptedPlugins.dll from this page
2. Place it in your server's RustDedicated_Data/Managed/ folder
3. Put .csenc plugin files in carbon/plugins/
4. Restart the server — plugins load automatically

Oxide / uMod Server

1. Download Oxide.EncryptedPlugins.dll from this page
2. Place it in your server's RustDedicated_Data/Managed/ folder
3. Put .csenc plugin files in oxide/plugins/
4. Restart the server — plugins load automatically

Note

The loader requires an active internet connection to decrypt plugins. It contacts our API to securely decrypt each plugin on server startup. No encryption keys are stored on your server.

Ready to Secure Your Plugins?

Join hundreds of Rust server owners protecting their custom plugins with military-grade encryption.

Frequently Asked Questions

Everything you need to know about encrypting Rust server plugins.

What is Plugin Encryptor for Rust?

Plugin Encryptor is a security tool that converts your Rust server C# plugins (.cs) into encrypted .csenc files. It uses AES-256 encryption and HWID-locked vendor keys so your plugins cannot be stolen, reverse engineered, or redistributed without permission.

Does it work with Oxide and uMod?

Yes. The Oxide / uMod loader (Oxide.EncryptedPlugins.dll) is stable and production-tested. Drop it into oxide/extensions/, place your .csenc files in oxide/plugins/, restart the server and it works identically to classic .cs plugins.

Does it work with Carbon framework?

Carbon support is currently in beta. The CarbonEncryptedPlugins.dll loader is available for download but has not yet been tested in production. Use it at your own risk until the stable release.

What is the .csenc file format?

.csenc is an encrypted container format for Rust plugins. The C# plugin source is compressed with LZMA, encrypted with AES-256 using a vendor-specific key, and wrapped in a header that the loader validates at runtime before decrypting in memory.

Can encrypted plugins be reverse-engineered?

The loaders are obfuscated with ConfuserEx and the vendor keys are fetched via HTTPS from the licensing server at runtime — never stored on the game server. Plugin bytes exist decrypted only inside the Rust process memory, making static extraction impractical.

Does encryption slow down my Rust server?

Decryption happens once per plugin at load time. After that plugins run as normal compiled C# with zero runtime overhead. Server performance is identical to regular Oxide / Carbon plugins.

Will my plugins break after a server restart?

No. On every restart the loader re-fetches the vendor key over HTTPS (TLS 1.2+), validates your HWID and server fingerprint, then decrypts the plugins. As long as your license is active, everything reloads automatically.

Does it run on Linux Rust servers?

Yes. Both loaders target .NET Framework 4.8.1 and run on the Mono runtime used by Linux Rust dedicated servers. TLS 1.2 is enforced in the loader so Mono connects to the licensing API without certificate issues.

How does HWID and server locking work?

When a plugin is first loaded, the loader sends the server hostname, port, max players, map and OS to the licensing API. The vendor key returned is bound to that fingerprint — if the plugin is copied to a different machine, decryption fails silently.

What do I need to get started?

Download the Plugin Encryptor Windows app, create an account, buy a Pro license via Stripe, then encrypt your .cs plugins into .csenc. Place the appropriate loader (Oxide or Carbon) in your server and drop the .csenc plugins in the plugins folder. Done.

Plugin Encryptor

Protect Your Plugins