Dev.to Security 🔐 Cybersecurity 👁 0 📖 2 min read

Why I Built ZeroTrace-Vault: A Zero-Knowledge Ephemeral Secret Sharing Tool with WebCrypto

Every day, developers and DevOps engineers share database passwords, SSH keys, and API tokens across Slack, Microsoft Teams, WhatsApp, and email. We treat these platforms like temporary scratchpads, but in reality, they

Every day, developers and DevOps engineers share database passwords, SSH keys, and API tokens across Slack, Microsoft Teams, WhatsApp, and email.

We treat these platforms like temporary scratchpads, but in reality, they are permanent, indexed, searchable databases.

During the infamous Uber 2022 breach, an attacker compromised the entire corporate infrastructure simply by searching Slack for AWS_SECRET_ACCESS_KEY. The credentials had been sitting there in plaintext for months.

Why Existing Pastebins Fall Short

Most pastebin and "secret sharing" tools either encrypt on the server side or hold plaintext credentials in memory. If the server is seized, a database dump is leaked, or a cloud provider goes rogue, all secrets are exposed.

To solve this, I built ZeroTrace-Vault — an open-source, mathematical Zero-Knowledge secret sharing engine.

🔐 The Mathematical Zero-Knowledge Architecture

The core philosophy of ZeroTrace-Vault is simple: Even the server hosting the application physically cannot read the secrets.

Here is how the cryptographic lifecycle works:

Client-Side AES-GCM-256: When you type a secret, your browser generates a cryptographic 256-bit AES-GCM key locally via the native WebCrypto API.
RFC 3986 URL Hash Key Isolation: The secret is encrypted before sending anything to the server. The encryption key is appended to the URL fragment (# anchor): https://vault.domain.com/v/{UUID}#{EncryptionKey}
Zero Wire Exposure: According to RFC 3986 specifications, web browsers never transmit the hash fragment (#...) in HTTP requests. The server only stores the ciphertext and 96-bit IV. The key never touches the server's disk, RAM, or logs.
Atomic Burn-on-Read: Once the recipient opens the link, the browser fetches the ciphertext, decrypts it locally using the key in the hash fragment, and triggers an atomic memory shred on the database. Any secondary visit returns a permanent 404 Purged.
Anti-Crawler Shield: Preview bots (Slackbot, Discord, WhatsApp) hitting the link won't prematurely burn your secret before the real person opens it.
💻 Try It Out (Live Demo & Source Code)

I have deployed a live instance and open-sourced the entire project:

🌐 Live Demo: https://zerotrace-vault.onrender.com
📂 GitHub Repository: https://github.com/Atulkumar5772/ZeroTrace-Vault

It also includes a lightweight Docker container for self-hosting and a direct Linux CLI tool (cat id_rsa | zerotrace) for terminal pipelines.

💬 Looking for Your Feedback!

As a student developer passionate about cryptography and systems engineering, I'd love to hear your thoughts:

How does the WebCrypto implementation look to you?
What features would you like to see in a self-hosted secret vault?

🌟 If you find this project useful or support open-source privacy tooling, please consider giving ZeroTrace-Vault a star ⭐ on GitHub! It really helps independent developers get discovered.

📰 Read the original article on Dev.to Security

Originally published by Dev.to Security. Aggregated on AIWithGhost for educational purposes — full credit and traffic to the original publisher.