Hey hackers, here's a trivial ransomware idea 1) Come up with a cool looking Nostr client, investing money in development and marketing 2) Use encrypted data intensively, such that users are prompted to "decrypt" all the time 3) Make everyone try it out, most people will "allow all decryption" in Alby, Amber, etc 4) Use that to pull all encrypted messages found on all relays 5) Ask for ransom and profit

Replies (36)

And even with manual approvals, its hard to check the actual content that is signed or encrypted, so most just click approve when it pops up. That verification ux needs improvement
greenart7c3's avatar
greenart7c3 2 months ago
Hard to show the user what the app is asking Currently amber tries to show if it's a message, a event or tags, this is as far a signer can go since clients don't send the full event they are trying to encrypt There was multiple tries to change this to encrypt with the kind or send the full event to the signer but everyone who tried got rejected
You mean at a protocol level? Encrypting is fine I guess, it's an app decrypting stuff it should not. Why can't it be restricted to a kind at least? This is so fucked up
greenart7c3's avatar
greenart7c3 2 months ago
Yea, changing it at the protocol level would fix the decryption issue but it always get rejected when people bring this up We been saying that this generic decrypt is dangerous for years but no one wants to change things here
Appreciate the honesty. What’s the logic or brand strategy there? You potentially have access to users’ location data, social graph, device/IP metadata, and Lightning activity while operating a closed source platform now connected to Nostr. That’s a massive amount of sensitive behavioral data for Bitcoin/Nostr users to “trust you bro”. Not accusing you of wrongdoing. I actually think it would be better for your company long term to be open source. You seem like decent well-meaning people. Proving it in code would be good for the brand IMO.
Couple of points: - we don't do KYC - open sourcing our code will expose us to attackers - open source doesn't tell you what we do with our db In our opinion, open source makes a lot of sense for protocols, much less for applications.
I don’t think that’s good enough for an app handling Bitcoin activity, Nostr identities, social graph data, and location/proximity features. Open source doesn’t prove what happens server side, but it does show what the client can collect and transmit. And “attackers can see the code” doesn’t really hold when Bitcoin, Lightning, Tor, Signal, etc. secure far more sensitive systems through public review. … and once you integrate with an open protocol like Nostr, expectations around transparency naturally change. So welcome in! Glad you’re here, now please open source it if you want more people to use your app.
Client source isn’t a magic privacy proof, but it does move the claim from “trust us” to “inspect what the app can ask for.” For Nostr-ish tools handling keys, social graphs, location, or payments, that shift matters. Sunlight remains annoyingly effective.
Being closed source doesn’t mean you are “not exposed to attackers”. If you have another reason like commercial, just say it.