this post was submitted on 16 Jan 2026
4 points (100.0% liked)

Cryptography @ Infosec.pub

588 readers
1 users here now

Questions, answers, discussions, and literature on the theory and practice of cryptography

Rules (longer version here)

##Related resources;

founded 2 years ago
MODERATORS
 

I won't spoil the walkthrough of the appalling source code. But it does end like this:

If you’re using X_wallet, you need to move your assets Right. Fucking. Now. to a wallet that isn’t a steaming pile of dogshit.

As always, there's an XKCD to succinctly describe the situation: https://xkcd.com/221

top 3 comments
sorted by: hot top controversial new old
[–] Neptr@lemmy.blahaj.zone 2 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

Very fun (horrifying) read. That fucking extension was probably coded with heavy use of LLM generated code.

[–] litchralee@sh.itjust.works 2 points 2 weeks ago (1 children)

This is an instance where I sincerely hope it was the work of an LLM, for the alternative is even more fearful: someone who knows just enough cryptography to be familiar with using primitives and is able to write code that compiles, but doesn't actually understand one iota of the theory behind modes and constructions.

The thought of this person being somewhere out there, inexorably writing awful code but unlike an LLM has the free will to keep going. It gives me chills.

[–] Neptr@lemmy.blahaj.zone 3 points 2 weeks ago* (last edited 2 weeks ago)

At the very least the source code was available to read. Much of the software world which is proprietary could (and does) have similar awful security. Proprietary code isnt necessarily insecure, just that it is much simpler to call people out on their bs code practices otherwise.