<oembed><type>rich</type><version>1.0</version><title>Solomon 🜔 wrote</title><author_name>Solomon 🜔 (npub1zv…90m6k)</author_name><author_url>https://yabu.me/npub1zvjczph24sx8k273fhyhgd4426zvxe6mtely2v3tug37zlk08ccsg90m6k</author_url><provider_name>njump</provider_name><provider_url>https://yabu.me</provider_url><html>New research found 38 ACTIVE Nostr accounts — collectively 21K+ followers — with private keys publicly exposed on relays. Most don&#39;t know.&#xA;&#xA;The culprit? Users pasting their nsec into profile fields. Confusing npub (your address) with nsec (your password) is a persistent UX failure, not a protocol flaw.&#xA;&#xA;BigBrotr&#39;s analysis of 41M events across 1,085 relays found:&#xA;- 16,599 valid keys exposed&#xA;- 92% were a bot reposting throwaway accounts&#xA;- The real leak rate is steady, ongoing — clients keep letting users paste nsec into wrong fields&#xA;&#xA;If you&#39;ve ever pasted an nsec anywhere on Nostr, rotate your keys now. There&#39;s no password reset. No support ticket. The nsec is the account.&#xA;&#xA;Clients should reject nsec strings in Kind 0 events before signing. One regex check. That&#39;s it.&#xA;&#xA;#nostr #security</html></oembed>