v2.2.0 · AES-256-GCM-SIV · Argon2id

Encrypt your files.
No accounts. No internet.
No compromise.

Drag a file in. Enter a passphrase. Get an encrypted .vx2 file. Your original is never modified. Nothing leaves your machine.

100%
Safe Rust
0
Network perms
258MB
Peak RAM
4PiB
Max file size
GPL-3.0 Licensed
100% Safe Rust
RFC 8452 (GCM-SIV)
RFC 9106 (Argon2id)
0 critical vulnerabilities

Built for security.
Designed for simplicity.

Nonce-misuse resistant

AES-256-GCM-SIV (RFC 8452) stays secure even if nonce reuse happens. Per-chunk authentication tags catch any tampering.

Memory-hard KDF

Argon2id at 256 MiB / 3 iterations / 4 lanes. GPU and ASIC resistant. Offline brute-force becomes prohibitively expensive.

Streaming, not buffering

Files of any size (up to 4 PiB) stream through 1 MiB chunks. Constant ~258 MB RAM whether you encrypt 1 KB or 1 TB.

Authenticated header

V4 format authenticates the full header (magic, salt, nonce) as AAD on every chunk. Any tampering is detected at the AEAD layer.

Cancel mid-operation

Started encrypting the wrong file? Hit Cancel. The .tmp file is cleaned up and you're back to a clean state in under 50 ms.

Memory hygiene

Every key, plaintext buffer, and intermediate is wrapped in Zeroizing<T>. Secrets are wiped from RAM the moment they go out of scope.

Cross-platform

Windows x64, macOS Universal, Linux x64, and Android 7.0+ (arm64, armv7, x86_64, x86). One Rust core, four platforms.

Atomic writes

Output is written to a .tmp file first, then renamed on success. Kill the process, pull the plug — no partial or corrupted files.

Offline-first Android

Zero internet permissions. Zero storage permissions (uses Storage Access Framework). Your files never leave your device.

Get Neuron Encrypt

Latest release: v2.2.0. Verify the SHA-256 hash in the release notes after download.

Windows
x64 installer + portable
→
macOS
Universal (Intel + Apple Silicon)
→
Linux
x64 static binary
→
Android
APK (Android 7.0+)
→
CLI (cargo install)
cargo install --git https://gitlab.com/theredhacker0345/neuron-encrypt --bin neuron-encrypt-cli

Cryptography you can verify

Every algorithm is cited to its RFC. Every claim is backed by a public audit. No security through obscurity.

Cipher suite

EncryptionAES-256-GCM-SIV
RFC8452
StreamingBE32, 1 MiB chunks
KDFArgon2id (256 MiB / 3 / 4)
Key expansionHKDF-SHA512
RNGOsRng (OS CSPRNG)
FormatVAULTX04 (AAD)

Threat model

Protected against
  • Offline brute-force (Argon2id 256 MiB)
  • Ciphertext tampering (per-chunk GCM-SIV tags)
  • Header tampering (V4 AAD)
  • Nonce reuse (GCM-SIV is misuse-resistant)
  • Truncation, reorder, substitution attacks
  • Plaintext in RAM after use (Zeroizing)
Not protected against
  • Cold-boot / DMA attacks
  • Keyloggers and screen recorders
  • SSD wear-leveling (wipe is best-effort)
  • Weak passphrases (meter is advisory)
  • Metadata (file names, sizes, timestamps)
Full audit: 44 findings, 0 critical, 0 high, 9 medium (all fixed). Read the report ↗

Questions, answered

Can I recover my files if I forget the passphrase?

No. There is no backdoor, no recovery key, no master password. If you forget the passphrase, the files are gone. This is by design — a backdoor that lets you in also lets an attacker in.

Is my passphrase stored anywhere?

No. The passphrase is held in memory only long enough to derive the encryption key via Argon2id, then it's zeroed. It's never written to disk, never sent over the network, never logged.

What's the difference between V2, V3, and V4 formats?

V2 (VAULTX02) — legacy single-shot format, entire file in RAM, ≤1 GiB.
V3 (VAULTX03) — streaming format, 1 MiB chunks, no size limit, header NOT authenticated.
V4 (VAULTX04) — current default, same as V3 but with header authenticated as AAD on every chunk.

All three are readable by v2.1. New encryptions use V4. There is no auto-migration — re-encrypt to upgrade.

Why is the binary not code-signed?

Code signing requires an Authenticode certificate ($200-400/year). This is an open-source project without a budget for that yet. Windows SmartScreen will warn on first install — click "Run anyway". Always verify the SHA-256 hash in the release notes against your download.

How does this compare to VeraCrypt / Cryptomator / 7-Zip?

Neuron Encrypt is file-level (not volume-level like VeraCrypt, not cloud-file like Cryptomator). It uses AES-256-GCM-SIV (nonce-misuse resistant, unlike AES-XTS or AES-CBC), Argon2id (memory-hard, unlike PBKDF2), and authenticates the header (V4 AAD, unlike most tools). See the README for a detailed comparison table.

Is there a CLI?

Yes — neuron-encrypt-cli ships with the desktop build. Supports piping (encrypt -i file.pdf -o - | ssh ...), JSON output for CI/CD, password files, and shell completions.

How do I report a vulnerability?

Do NOT open a public issue. Use the GitLab confidential issue to report privately. We'll acknowledge within 48 hours and work with you on a fix before public disclosure.

What license is it under?

GPLv3 — Copyright (c) 2024–2026 Ubaid ur Rehman. See LICENSE for full text.

Ready to encrypt?

Download Neuron Encrypt and protect your files in under a minute.

Get Neuron Encrypt