Security usually feels like a static, boring wall. I wanted to build something different—something active.
I’m excited to share CyberFuck, a project where I combined synthwave aesthetics, custom-built esoteric interpreters, and active-defense honeypot logic to create a "Vault" that doesn't just store your secrets—it traps anyone trying to steal them.
The "Why"
Most encryption tools are passive. You store a file, and it sits there, waiting to be brute-forced. I wanted to explore "active defense." What if your data could fight back? What if the encryption itself was proprietary enough that standard tools couldn't even parse it?
The Tech Stack
Backend: Node.js + Express (wrapped for Serverless deployment).
The Engine: A custom-built Brainfuck interpreter that uses a proprietary dialect.
Frontend: HTML5/CSS3 with Glassmorphism, custom local typography, and pixel-art video loops for that 90s hacker movie vibe.
Deployment: Render for the backend/serverless functions.
The Secret Sauce: Proprietary Obfuscation
The heart of CyberFuck is a custom Brainfuck dialect. Because standard Brainfuck interpreters are open-source and common, they are useless for security.
By engineering my own mathematical offset algorithms and a hidden "Auth-Signature," I’ve ensured that no standard interpreter on the web can parse these files. If a snooper tries to run a CyberFuck vault through a generic interpreter, they’ll get nothing but syntax errors or corrupted gibberish.
How it works (The Honeypot)
The vault uses a "Signature Verification" method:
Auth Check: Before the data is output, the interpreter checks for a specific "Auth-Signature."
The Trap: If you provide the wrong 4-character PIN, the interpreter fails the signature check. Instead of "failing quietly," it triggers a WEBHOOK TRIGGERED alert, logging the breach attempt and neutralizing the data output to prevent further brute-forcing.
Challenges Faced
The biggest technical hurdle was memory management. Building a Brainfuck interpreter from scratch in JavaScript meant handling potential infinite loops. I had to implement strict execution limits to ensure that even if someone feeds the vault malicious, corrupted code, the server stays up and the system remains stable.
Give it a spin
If you’re interested in esoteric security, check out the repo and try to break the vault yourself!
Try the live app:
I’m looking for feedback on the honeypot logic—does anyone see a way to bypass the signature check without the correct key?
If you enjoyed this, feel free to give the repo a star on GitHub! I'm constantly tweaking the offset algorithms to make the encryption even harder to reverse-engineer.
SOCIAL SHARE CARD GENERATOR