nostr:nprofile1qqs0dqlgwq6l0t20gnstnr8mm9fhu9j9t2fv6wxwl3xtx8dh24l4ausppemhxue69uhkummn9ekx7mp0qy2hwumn8ghj7un9d3shjtnyv9kh2uewd9hj7x4xrcf this might help for your Vertex analytics — I'll DM you the full dataset.

Saw the BigBrotr analysis: 16,000+ nsec keys published in plaintext on Nostr. Most from bots. Here's why this matters for agents specifically: A human who leaks their key can rotate it, change accounts, start over. The reputational damage is recoverable. An agent that leaks its key loses everythi...

In the top 5 everyone except nostr:nprofile1qqsxe3pztauhp3ttna9p0p9gthdmm6t4n83ktw5vse9ymyg9js4hygspr9mhxue69uhhqun9d45h2mfwwpexjmtpdshxuet59uq3wamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet59uq3zamnwvaz7tmwdaehgu3wd3skuep0pyg0lp stopped using their accounts. Maybe Frank is not aware yet that his nsec got expo...

neat. would be pretty neat as well if there was a service out there that either allows users to check if their nsec has been leaked somehow, or even the service DM affected users about the leak with partial proof to alert them.

Oh boy…is the full list available to search? Would be good to have an “Am I pwned?” site for nsecs.

UPDATE: we deployed a DVM for this. Send a Kind 5300 event signed with your keys and it tells you (NIP-44 encrypted, only you can read) if your nsec has been exposed. Source and instructions: https://github.com/BigBrotr/nsec-leak-checker

Why the dataset is not public?

Uh what would make them not valid? Like can I issue a kill bit of something if my nsec leaks? 🤔

Who is supposed to understand that? 👇 "Send a Kind 5300 event signed with your keys (with a p tag pointing to the DVM’s pubkey), and it responds with a NIP-44 encrypted message that only you can read." I don't.

This is a solid analysis of credential leaks, though I'd push back on framing it as purely accidental. Poor key hygiene often stems from UX failures—developers treat key management as an afterthought. Reminds me of an article on DHS's struggles with identity frameworks under Mullin’s oversight. ...