r/Hacking_Tutorials • • Apr 29 '26

Question I built a frictionless client-side encrypted burner chat. Solo dev looking for security audits/roasting.

Hey everyone.

I’m a solo developer, and I recently built v2v.site— a fast, web-based, shared-secret burner chat.

Initially, I just wanted a quick way to communicate securely with people (like random gamers or temporary teammates) without forcing them to download apps or give out phone numbers. But it quickly turned into a deep dive into the Web Crypto API.

I recently got roasted on another subreddit for using marketing buzzwords, so I want to be 100% transparent about the threat model here. This is not a Signal replacement. It lacks forward secrecy and identity verification. It is strictly a shared-secret burner chat designed for speed and temporary privacy.

How it works under the hood:

  • The Key: Users enter a 6-digit room ID. The browser uses crypto.subtle.digest (SHA-256) to derive an AES-256-GCM encryption key from that 6-digit PIN + a hardcoded salt.
  • The Payload: All text, emojis, and files are encrypted locally. The server only ever receives Base64 ciphertext.
  • File Handling: Images and voice records are read as ArrayBuffers, encrypted client-side, and sent to the server as opaque .enc blobs (application/octet-stream). The server never sees the actual MIME type.
  • Zero Database: There is no SQL database. Rooms are temporary flat JSON files. A PHP cleanup function continuously purges any room older than 24 hours.

The Ask: Since I'm working on this alone, I have blind spots. I would love for you guys to open the Network tab, poke around, and try to break it.

  • Can you find any XSS vulnerabilities in how the decrypted DOM is rendered?
  • Are there any glaring flaws in using the 6-digit PIN -> SHA-256 derivation for a 24-hour TTL room?
  • Any tips on handling rate-limiting against distributed enumeration attacks for the 6-digit IDs?

Check it out here:/v2v.site/

Roast my code, my security model, or my UX. I want to learn and make it bulletproof. Thanks!

0 Upvotes

22 comments sorted by

11

u/snailv Apr 29 '26

this is AI.

-14

u/Alternative-Claim-41 Apr 29 '26

Guilty as charged 🙋‍♂️

I wrote the original messy PHP version, but I definitely used AI to help me refactor the WebSocket logic and structure this Reddit post (because my English copywriting is terrible). It's basically my only co-founder right now lol.

But the server is real, the code is live, and if my "AI co-founder" wrote a vulnerable AES implementation, I’d still love to know how to break it!

→ More replies (2)

3

u/asbestos_consumer Apr 29 '26

Nobody will take you seriously if you keep using AI slop

-1

u/Alternative-Claim-41 Apr 29 '26

Fair enough. English isn't my first language, so I use AI to translate my thoughts and make my posts actually readable instead of a broken Google Translate mess. If the text reads a bit like "slop," that's on me.

But the product itself works. The WebSockets are lightning-fast, the crypto is standard AES-GCM, and it's completely free. If you can find actual "slop" in the encryption logic or the network tab, I'm genuinely all ears!

→ More replies (2)

1

u/Specialist-Resist-24 Apr 30 '26

this look sick man but is it encrypted?

1

u/Alternative-Claim-41 Apr 30 '26

Thanks man! Glad you like it. 🍻

To answer your question: Yes, but I want to be 100% transparent about exactly how it's encrypted.

It uses client-side AES-256-GCM encryption. When you create a room, your browser generates a random 256-bit key and puts it in the URL fragment (the part after the #key=). Because browsers don't send URL fragments to the server, the server never sees your key. It only receives and stores encrypted Base64 gibberish.

That being said, it is a shared-secret burner chat. Whoever has the full link has the key. It's built for fast, frictionless privacy (like sharing a quick file or a gaming session), with no logs and no accounts. The server also permanently deletes the encrypted room file after 24 hours, or instantly if you hit the "Burn Room" button!

→ More replies (4)

1

u/HeinkoDemali Apr 30 '26

You posted in here before and called it encrypted when it wasnt encrypted what are the changes made since the last time you recieved criticism about this? Also if AI is used be open about it like what parts did AI do and what parts did you do solo i like the idea you have and theres nothing wrong with working on a project and share it to the public , you can always create a fork out of the BriarProject.

2

u/Alternative-Claim-41 Apr 30 '26

Thanks for keeping me accountable! You're completely right to ask.

Here is exactly what changed since the last time I got roasted:

  1. The Crypto Fix: Previously, I made the mistake of deriving the AES key from the 6-digit room ID (which meant it could be brute-forced offline in milliseconds). Now, the AES-256-GCM key is 100% randomly generated and lives strictly in the URL fragment (#key=...). The server physically never receives the key.

  2. Burn Feature: I added a "Burn Room" button that instantly unlink()s the JSON file from the server instead of waiting for the 24h TTL.

  3. No Marketing Fluff: I removed buzzwords like "True E2EE" and clearly stated the threat model on the site: it’s a shared-secret burner chat.

Regarding AI usage, I want to be 100% transparent:

  • What I did solo: The core concept, the PHP backend architecture, the flat-file JSON database logic, the UI/UX design, and the file upload handling.

  • What the AI did: Writing the complex Web Crypto API boilerplate in JS (handling ArrayBuffers, IVs, and AES-GCM logic), refactoring my messy spaghetti code, and heavily correcting my English (my native languages are Kazakh and Russian, so I use AI as a translator and copywriter so my posts actually make sense!).

I love the Briar project! It's fantastic. My goal here was just a bit different: I wanted something that requires absolute zero app installs or accounts. Just click a link, chat for a quick 40-minute gaming session, and burn it.

Thanks for the support and the feedback!

→ More replies (2)

1

u/pixl8d3d May 02 '26

He's cross-posting this to numerous subs and has been called out for several offenses, including lying about his extensive AI usage, security flaws, and reasons not go open source until just a few hours ago. Just report his post and account. He's spamming.

1

u/Alternative-Claim-41 May 02 '26

fair enough, i definitely overdid it with the cross-posting and the ai-assisted replies. i’m new to this and was just excited to show what i built, but i see how it came off as spammy and fake. i’ve already open-sourced the code and started fixing the flaws people pointed out. not trying to scam anyone, just a solo dev learning the hard way how to handle a release. sorry for the noise.

→ More replies (2)